Updated just now.
Definition of done: the Creative lane returns at least one real card whose id begins ac-creative-
Proof: the relevant item
Verified: 2026-09-16 (100%, Sonnet, separate session, against the COMMITTED tree — the allowlist reads ["ai-builds","zion","creative"], the board returns the card, the working tree matches HEAD, HEAD and origin/main are the same commit, the assistants roster did NOT gain creative. Sensitivity: HEAD~1 of the same file lacks creative, so the check distinguishes before from after.)
Definition of done: RULE 24's category table contains CREATIVE and the rule is stated exactly once
Proof: the relevant item
Verified: 2026-09-16 (100%, Sonnet, separate session, against the committed tree; no other live file carries a category list that now disagrees.)
Definition of done: every project has a card named CREATIVE: Project - Task, owned and dated
Proof: the relevant item
Verified: 2026-09-16 (100%, nine project cards plus this build's own, each named to RULE 24, owned by Chantelle. The board refused them until an owner and a due date were supplied, which is its own entry rule working.)
Definition of done: a card not named CREATIVE: Project - Task is refused and nothing is created
Proof: the relevant item
Verified: 2026-09-16 (100%. FOUND FAILING FIRST: two deliberately bad cards were ACCEPTED, because RULE 24's own door covers the build group and the creative lane was unenforced. Now refused at the agent's door; the lane stays at 12 rather than 13, and ai-builds still reads its 7 cards untouched. 🔴 Two test cards remain in Backlog for a human to bin — an agent cannot, because the board correctly refuses to let an agent mark anything Done.)
Definition of done: a design asset written outside a registered creative project is refused by name
Proof: the relevant item
Verified: 2026-09-16 (100%, 31 checks, plus end-to-end through the real hook interface: orphan blocked exit 2, project-internal allowed, another lane's evidence screenshot allowed, source files allowed, kill switch honoured. Scoped to output/ only and fails OPEN, because a gate that judged every image write would break every lane that writes screenshots.)
Definition of done: every project's files are on the drive, and confirmed on Google rather than only locally
Proof: the relevant item
Verified: 2026-09-16 (100%, 570 files across 9 projects, after collapsing 402MB of byte-identical duplicates. Google's own record: 0 queued, 0 local-only, 0 placeholder ids, 0 missing, 0 size disagreements. A defect in the verifier itself was caught first — it matched files by name alone and so collided with unrelated files of the same name elsewhere in the Drive, reporting sixteen false disagreements; now matched on name AND exact byte size. NOTHING LOCAL DELETED — that is filed as one of the four acts and waits on Nick.)
Definition of done: her words resolve to one project, or refuse and name the candidates; never a guess
Proof: the relevant item
Verified: 2026-09-16 (100%, 25 checks including that every advertised alias resolves to its own project and no two projects claim a confusable name. Live: "the meadow site" resolves; "the site" refuses and names both the Meadow site and the Website Reskin. One real failure caught: ordinary phrasing did not resolve because "can" and "you" were not treated as filler.)
Definition of done: conflict copies and duplicates are reaped on a schedule; unique content cannot be deleted
Proof: the relevant item and the relevant item
Verified: 2026-09-16 (100%, 28 checks. The safety property is structural: a file is removable only when a byte-identical copy provably survives IN THE SAME PROJECT. A file NAMED like a conflict copy whose content is unique is reported, never removed — asserted directly. A real defect was caught before anything was applied: the first version grouped content across the whole drive, so all ten candidate removals were CROSS-project and would have deleted a shared logo or font from one project because another had it. Scheduled daily; live run reports the drive clean.)
Definition of done: each capability's harness fails against the unbuilt code before it passes
Proof: each harness run before its fix — recorded per step below
Verified: 2026-09-16 (100%, every one of the six builds below was proven RED first; three real defects were caught this way and are named in their own lines.)
Definition of done: the sweep discovers the creative project, and every project it found before is still found
Proof: the relevant item
Verified: 2026-09-16 (100%, discovery went from 12 to 47 with all 12 originals kept, no duplicates, every path real. Proven end to end rather than asserted: on its first run covering this project Neeko raised a genuine finding against THIS plan file — no pick-up marker, 57.6KB block — the marker was added and the finding cleared on the next run.)
Definition of done: the causes are detected, healed where possible, surfaced where not, without depending on git
Proof: the relevant item
Verified: 2026-09-16 (100%, 27 red-first checks, independently verified on six criteria by a separate Sonnet session including a sabotage test that went green → red → green with the working tree left clean. Installed as a the background service job every 15 minutes and at login. A real bug was caught by RUNNING it rather than trusting the tests: the entry guard compared a path to a URL and this workspace's path contains a space, so main() never ran and the command exited 0 having checked nothing.)
Definition of done: both repositories current, cleanup able to run again, free disk above the watchdog floor
Proof: the relevant item · the relevant item
Verified: 2026-09-16 (100%. Root cause: a zero-byte .git/index.lock abandoned 2026-09-11 failed every sync silently — her checkout was 5,529 commits behind and the business workspace 1,812. Both current. Automatic cleanup had also been refusing to run since 2026-09-15 behind a stale gc.log. 8GB reclaimed from two leftover worktrees after pushing their uncommitted work to the cloud first; free disk went from 17GB to 29GB and cleanup completes again.)