docs: recover AR redesign docs onto freeze main (supersedes #245) - #251
Conversation
Fresh branch from current main recovers SUPPORTING redesign map, inventory (Ember Fox runtime), IA conflicts, phased plan, north star, and MVP→vision ladder. Index wiring only on freeze-era docs; no stale #245 history, no binding-law rewrite, no mesh/code changes.
|
Recovery of #245 onto freeze main for Prabu's rebase request. Docs-only; SUPPORTING authority. Please review when CI is green. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ac2efb514b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Require Phase 1 indoor+outdoor device evidence before Phase 2 AR-default UX; document assumed-ground then camera placement fallback; mark recovery as landing via #251 (complete after merge).
prabu-openclaw
left a comment
There was a problem hiding this comment.
Approving. This is the clean recovery of #245 onto the freeze baseline — #245 can be closed.
Verified rather than assumed:
Scope. Docs only. The two files outside docs/ are README.md and ROADMAP.md, both pointer wiring. No Swift, no assets.
The freeze is not lifted. AR_MVP_FREEZE.md has exactly one added line and zero removals — the redesign map is registered as SUPPORTING with "does not lift freeze" stated inline. That was the thing worth checking most carefully, and it holds.
Binding law untouched. WAYKIN_SPEC, SOLO_MVP_SCOPE, ARCHITECTURE and the capability matrix appear only in the does_not_override list. North star stays REFERENCE_ONLY; the map is scoped "near-term only, chapter one, not the full vision."
Runtime description is accurate. recovered_on_main_base: 28bea09, companion_runtime: MESHY_EMBER_FOX_WALK_V1, and the inventory correctly describes the post-#246 loader — versioned async template load, procedural fallback, live authored replacement, explicit scene-anchor detach. That matches what actually shipped, including the two bugs that caused the placeholder to persist on device.
Only carry-over note from my #245 review, unchanged and not blocking: WAYKIN_SPEC still opens "audio-first adaptive walking experience" while this maps AR as the primary surface. C1–C11 and Phase 0 are the right place for that; flagging so the eventual spec edit is deliberate rather than drift. Worth remembering audio is currently the most reliable layer on device — .playback plus background mode, cues confirmed audible on real walks.
Summary
Workstream E / Prabu rebase request for #245 — recovered onto current freeze
mainwithout merging stale branch history.main(post #249/#250 freeze)SOLO_MVP_SCOPE,WAYKIN_SPEC)Why not rebase #245 in place
Per freeze plan and safety hold: #245 was cut before Ember Fox / pressure on main. Recreating from current
mainavoids force-merging stale history and index conflicts with freeze re-baseline docs.Documents recovered
docs/design/AR_PRODUCT_REDESIGN_MAP.mddocs/design/AR_SYSTEM_INVENTORY.md(Ember Fox runtime corrections)docs/design/AR_SESSION_IA_CONFLICTS.mddocs/plans/AR_APP_REDESIGN_PLAN.mddocs/design/PRODUCT_VISION_NORTH_STAR.md(REFERENCE_ONLY)docs/canonical/MVP_TO_VISION_LADDER.mdCorrections vs original #245
SPECULATIVElabelsNon-goals
After merge
Close #245 as superseded. Device indoor smoke remains next for product evidence before redesign implementation.
Test plan