#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.

• First Honest Burden: "We keep mixing responsibilities, working method, plans, and what actually happened."

For project alignment - contexts, roles, method, plan, run, and a first shared work or vocabulary stabilizer: inspect A.1.1, A.15, A.15.2 / A.15.3, and B.5.1. Consider F.11 when method/work vocabulary must be aligned across contexts, F.9 when bridge discipline matters, and F.17 when term stabilization is the live burden. F.11 when method/work vocabulary is itself unstable; F.9 when bridge discipline is live; F.17 as a typical vocabulary-stabilizing output

#Ordered steps

1. A.1.1 U.BoundedContext: The Semantic Frame
2. A.15 Role-Method-Work Alignment (Contextual Enactment)
3. A.15.2 U.WorkPlan: The Schedule of Intent
4. A.15.3 SlotFillingsPlanItem — Planned Slot-Fillings Baseline (WorkPlanning PlanItem)
5. B.5.1 Explore → Shape → Evidence → Operate

#Landing points

• F.11 Method Quartet Harmonisation
• F.9 Alignment & Bridge across Contexts
• F.17 Unified Term Sheet (UTS)

#Route surfaces

• A.1.1 U.BoundedContext: The Semantic Frame
• A.15 Role-Method-Work Alignment (Contextual Enactment)
• A.15.2 U.WorkPlan: The Schedule of Intent
• A.15.3 SlotFillingsPlanItem — Planned Slot-Fillings Baseline (WorkPlanning PlanItem)
• B.5.1 Explore → Shape → Evidence → Operate

#Citations

• Preface/Where to start
• J.4