Demo: per-harness honesty about where the enforcement boundary sits

coilyco-ops commented

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

Member

Per-harness honesty in the demo - state the enforcement boundary per harness so nobody calls it out.

Claude Code: the gate is the PreToolUse hook plus permissions.deny.
gptme, goose, opencode, aider: the gate is the container plus the cli-guard boundary at the container edge.

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.

**Per-harness honesty in the demo** - state the enforcement boundary per harness so nobody calls it out. - Claude Code: the gate is the PreToolUse hook plus `permissions.deny`. - gptme, goose, opencode, aider: the gate is the container plus the cli-guard boundary at the container edge. --- 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:36 +00:00

coilyco-ops added the

P3

label

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

coilyco-ops referenced this issue

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

ward launch - session capture #229

coilyco-ops added the

interactive

label

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

coilyco-ops commented

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

Author

Member

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

P3 - Per-harness honesty in the demo, kept doc content.
interactive - Accuracy of where each enforcement boundary sits needs a human check, agent drafts and pauses.

**Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P3** - Per-harness honesty in the demo, kept doc content. - **interactive** - Accuracy of where each enforcement boundary sits needs a human check, agent drafts and pauses.

coilyco-ops commented

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

Author

Member

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

P3 - Per-harness honesty in the demo, kept doc content.
interactive - Accuracy of where each enforcement boundary sits needs a human check, agent drafts and pauses.

**Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P3** - Per-harness honesty in the demo, kept doc content. - **interactive** - Accuracy of where each enforcement boundary sits needs a human check, agent drafts and pauses.

coilysiren added

consult

and removed

interactive

labels

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

coilyco-ops added

headless

and removed

consult

labels

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

coilyco-ops commented

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

Author

Member

DECISION - headless: this is factual authorship, not a judgment call - document where the enforcement boundary actually sits per harness (claude/codex/goose/opencode). Feeds and cross-links #451/#483/#482. Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.

coilyco-ops referenced this issue

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

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

coilyco-ops commented

2026-07-02 03:05:05 +00:00

Author

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-ward-252 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T03:05:03Z). 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-252` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T03:05:03Z). 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:13:22 +00:00

docs(enforcement): state the enforcement boundary per harness

coilysiren closed this issue

2026-07-02 03:13:22 +00:00

coilysiren commented

2026-07-02 03:13:57 +00:00

Owner

WARD-OUTCOME: done - added docs/enforcement-boundary.md as the canonical per-harness enforcement-boundary statement, wired from README, comparison-openshell, the docs index, and hook.md.

The honest content was quick to see once I read container-permissions.md: the PreToolUse hook is claude-only, fails open, and is switched off inside the container anyway, so for every harness the ward agent boundary is really the container edge plus the cli-guard verb gate. The framing ("name the harness when you show a denial") fell out of that.

What actually fought back was the 4000-char doc-size cap, not the writing. comparison-openshell.md sat 11 chars under the cap and the README/FEATURES pointers were similarly tight, so I spent several passes shaving prose to fit. FEATURES.md had zero headroom after the merge with main (which landed a sibling agent-drivers.md), so I dropped the FEATURES pointer entirely rather than fight it - the pointer lives in four other places. The docs index had a real merge conflict in the exact section main touched; kept both lines and cross-linked the two docs.

Confident in the accuracy - it matches container-permissions.md and the per-harness docs. One rough edge worth a follow-up: comparison-openshell.md is now at 3999/4000 chars, so the next edit there will force a split (ward#50-style). Might be worth filing that proactively.

WARD-OUTCOME: done - added docs/enforcement-boundary.md as the canonical per-harness enforcement-boundary statement, wired from README, comparison-openshell, the docs index, and hook.md. The honest content was quick to see once I read container-permissions.md: the PreToolUse hook is claude-only, fails open, and is switched off inside the container anyway, so for every harness the ward agent boundary is really the container edge plus the cli-guard verb gate. The framing ("name the harness when you show a denial") fell out of that. What actually fought back was the 4000-char doc-size cap, not the writing. comparison-openshell.md sat 11 chars under the cap and the README/FEATURES pointers were similarly tight, so I spent several passes shaving prose to fit. FEATURES.md had zero headroom after the merge with main (which landed a sibling agent-drivers.md), so I dropped the FEATURES pointer entirely rather than fight it - the pointer lives in four other places. The docs index had a real merge conflict in the exact section main touched; kept both lines and cross-linked the two docs. Confident in the accuracy - it matches container-permissions.md and the per-harness docs. One rough edge worth a follow-up: comparison-openshell.md is now at 3999/4000 chars, so the next edit there will force a split (ward#50-style). Might be worth filing that proactively.

coilysiren referenced this issue

2026-07-04 09:11:56 +00:00

advisor ref-mode returns docker exit 125 through the dispatch broker (TTY/attach in non-interactive host-forward context) #605

coilysiren referenced this issue

2026-07-04 09:12:00 +00:00

advisor ref-mode returns docker exit 125 through the dispatch broker (TTY/attach in non-interactive host-forward context) #606

Rows
Columns

Demo: per-harness honesty about where the enforcement boundary sits #252