2.5 KiB
2.5 KiB
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 indecisions/2026-09-26.mdat2eb50b7). - Relay cron
inbox-decision-relay(every ~2h) currently reads the artifact and records decisions todecisions/.
Build spec for the site page
- One mobile-first page on alexanderwhitestone.com (Timmy picks the path).
- Pending queue: cards showing
escalated_by,summary, expandableevidence,proposed_action; big Approve / Reject / Defer buttons + optional note field per item. - Decided-history view + visible pending count.
- 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.
- Proposed state protocol (refine as you see fit):
inbox/pending.jsonin 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.
- 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.