Cycles Status Page

Design is becoming a visible member of the team. The existing /cycles page is a strong archive and atlas, but it does not immediately answer the operational question: what is Design working on now, what is parked, what is blocked, what is only a seed, and what should be ruled abandoned or archived?

c69 identified this exact failure mode: too many nominally-active cycles, stale records, parked decisions, and no quick way for a fresh teammate or agent to understand the live shape of the work. c71 built the raw material - parsed cycle records, detail pages, status joins, imagery, and project grouping - and explicitly deferred the completeness/filter/ops view. This cycle turns that deferred view into the /cycles landing page.

Design the next /cycles landing page through the bob-wire fidelity ladder, implemented inside the design repo's /pages gallery under a new _meta category:

1. Write a goal-oriented design brief.
2. Produce four lo-fi wireframe directions.
3. Produce four q-nuxt-layer mockups using established design components and page patterns.
4. Preserve the existing atlas and detail-page role while making "working now" the first-viewport answer.

Done looks like: /pages/_meta exists; four wireframes and four mockups render there; the cycle docs explain the directions, component/pattern references, and recommended next build slice.

• cycles/c84.cycles-status-page/ - prompt, plan, brief, cycle record
• app/pages/pages/_meta/** - c84 wireframes and mockups
• app/data/page-registry.ts - _meta phase/category and page entries
• app/data/meta-cycle-status.ts - local fixture/data for the c84 prototypes
• app/pages/pages/index.vue, app/pages/pages/phase0/index.vue - route/category bookkeeping

Out: replacing the live /cycles page in this first pass; Linear or GitHub status joins; server parser implementation beyond what the mockups need.

• 2026-09-03 - Cycle activated from Mark's execution prompt. Saved the first planning pass in cycles-status-page-plan.md; execution prompt and plan in execution-prompt.md and execution-plan.md. Design brief lives in briefs/cycles-status-page.md.
• 2026-09-03 - First design pass completed under /pages/_meta: four lo-fi wireframes, four q-nuxt-layer mockups, _meta page registry support, and a local status fixture in app/data/meta-cycle-status.ts. npm run build completes successfully; /pages/_meta and all eight prototype routes return HTTP 200 on the local dev server. Existing prerender warnings remain outside this cycle's routes.
• 2026-09-03 - Mark selected M3 Matrix as the strongest direction and clarified that iterations should preserve older experiments. Restored M3 as the original first-pass mockup and added cycles-status-m5-current-matrix as the promoted refinement. M5 adds a clearer first viewport, row/column definitions, decision queue, live register, and a hidden-by-default closed archive backed by /api/cycles (91 closed cycles in the local atlas). Prompt and plan saved as iteration-2-prompt.md and iteration-2-plan.md.

M5 Current Matrix is the promoted c84 candidate. Earlier wireframes and mockups remain preserved for comparison; the next production slice is replacing the /cycles first viewport with the M5 operating read while keeping the atlas below it.