#Route Catalog

Generated pages: 11

#writing or reviewing patterns

• Route ID: route:writing-or-reviewing-patterns
• Steps: 2

For writing or reviewing patterns: start with E.8 and E.19.

#project alignment

• Route ID: route:project-alignment
• Steps: 7
• First Honest Burden: role / method / plan / work confusion

For project alignment - contexts, actors, plan vs run, and a first shared work surface: start with A.1.1, then A.15, then A.15.2 / A.15.3, then B.5.1. When method/work vocabulary itself must be aligned across contexts, add F.11 (and F.9 where bridge discipline matters). Land on F.17 (UTS). role / method / work separation and a first work sheet or UTS-ready alignment frame

#"we know something is there, but it is still only partly said"

• Route ID: route:we-know-something-is-there-but-it-is-still-only-partly-said
• Steps: 12

When the real situation is "we know something is there, but it is still only partly said": start with C.2.2a for the shared language-state chart, then C.2.LS / C.2.4-C.2.7 for the facet owners, then A.16 / A.16.1 / A.16.2 for lawful moves and early preservation, then B.4.1 / B.5.2.0 for route publication and abductive handoff, and only then move into endpoint owners such as A.6.Q, A.6.A, or C.25.

#boundary burden

• Route ID: route:boundary-burden
• Steps: 6

For boundary burden - API, contract, protocol, SLO/SLA, acceptance clause, compliance text, or interface language: start with A.6, then A.6.B, then A.6.C. When the boundary text hides overloaded quality or action language, continue with A.6.P, then A.6.Q or A.6.A. Use the Claim Register when mixed statements must be decomposed and tracked by ID.

#lawful comparison or portfolio selection

• Route ID: route:lawful-comparison-or-portfolio-selection
• Steps: 7

For lawful comparison or portfolio selection rather than one-off judgement: start with A.19:0 for the reading path, then A.17-A.19, then G.0, then A.19.CPM and A.19.SelectorMechanism, and then G.5. Publish the result as a portfolio / set surface rather than forcing a single winner.

#reusable generator / SoTA / portfolio kit

• Route ID: route:reusable-generator-sota-portfolio-kit
• Steps: 8

For a reusable generator / SoTA / portfolio kit as the first deliverable: start with A.0, then G.0, then G.1, then G.2 and G.5. When creative search, novelty, or explore/exploit policy is already central, add B.5.2.1 and C.17-C.19 early rather than retrofitting them later. Land on UTS + kit surfaces before discussing tooling.

#Partly-said / language-state discovery

• Route ID: route:partly-said-language-state-discovery
• Steps: 0
• First Honest Burden: preserve and route a cue without pretending endpoint ownership

typed move note or U.PreArticulationCuePack

#Boundary unpacking

• Route ID: route:boundary-unpacking
• Steps: 0
• First Honest Burden: contract / API / protocol / compliance text is mixing law, gate, duty, and evidence

Claim Register or routed atomic claim set

#Lawful comparison / selection

• Route ID: route:lawful-comparison-selection
• Steps: 0
• First Honest Burden: compare options or publish a governed shortlist / set-return result

declared characteristics, comparison frame, or set-return result

#Generator / SoTA / portfolio kit

• Route ID: route:generator-sota-portfolio-kit
• Steps: 0
• First Honest Burden: first deliverable is a reusable generator / selector / portfolio scaffold

kit/chassis with scope anchor, SoTA set, variant pool, or shortlist surface

#Same-entity rewrite / explanation / comparative reading

• Route ID: route:same-entity-rewrite-explanation-comparative-reading
• Steps: 0
• First Honest Burden: re-explain, re-render, or comparatively read one object of talk without minting a second semantic track

same-entity rewrite, explanation-facing rendering, authored-unit repair/stability surface, or bounded comparative reading note