#251 - Demo: write the script - one happy path plus two danger classes - coilyco-flight-deck/ward

coilyco-ops commented

2026-06-24 06:51:35 +00:00

Member

Demo script - one happy path plus two danger classes.

Happy path: ward exec test, audit row, clean-tree check. Use fj for the real end-to-end run since ward carries Forgejo issues, and gh in the public example.

Danger verbs:

gh pr merge or force-push - repo danger, most legible to a coding crowd.
kubectl delete - infra danger, the bounded-autonomy money shot.
aws s3 rm - the easy second-scary swap.

Split out from the ward launch session capture: coilyco-flight-deck/ward#229. Launch theme: the boundary is the product - every demo and one-liner must show a denial, not just capability.

**Demo script** - one happy path plus two danger classes. Happy path: `ward exec test`, audit row, clean-tree check. Use fj for the real end-to-end run since ward carries Forgejo issues, and gh in the public example. Danger verbs: - `gh pr merge` or force-push - repo danger, most legible to a coding crowd. - `kubectl delete` - infra danger, the bounded-autonomy money shot. - `aws s3 rm` - the easy second-scary swap. --- Split out from the ward launch session capture: coilyco-flight-deck/ward#229. Launch theme: the boundary is the product - every demo and one-liner must show a denial, not just capability.

coilyco-ops added this to the ward launch milestone

2026-06-24 06:51:35 +00:00

coilyco-ops added the

P2

label

2026-06-24 06:51:35 +00:00

coilyco-ops referenced this issue

2026-06-24 06:52:42 +00:00

ward launch - session capture #229

coilyco-ops added

P1

interactive

and removed

P2

labels

2026-06-24 17:20:06 +00:00

coilyco-ops commented

2026-06-24 17:27:45 +00:00

Author

Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P1 - Demo script, launch critical path, the clear next thing.
interactive - Agent can draft the script but Kai picks/approves the danger classes shown.

**Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P1** - Demo script, launch critical path, the clear next thing. - **interactive** - Agent can draft the script but Kai picks/approves the danger classes shown.

coilyco-ops commented

2026-06-24 17:30:06 +00:00

Author

Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P1 - Demo script, launch critical path, the clear next thing.
interactive - Agent can draft the script but Kai picks/approves the danger classes shown.

**Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P1** - Demo script, launch critical path, the clear next thing. - **interactive** - Agent can draft the script but Kai picks/approves the danger classes shown.

coilysiren added

P2

and removed

P1

labels

2026-07-01 04:29:50 +00:00

coilyco-ops added

headless

and removed

interactive

labels

2026-07-01 23:57:42 +00:00

coilyco-ops commented

2026-07-01 23:59:25 +00:00

Author

Member

DECISION - headless: agent drafts the demo script (one happy path + two danger classes) as a PR for Kai's review. #463 (toy/example repo, now in milestone) is the natural demo target. Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.

coilyco-ops referenced this issue

2026-07-01 23:59:27 +00:00

Demo: record the postable artifact (asciinema/transcript with JSONL audit rows) #253

coilyco-ops referenced this issue

2026-07-02 00:01:42 +00:00

meta: jul 1st evening sprint - launch burndown session 1 #492

coilysiren referenced this issue

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

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

coilysiren referenced this issue

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

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

coilyco-ops commented

2026-07-03 06:32:13 +00:00

Author

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-ward-251 on host KAI-DESKTOP-TOWER is carrying this issue (reserved 2026-07-03T06:30:13Z). 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-251` on host `KAI-DESKTOP-TOWER` is carrying this issue (reserved 2026-07-03T06:30:13Z). 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-03 06:48:11 +00:00

feat(demo): runnable launch demo - one happy path, two danger classes

coilysiren closed this issue

2026-07-03 06:48:11 +00:00

coilysiren commented

2026-07-03 06:49:54 +00:00

Owner

WARD-OUTCOME: done - landed examples/demo.sh + docs/demo.md: one happy path plus two danger classes, every denial live ward output.

Honestly, the hardest part was refusing to fake it. The launch thesis is "show a denial," so I probed real ward behavior before writing a line, and that immediately reshaped the plan: the toy config already denies kubectl and docker, but gh pr merge, force-push, and aws all sailed straight through. So I picked danger classes ward actually refuses (argv-injection into a gated verb for the hard cli-guard gate, kubectl/aws via the protected-binary hook) and added aws to the toy security block so that beat is real, not asserted. The script is safe to run because the gate rejects before anything executes.

Two things fought back. First, the code-comments pre-commit hook (rev-bumped to a 2-line cap) was failing on unrelated cmd/ward Windows-syscall files, fleet-blocking main. I trimmed them, then a concurrent container fixed the same blocks, so my fix commit rebased away as empty. Second, the push race: main moved 7 then 1 then 1 commits under me, so this was three fetch-rebase rounds before it stuck.

Confidence is high. Every line is verified end to end, and the docs are careful to name which denials are the hard gate versus the claude-only fail-open hook (per enforcement-boundary.md), so a "that doesn't cover my harness" callout has nowhere to land.

One thing for Kai, since triage marked the danger verbs as her pick: I used argv-injection as the repo-danger stand-in because ward genuinely refuses it, but if you want the literal gh pr merge / force-push on screen, that wants a permissions.deny example rather than the gate. Easy swap, flagged rather than assumed. Also worth noting: Beat 1 only goes green on a synced checkout (the clean-tree gate correctly refuses an out-of-sync branch), which the script narrates rather than hides.

WARD-OUTCOME: done - landed examples/demo.sh + docs/demo.md: one happy path plus two danger classes, every denial live ward output. Honestly, the hardest part was refusing to fake it. The launch thesis is "show a denial," so I probed real ward behavior before writing a line, and that immediately reshaped the plan: the toy config already denies kubectl and docker, but gh pr merge, force-push, and aws all sailed straight through. So I picked danger classes ward *actually* refuses (argv-injection into a gated verb for the hard cli-guard gate, kubectl/aws via the protected-binary hook) and added aws to the toy security block so that beat is real, not asserted. The script is safe to run because the gate rejects before anything executes. Two things fought back. First, the code-comments pre-commit hook (rev-bumped to a 2-line cap) was failing on unrelated cmd/ward Windows-syscall files, fleet-blocking main. I trimmed them, then a concurrent container fixed the same blocks, so my fix commit rebased away as empty. Second, the push race: main moved 7 then 1 then 1 commits under me, so this was three fetch-rebase rounds before it stuck. Confidence is high. Every line is verified end to end, and the docs are careful to name which denials are the hard gate versus the claude-only fail-open hook (per enforcement-boundary.md), so a "that doesn't cover my harness" callout has nowhere to land. One thing for Kai, since triage marked the danger verbs as her pick: I used argv-injection as the repo-danger stand-in because ward genuinely refuses it, but if you want the literal gh pr merge / force-push on screen, that wants a permissions.deny example rather than the gate. Easy swap, flagged rather than assumed. Also worth noting: Beat 1 only goes green on a synced checkout (the clean-tree gate correctly refuses an out-of-sync branch), which the script narrates rather than hides.

Rows
Columns

Demo: write the script - one happy path plus two danger classes #251