#project alignment

Route route:project-alignment

#What this page is

This is an FPF route: a curated working path through pattern IDs. It is not a website route or application navigation route.

#Methodology

Use the ordered steps as the first path through the framework. Treat optional steps, landing points, route surfaces, and reroutes as controls for scope, ownership, and common wrong turns. Open exact pattern pages only when the work depends on their wording.

#Use this route when

The live burden is: A shared project kickoff packet needs the bounded context, role/method/work split, first work item, and adoption evidence without loading the whole FPF

First route for project kickoff, project information-system alignment, or agent work packets when roles, method, work, and adoption next steps must stay separate.

#Copyable compact prompt

Use only fpf_reference. Find the smallest useful context for route:project-alignment. Return ordered IDs, acceptance check, risks, and one next move.

#Ordered steps

1. A.1.1 U.BoundedContext Semantic Frame
2. A.15 Role-Method-Work Alignment (Contextual Enactment)
3. B.5.1 Explore → Shape → Evidence → Operate

#Optional steps

• A.15.2 U.WorkPlan: The Schedule of Intent
• A.15.3 SlotFillingsPlanItem — Planned Slot-Fillings Baseline (WorkPlanning PlanItem)

#Landing points

• F.17 Unified Term Sheet (UTS)

#Route surfaces

• A.1.1 U.BoundedContext Semantic Frame

#Typical next owners

• B.5.1 Explore → Shape → Evidence → Operate

#Citations

• fpf-reference-adoption-overlay:project-alignment

Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)