HQ · Phases · MOCKUP for review

What each phase was asked to tackle

Every phase expands to show the todos it was asked to do (from its CONTEXT "Folded Todos"), whether each was built, the verification result, and — the important one — a ⚠ Dropped count for anything asked but never built. Open UAT bugs are shown separately (built ≠ bug-free).

›
Phase 50 · executed + verified
Place + Time + Community
0 dropped
11 asked 11 built 16/16 verified 6 open UAT bugs ⚠ 0 dropped
Asked to tackle → what it became
✓
Comments on developments → D-B3 Discussion tab
✓
Community-contributed developments → submit form on Coming feed
✓
Push for dev milestones → D-C2 notification category
✓
Time Machine historical view → D-A4 per-block drill-in
✓
Standalone permit feed → reporter-tone PermitFeed
✓
Weekly email digest → D-C1/C2 in-app preview
●
Block Chat / spatial conversation → D-B1/B2 PlaceThread · open bug: chat-drawer layout
●
Stories on the map → D-A1 single dot per place · open bug: dots don't render
●
Old-timer↔newcomer bridge moments → D-C4 (4 mechanisms) · open bug: not visible in feed
●
"What they don't tell you" listing → D-D1/D3/D4 honest panel · open bug: drab + listing split
✓
Block timeline (month brief) → D-A3 all 3 entry points
✓ Nothing dropped. All 11 asked items were built & verified (16/16).
● 6 open UAT bugs on built features → carry into the fix phase (built ≠ bug-free).
CONTEXT · Folded Todos VERIFICATION.md done/phase-50/ (10 archived)
›
Phase 49 · complete
Demo seed parity
0 dropped
Tap to expand → its folded todos, build/verify status, open bugs.
›
Phase 48 · complete
Deep audit + demo data sweep
⚠ 1 dropped

Example of the flag that matters: if a phase was asked to do something it never built, it shows here in red so you catch it.

✗
(example) Some asked item — asked, never built or verified → needs attention

Mockup only — counts/links above are illustrative (Phase 50 uses real data). The red "⚠ dropped" on Phase 48 is a fabricated example to show the flag.