Disclose agents
If an AI agent helped write the code, the PR and the commit trailer say so. Every change stays attributable. No hidden AI involvement.
Humans own the merges
Agents review and recommend. A human approves and merges. Nothing merges automatically, ever.
Quality and security are gates
Not advisory on the things that matter. The intake gate fails hard. The security lens blocks on real findings.
Three ways in
CI
The govern layer. The intake gate and the review pipeline run on every PR, whoever or whatever authored it. The only mandatory surface: wire nothing else and you still have the airlock.
The CLI
Install once, then run the same deterministic gates locally, scaffold a repo with asdd init, and read a project’s activity on the read-only asdd dashboard. A spec that passes locally passes on the PR, because it is the same code.
The Goose operate kit
A ready-to-run operate layer on unmodified Goose, for projects that want the working agents and not just the gates. Optional; the standard mandates no runtime.
ASDD installs into the repository, not into a chat window, so the governance is identical for every tool that reaches it. Bring your own assistant (Claude, Goose, Cursor, Copilot, your own harness) and your own spec tool: Spec Kit, OpenSpec, or plain files. ASDD requires that a spec exists and is checked, not that a particular tool produced it.
Stewarded by the OneHill Foundation. Read why it exists, what it is, and how it works.