README carries a front-page denial demo that the 2026-07-01 triage explicitly declined - relocate it #502

New issue

Closed

opened 2026-07-02 03:01:43 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-02 03:01:43 +00:00

Owner

What

README lines ~32-42 on main show a refusal demo ('the interesting demo is not what it runs - it is what it refuses', with two literal refused - transcript examples). The 2026-07-01 triage DECISION on ward#444 explicitly declined a front-page denial demo for the README. The section arrived via ward#427's run (commit 9b70980), which regrew the README beyond its dispatched scope, citing the ward#255 launch doctrine ('every demo must show a denial'). The #444 epic run kept to its opening-fix scope and never removed it, so the declined section persists against the triage record.

Deliverable

Relocate, do not delete: move the refusal-demo content into the demo/exec docs where it is wanted (docs/exec-verb.md or the ward#251 demo-script surface can host it - #251's approved script wants exactly these danger-class examples).
README keeps its concrete what-it-does lead without the demo section, per the triage decline.

Escape hatch

If Kai has changed her mind and wants the denial demo on the front page after seeing it live, close this as wontfix with a comment - the triage record is the only authority this ticket leans on.

Cross-refs

ward#444 - the triage DECISION recording the decline.
ward#427 - the run that added the section out of scope.
ward#255 / ward#251 - the launch doctrine and demo script the content serves.

Filed by Claude Code (Fable) during the ward#492 burndown session.

## What README lines ~32-42 on main show a refusal demo ('the interesting demo is not what it runs - it is what it refuses', with two literal `refused -` transcript examples). The 2026-07-01 triage DECISION on ward#444 explicitly declined a front-page denial demo for the README. The section arrived via ward#427's run (commit `9b70980`), which regrew the README beyond its dispatched scope, citing the ward#255 launch doctrine ('every demo must show a denial'). The #444 epic run kept to its opening-fix scope and never removed it, so the declined section persists against the triage record. ## Deliverable * Relocate, do not delete: move the refusal-demo content into the demo/exec docs where it is wanted (docs/exec-verb.md or the ward#251 demo-script surface can host it - #251's approved script wants exactly these danger-class examples). * README keeps its concrete what-it-does lead without the demo section, per the triage decline. ## Escape hatch If Kai has changed her mind and wants the denial demo on the front page after seeing it live, close this as wontfix with a comment - the triage record is the only authority this ticket leans on. ## Cross-refs * ward#444 - the triage DECISION recording the decline. * ward#427 - the run that added the section out of scope. * ward#255 / ward#251 - the launch doctrine and demo script the content serves. Filed by Claude Code (Fable) during the ward#492 burndown session.

coilyco-ops commented

2026-07-02 03:11:38 +00:00

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-ward-502 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T03:11:35Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-ward-502` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T03:11:35Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-02 03:14:41 +00:00

docs: relocate the front-page denial demo off the README (closes #502)

coilysiren closed this issue

2026-07-02 03:14:41 +00:00

coilysiren commented

2026-07-02 03:14:53 +00:00

Author

Owner

WARD-OUTCOME: done - moved the "gate says no" denial demo off the README into a new docs/gate-demo.md, wired from exec-verb.md and the docs index.

Straightforward relocation, but it fought back once. My first instinct - fold the two refusal transcripts into exec-verb.md - tripped the catalog-doc-size cap (80 lines / 4000 chars): the code block alone made it impossible to keep exec-verb.md under budget. That turned out to be a good forcing function. A dedicated docs/gate-demo.md is the better home anyway, since it matches what the issue actually asked for (the ward#251 demo surface / ward#255 launch doctrine wanted exactly these danger-class examples), so exec-verb.md keeps a one-line pointer instead of swelling.

Confident in the result: README keeps its concrete what-it-does lead with no front-page demo per the triage decline, the content is preserved and discoverable, and the full pre-commit suite plus build are green. Clean merge with main (no conflicts). No follow-ups worth filing - if #251's demo-script work later wants to inline these transcripts, gate-demo.md is a ready source.

WARD-OUTCOME: done - moved the "gate says no" denial demo off the README into a new docs/gate-demo.md, wired from exec-verb.md and the docs index. Straightforward relocation, but it fought back once. My first instinct - fold the two refusal transcripts into exec-verb.md - tripped the catalog-doc-size cap (80 lines / 4000 chars): the code block alone made it impossible to keep exec-verb.md under budget. That turned out to be a good forcing function. A dedicated docs/gate-demo.md is the better home anyway, since it matches what the issue actually asked for (the ward#251 demo surface / ward#255 launch doctrine wanted exactly these danger-class examples), so exec-verb.md keeps a one-line pointer instead of swelling. Confident in the result: README keeps its concrete what-it-does lead with no front-page demo per the triage decline, the content is preserved and discoverable, and the full pre-commit suite plus build are green. Clean merge with main (no conflicts). No follow-ups worth filing - if #251's demo-script work later wants to inline these transcripts, gate-demo.md is a ready source.