Add ward goose - audited passthrough to the goose binary #118

Closed
opened 2026-06-17 21:24:23 +00:00 by coilysiren · 0 comments
Owner

Why

The goose-triage / goose-json tooling in agentic-os shells out to the bare goose binary (scripts/goose_json.py, goose run --no-profile --quiet --no-session --max-turns 1 --output-format json --recipe <tmp>). To route the whole setup through ward, goose needs an audited ward surface.

Why a passthrough, not a ward.yaml exec verb

An exec repo verb re-runs the clean+synced-tree gate and writes an audit row on every call - that's 90+ rows per triage run, and it aborts mid-run the moment a release bump lands and the tree goes "1 behind". A passthrough subcommand (like ward git / ward pkg) audits without the repo-verb gate, so it survives a mid-run tree change.

Asked-for surface

ward goose <args...> - thin audited passthrough to the goose binary, forwarding all args verbatim (must handle --recipe <path>, --output-format json, etc.).

Context: agentic-os goose-triage swap-to-ward (agentic-os#237).

## Why The goose-triage / goose-json tooling in agentic-os shells out to the bare `goose` binary (`scripts/goose_json.py`, `goose run --no-profile --quiet --no-session --max-turns 1 --output-format json --recipe <tmp>`). To route the whole setup through ward, goose needs an audited ward surface. ## Why a passthrough, not a ward.yaml exec verb An `exec` *repo verb* re-runs the clean+synced-tree gate and writes an audit row on **every** call - that's 90+ rows per triage run, and it aborts mid-run the moment a release bump lands and the tree goes "1 behind". A passthrough subcommand (like `ward git` / `ward pkg`) audits without the repo-verb gate, so it survives a mid-run tree change. ## Asked-for surface `ward goose <args...>` - thin audited passthrough to the goose binary, forwarding all args verbatim (must handle `--recipe <path>`, `--output-format json`, etc.). Context: agentic-os goose-triage swap-to-ward (agentic-os#237).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/ward#118
No description provided.