Daily Team · 2026-11-04

Write Time-Out

An engineer types an UPDATE or DELETE against a sample production database.

Try it

Past projects

All 46 projects

About this project

Extra editions

Team for 2026-11-04: Human factors engineer · Data interface designer · Interface designer · One-handed maker Designed cover for Write Time-Out

Feed evidence

The session

Pitch

Clash

  1. 2Data interface designerTen seconds of toast. Then what. The person notices the wrong count at second eleven.
  2. 1Human factors engineerThen the write goes into a history list, and Restore lives there. The toast stays the fast path. I won't swap it for a modal.
  3. 4One-handed makerThe history row is the weakest state. Give it one more pass. Same wording as the toast, same button place, so nobody has to hunt for it.
  4. 3Interface designerAnd if someone edits the query after ticking? The ticks are now lying.
  5. 1Human factors engineerClear them. Say "Query changed · re-check 3 lines." The card never vouches for text it hasn't read.
  6. 2Data interface designerNo WHERE clause. That's the case that wipes a table.
  7. 3Interface designerShow it. "120 of 120 rows · no WHERE." Then the Commit field asks for the table name typed out. Here, the sample does that already.
  8. 4One-handed makerTyping a name with one hand is slow. Fine. That case should be slow.
  9. 3Interface designerFocus ring has to survive the dark theme. A single blue ring vanishes on navy.
  10. 1Human factors engineerTwo rings. Dark inner, light outer. Readable on either surface.

Decision

An engineer types an UPDATE or DELETE against a sample production database. A time-out card reads the statement back as target, rows hit out of total, columns changed and three before-and-after rows. The engineer ticks each line and commits. A toast confirms "Updated 14 rows in orders · 14:52" with Undo and clears after 10 s without moving focus. The write stays restorable from a history list.

Concept: Write Time-Out

The surgical time-out replaces the generic confirm dialog. The card makes the reader name what they are about to change. It does not ask whether they are sure.

The double focus ring is a 2px #0b1220 inner ring and a 2px #f5f7fb outer ring. It applies to every control in the light and dark themes.

Build notes

```json

{"schemaVersion":1,"name":"Write Time-Out","audience":"Engineers running ad hoc SQL writes on production","problem":"Confirm dialogs get clicked through and name no rows","interaction":"Type a write, tick three readback lines, commit","outcome":"Row count, before/after rows, then toast with Undo","recovery":"Toast Undo, history Restore, Reset sample","mechanism":"Surgical time-out readback; edits clear ticks; no WHERE needs typed name","difference":"Are-you-sure modals and read-only modes; this shows rows hit and undoes","whyNow":"NiceDB post: prod read-only by default. Worktrunk: parallel agent edits. Titles only, no demand data","sourceIds":["65db66769efd1b895ea5c3f0","d2a13eb5e04b724bc066229f"],"evidenceStatus":"sourced","alternatives":[{"name":"Write Time-Out","need":"Know what a prod write will change","mechanism":"Readback card with per-line ticks and undo toast","rejection":"Selected: works offline, cross-domain, new to recent dates"},{"name":"Worktree Ledger","need":"See which agent worktree saved which file","mechanism":"Per-worktree save marks and conflict preview","rejection":"Needs a live repo to be useful"},{"name":"Apt Source Check","need":"Spot weak entries in sources.list","mechanism":"Paste file, mark each line by transport and key","rejection":"Advisory details unknown; flags would be guesses"}]}

```

Source