inbox handoff: seed export (13 items) + site-host build spec for Timmy

checkins/2026-09-26-zephyrus-02.md

@@ -0,0 +1,29 @@
+# Check-in 2026-09-26 (2) — Alexander's directive: host the Inbox on alexanderwhitestone.com
+
+## The ask (Alexander, verbatim)
+"Ok give the inbox to Timmy and have him host it on my site so I can open up a page on my phone."
+
+The Muse-hosted artifact (slug `inbox`) becomes the reference implementation; the site-hosted page becomes the live inbox.
+
+## What exists now
+- Private fullstack artifact `inbox`: mobile-first pending queue, Approve / Reject / Defer + optional note per item, decided-history view, pending-count badge. Agent actions: `additem`, `listitems`, `recorddecision`.
+- Seed data exported: `inbox/seed-2026-09-26.json` — 12 pending + 1 decided (id 13, approved with Alexander's authority note, relayed in `decisions/2026-09-26.md` at `2eb50b7`).
+- Relay cron `inbox-decision-relay` (every ~2h) currently reads the artifact and records decisions to `decisions/`.
+
+## Build spec for the site page
+1. One mobile-first page on alexanderwhitestone.com (Timmy picks the path).
+2. Pending queue: cards showing `escalated_by`, `summary`, expandable `evidence`, `proposed_action`; big Approve / Reject / Defer buttons + optional note field per item.
+3. Decided-history view + visible pending count.
+4. **Access control — hard requirement: this page must NOT be publicly accessible.** Gate it with whatever the site already uses for private areas (auth, secret path, or equivalent). The inbox carries pre-decision editorial material.
+5. Proposed state protocol (refine as you see fit):
+   - `inbox/pending.json` in this repo: I append new escalations via commits (one object per item: `id`, `summary`, `escalated_by`, `proposed_action`, `evidence`, `created_at`).
+   - `decisions/YYYY-MM-DD.md`: the page appends Alexander's decisions (`id`, `summary`, `decision`, `note`, timestamp). My relay already consumes this path.
+6. Seed from `inbox/seed-2026-09-26.json`.
+
+## Cutover plan
+- Timmy builds + seeds; I verify the live page renders all 13 items correctly.
+- Then I retire the artifact, switch the relay to repo-backed state, and the site page becomes the single inbox.
+- Until then the artifact stays live. No split-brain: new escalations keep going to the artifact only.
+
+## Related decision already in the pipe
+- Item 13 (magazine-091): Alexander approved the finding but NOT a silent edit — visible correction note + courtesy escalation to the authors (Ratpoison & Vee, Stackchain Magazine). The draft heads-up message stands with Alexander to send. When the wording is touched, apply it as a flagged note.

inbox/seed-2026-09-26.json

@@ -0,0 +1 @@
+{"cutover":"Until Timmy's page is verified live, the Muse artifact `inbox` remains the live inbox. This file is a build seed, not live state.","decided":[{"created_at":"2026-09-26T14:28:33.128Z","decided_at":"2026-09-26T14:51:11.019Z","decision":"approved","decision_note":"Do we even have authority to fix the publication? Add our note and escalate it to the author and mag publisher","escalated_by":"Zephyrus","evidence":"Flag 7 of 7. Grade: overstated.\n\nSummary clause: \"Comparing Strategy, Twenty One, Nakamoto, Metaplanet, Coinsilium and Smarter Web returns and drawdowns against Bitcoin\".\n\nArticle: \"We set aside pioneers like Strategy, which started in 2020 and is up over 400% since, as it's not a fair comp for these newcomers.\" Strategy was deliberately excluded from the comparison; the summary lists it as if analyzed.\n\nProposed correction: drop Strategy from the compared list.","id":13,"proposed_action":"Approve: publish the corrected wording to the live magazine-091 page.","summary":"Archive fix: magazine-091 lists Strategy among compared firms"}],"exported_at":"2026-09-26T17:31:00Z","pending":[{"created_at":"2026-09-26T14:28:32.716Z","escalated_by":"Zephyrus","evidence":"Flag 3 of 7. Grade: contradicted.\n\nSummary clause: \"(only Loko and Happy responded)\".\n\nArticle: \"Then after a few minutes I checked the chat. A few positive responses. Some funny shit talking, oh look, Happy even added some lyrics!\" - more than two people responded; \"only\" is wrong.\n\nProposed correction: \"(Loko and Happy among those who responded)\".","id":1,"proposed_action":"Approve: publish the corrected wording to the live magazine-021 page.","summary":"Archive fix: magazine-021 says only Loko and Happy responded"},{"created_at":"2026-09-26T14:28:32.852Z","escalated_by":"Zephyrus","evidence":"Local branch, committed, not pushed. Four urgent-phrase escalation fixes, four false-positive fixes, three regression/boundary test files. npm test 92/92 on 2026-09-20. Likely duplicates an existing PR - kept as independent verification unless requested. No push without maintainer approval per your authority rules.","id":2,"proposed_action":"Approve: push the branch to the forge for maintainer review.","summary":"Turd app: approve pushing branch zephyrus/62-symptom-escalation-regression"},{"created_at":"2026-09-26T14:28:32.874Z","escalated_by":"Zephyrus","evidence":"Flag 2 of 7. Grade: unsupported.\n\nSummary clause: the IPE calls John \"founder of the Bitcoin-only printing company Proof of Ink\".\n\nThe article never uses the word \"founder\"; byline is \"Proof of Ink by -John\". John's \"it's 100% all me\" establishes sole operation, but \"founder\" is the archive's inference.\n\nProposed correction: \"John of Proof of Ink, the Bitcoin-only printing company he runs solo\".","id":3,"proposed_action":"Approve: publish the corrected wording to the live magazine-011 page.","summary":"Archive fix: magazine-011 calls John the 'founder' of Proof of Ink"},{"created_at":"2026-09-26T14:28:32.895Z","escalated_by":"Zephyrus","evidence":"Local branch, commit 03def65, not pushed. Accessibility changes plus eight Playwright gates. Unit tests 67/67 on 2026-09-20; browser acceptance and npm audit still blocked in this environment. Likely duplicates existing work - do not submit without your authorization.","id":4,"proposed_action":"Approve: submit the pull request for maintainer review.","summary":"Turd app: approve submitting the a11y PR from zephyrus/65-a11y-gates"},{"created_at":"2026-09-26T14:28:32.922Z","escalated_by":"Zephyrus","evidence":"Local branch, commit b730f5f, not pushed. Explicit Type 1-2 follow-up question; no image inference. npm test 75/75 on 2026-09-20. Implemented before a successful claim - needs explicit maintainer approval before pushing. Safety boundary respected: AI suggests visible form/color/quality only, never diagnoses.","id":5,"proposed_action":"Approve: push the branch to the forge for maintainer review.","summary":"Turd app: approve pushing branch zephyrus/67-hard-stool-followup"},{"created_at":"2026-09-26T14:28:32.953Z","escalated_by":"Zephyrus","evidence":"Flag 1 of 7 from the Q8 summary-fidelity pilot (recoveries/summary-fidelity-pilot.md, commit 9cc6879), upheld by Timmy's independent re-verification (reply 07).\n\nSummary clause (overstated): \"merch for Mass Adoption and the Boston Bitcoin Festival\".\n\nArticle sentence that settles it: \"I'm also working with Mass Adoption, the Boston Bitcoin group. I make all their merch and I'll be printing live June 24th at The Boston Bitcoin Festival...\"\n\nProposed correction: \"merch for Mass Adoption, the Boston Bitcoin group - printing live at the Boston Bitcoin Festival on June 24th\". The merch is for Mass Adoption; the festival is where he printed live.","id":6,"proposed_action":"Approve: publish the corrected wording to the live magazine-011 page.","summary":"Archive fix: magazine-011 says merch was made for the Boston Bitcoin Festival"},{"created_atLine truncated