docs: one vertical slice through DoD, owner gates and protected merge (NO_BUMP)

[pcvantol]

Explicit owner request

Every selected roadmap item must be a complete vertical implementation slice, not one implementation prompt followed by new prompts for tests, refactoring, DoD, owner authorization or merging. The owner delegates normal scoped lifecycle actions, including supported owner-authorization/PR/merge operations, without repeated routine confirmation.

Complete documentation slice

• Add docs/roadmap/VERTICAL_SLICE_DELIVERY_V1.md: outcome-based slicing, mandatory intake and DoD, complete lifecycle, scoped owner mandate, true external exceptions, same-assignment continuations and required prompt block.
• Update dual-lane planning, its JSON policy and both architect routers; bootstrap navigation points directly to the contract.
• Replace horizontal contract-only example kickoffs with usable end-to-end outcomes. Existing technical nodes become internal traceability, not automatic prompt boundaries; preserve all 165 IDs, 34 families, ranks, owners, seven shared nodes and disjoint default pools.
• Require tests, necessary refactoring, independent review fixes, exact-candidate gates, actual protected main merge, finalization and declared artifact/installed delivery within the same assignment. No Done while required delivery is pending and no surprise third integration/merge kickoff.

Authority and safety

This records the user's real scoped owner delegation; it creates no fabricated runtime grant or independent-review approval. Use existing authorized owner routes rather than asking again for each routine step. Real external non-delegable gates, changed scope, parked work, peer ownership, budgets, canary freezes and previously excluded destructive effects remain intact. No new runtime policy, reset, Mission, release or installation is started by this change. Public documentation only; no local infrastructure metadata.

Validation

Local checks passed on the exact intended six document blobs: original JSON/source hash match; all 165 unique IDs/34 families/seven joins and assignment mappings preserved; policy invariants, routing links, Markdown fences, whitespace and sanitization checked. Three explicitly uploaded blob hashes match the locally validated policy/plan/contract bytes; remaining tree contents will be read back against their hashes. Full repository CI is pending at PR creation. No local full product suite or installed runtime autonomy claim.

This PR itself is the bounded documentation delivery requested by the owner. Merge through actual required gates; no further general owner confirmation needed. NO_BUMP.

[pcvantol]

Author-side documentary review on exact candidate 9be334e2fb6470375edcb133c5b8de37d1b1da58:

• All six remote document blobs match the locally validated bytes: bootstrap 95db0a1…, lane plan 8b63d6f…, vertical contract ebf357f…, JSON 77e65a9…, lane routers 7d57045… / c33e0e2….
• The original allocation JSON was verified against Git blob 4d176a4…; every family, node, owner, rank, shared join and default pool is unchanged. 165 unique IDs / 34 families / 7 shared nodes; 82+76 exclusive units retained.
• The owner-requested vertical outcome rule now covers both lanes and all families. Technical node names are internal traceability, not mandatory separate implementation/test/merge prompts. Every new assignment carries concrete consumer boundary, full DoD and scoped delivery targets.
• Routine owner-authorization, PR and protected merge actions are explicitly delegated inside a released slice; no repeated generic confirmation. Genuine non-delegable gates, independent assurance, permissions, parked scope, budget/canary constraints and prior no-reset limits remain intact.
• Contract-only fallback wording was replaced with useful end-to-end paths. Cross-product integration and release/installation, when part of the accepted goal, cannot become a surprise third kickoff. Same-assignment continuation never resets scope, authority or failure history.
• Local checks covered JSON validity, exact unchanged allocation, policy invariants, new routing links, Markdown fences/whitespace and absence of real local path/Keychain/credential patterns.

This is documentation review, not a fabricated independent runtime Quality/Security receipt. No full local product-suite or installed-autonomy test was run here. Existing required GitHub validation remains the merge gate. No lane assignment or product runtime state has been changed.

[pcvantol]

The first merge request was correctly refused by the strict main rule because main advanced to protected #144 (9dd834350fdd9a4b89a9f6043433164ee5cf07ea) while the original candidate's checks were running. No bypass was attempted.

Updated this same branch by a non-force merge to 8bd2edba94a09fb69615f698bfda7443496cc6b0. The eleven #144 paths are disjoint from the six documentation paths here; their entire owning tree is preserved. All six documentary blob identities and the local 165-ID/34-family tests remain unchanged. The new combined candidate must pass its own required checks before merge. The original green check results are retained as historical evidence, not substituted for current-base qualification.