#Route Catalog

New here? Start at the orientation page — work packets, glossary, and the right entry point per task. Use this catalog when you know the work shape but need the exact route ID or ordered steps.

#What this page is

Routes are generated FPF working paths through pattern IDs. They are not website routes, app routes, or navigation implementation details.

#Methodology

Use a route when the work shape is known but the exact patterns are not. Follow ordered steps first, use optional and landing points only when the task needs them, then open individual pattern pages for exact wording or audit evidence.

Generated pages: 3

#project alignment

• Route ID: route:project-alignment
• Steps: 3
• First Honest Burden: 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.

#boundary unpacking

• Route ID: route:boundary-unpacking
• Steps: 3
• First Honest Burden: Mixed boundary prose needs atomic claim IDs and a declared owner layer before implementation or review can proceed safely

First route for API, contract, workflow, protocol, CI gate, deploy promise, or acceptance-clause boundary review.

#writing or reviewing patterns

• Route ID: route:writing-or-reviewing-patterns
• Steps: 2
• First Honest Burden: A pattern author or reviewer needs the minimum writing/review path before opening neighboring patterns

First route for spec writers adding, drafting, revising, or reviewing FPF patterns.

---

Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)