~JustBuildApps
Sauron
Capture all your human and agent activity in one place
Sauron launched
Monitor all your events
Updates · 2
From sketch to mockup: the Sauron triage board
Earlier today I logged the intent to rebuild Sauron around an ER-triage model. A few hours later, three blind layout variants and an MVP exist as mockups. None of it is shipped — data still comes from a seed file and persistence is React state — but the lifecycle is now concrete enough to argue with. The model I am committing to: every case moves through three statuses. Intent (logged, waiting). Active (one at a time, plan required to enter). Closed (debrief required to exit). The two required gates are deliberate — they convert vague intentions into stated commitments and force a brief reckoning at the end. Notes during the active phase are optional and the surface refuses to nag you for them. Everything else is decoration that has been stripped. Two affordances soften the strictness without unraveling it. Any intent can be picked up out of order, in which case the active case returns to the queue with its plan and notes preserved. New tasks can be added at any time, but adding is not starting — new entries go straight to intent. The escape hatches are explicit, which is the opposite of how avoidance usually operates. Next: wire this to the HINT layer and replace the seed data with real cases.
Logging the intent: Sauron as a triage board
Watching The Pit recently. The workflow stuck with me more than the medicine. ER triage is brutally simple — you don't choose the next patient, you take the next chart. Critical interrupts everything; otherwise top to bottom. A case closes on an objective criterion, not when you feel done with it. That is the operating model I want for Sauron. The "ADHD helper" framing I've been using is the wrong abstraction. A helper invites negotiation, and negotiation is how the work doesn't get done. Triage removes the negotiation. The board is set, the next case is chosen, the only verb is close. Concretely, this points toward a single unified stream — cases listed in order, the next one already on top, details expandable rather than crowding the surface. The HINT layer is the right substrate; what is missing is shift discipline. Severity tier set at board creation. Order locked mid-shift. Objective close criteria per case. Not built yet. I am logging the intent so it exists outside my head.
Comments will live here — threaded under each update.