Everything below is in service of these. If a surface isn't one of the 6 and isn't feeding one of the 6, it's a candidate to cut.
| Cluster | What's there | Call |
|---|---|---|
| Home dashboards 4 → 1 | home.html (canonical) + home-cockpit + start + decide | KEEP home.html. Archive home-cockpit, start, decide — older variants of the same bento. |
| Queue / loop views 7 → 2 | next, today, week, list, triage, rethink + 2 dated boards — all render the same Action_Queue | KEEP next (do-this-now) + list (full queue). Fold triage's swipe + rethink's clustering into list as modes. Archive today, week, and the 2 boards (home already shows "today"). This is your biggest bloat — one queue, seven doors. |
| System maps 5 → 1 | architecture, map, stack-map, operating-map (+ a proposed Connections map) | KEEP operating-map ("what you're steering"). Archive the other 3-4 — you look at these almost never. |
| Briefings indexes 3 → 1 | index.html, index.generated.html, briefings.html | KEEP index.html (auto-generated). Kill the other two. |
| Chanie pages 10 → 1 | chanie + chanie-home (live) + 7 design mockups (A–G) + chanie-beach | NEEDS YOUR PICK: choose ONE design direction → make it the live chanie.html, archive the 7 mockups + beach. They were always meant as a "pick one" set. |
| Cameras 2 → 1 | cameras.html (live) + camera-live.html (a "moved" stub) | KEEP cameras.html. Delete the stub. |
| MIS surfaces keep | mis-cockpit (live via fn=cockpit) + peek + v1 (retired) + v2 (frozen) | KEEP mis-cockpit + peek. Archive MIS v1 (retired engine). v2 stays frozen. |
| Bots / relays keep all | Start Here bot, chanie-relay, manny-relay (shared webhook pattern) | KEEP all 3. Not redundancy — per-person isolation is deliberate (each client gets a walled bot). The shared pattern is a template, the asset you resell. |
| BOS money emails reconcile | BOS v1 + v2 sheets both fire obligation/cashflow emails; ops-api cron also does morning delivery | One owner for money emails. Documented as "complementary" but they overlap — worth a 15-min look to pick which fires what (separate pass). |
Net: ~20 surfaces collapse to ~8. Nothing you use daily is touched — only the variants, mockups, meta-maps, and duplicate queue doors. (Archive = move to archive/, never hard-delete — reversible.)
The pattern is the same one you flagged about the morning briefs: you don't have too many tools, you have too many doors into the same tool. One Action_Queue behind seven pages. One home behind four. One set of facts behind five maps. The fix isn't building — it's closing doors.
You just watched your own sprawl get read, clustered, and reduced from 50 surfaces to 6-that-matter with a keep/merge/kill call on each. That is the exact service. Every operator you'd sell to has this same mess — too many doors, no one who'll walk the whole thing and tell them what to close.
Your Bottleneck Review / Operator Cockpit offer is this map, run on their systems: inventory every surface → flag the overlaps → keep/merge/kill → hand back the clean 6. The deliverable is a one-pager exactly like this one. You don't have to invent the product — you just demonstrated it on yourself.
Two clean wins, your call which first: (1) say "archive the variants" and I move the ~14 safe kills (home variants, dup indexes, extra maps, camera stub, the dated boards) to archive/ in one pass — your launcher gets quiet. (2) Pick a Chanie design (A–G) and I make it live + archive the rest. The queue-view merge (7→2) is a slightly bigger build — flag it and I'll spec it next.