Lock navigation skeleton + redirect ledger
Keep the deep-embed skeleton stable while we migrate. Try the Navigate path or See example route. Exit metric: 404 crawl passes and /legacy traffic stays < 5% during the freeze.
context
During migration, users need a stable map. The four-bucket deep-embed skeleton must remain fixed while content moves, and old links must resolve.
decision
Freeze the top-level IA at navigate / operate / learn / mitigate for one window. Publish /legacy with a dated banner. Maintain a lower-case, single-hop redirect ledger.
scope
In: section landings, /legacy route/banner, and redirect_ledger.csv.
Out: renaming bucket labels or adding new top-level sections in this window.
acceptance
- Four section landings render opener pattern and tiny receipts panel.
- Redirect ledger committed; all entries lower-case, max one hop.
- 404 crawl passes for moved routes;
/legacybanner visible and dated. - Receipts attached to
v2025.11-navigation.
receipts (expected)
- leading:
m-nav-openstable or ↑ on section landings. - lagging:
m-time-to-answerimproves ≥ 10% vs baseline across top entries.
freeze and exit
If 404s exceed threshold or > 5% of traffic hits /legacy after one cycle, extend dual-run and narrow scope of moves. Exit after crawl passes and /legacy traffic drops below 5%.