Skip to content

The local-first proof-gated control plane for multi-agent teams. πŸ¦€

License

Notifications You must be signed in to change notification settings

RomanAlexanderW/decapod

Β 
Β 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

1,115 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

πŸ¦€

cargo install decapod && decapod init

Decapod
The governance runtime for AI coding agents.

Local-first, repo-native, and built for verifiable delivery.

CI crates.io License: MIT Ko-fi


Why Decapod 🧠

AI coding agents can write code fast. Shipping it safely is the hard part.

Decapod gives agents a consistent operational contract: guided execution, enforceable boundaries, and auditable completion signals. It replaces "looks done" with explicit outcomes.

Decapod is invoked by agents; it never runs in the background. It is a single executable binary that provides deterministic primitives:

  • Retrieve canon (constitution .md fragments) as context.
  • Provide authoritative schemas for structured state (todos, knowledge, decisions).
  • Run deterministic validation/proof gates to decide when work is truly done. Example gate: forbid direct pushes to protected branches β€” fails if the agent has unpushed commits on main.

AGENTS.md stays tiny (entrypoint). OVERRIDE.md handles local exceptions. Everything else is pulled just-in-time.

Traces: .decapod/data/traces.jsonl. Bindings: context.bindings. Architecture-agnostic (not coupled to a specific OS or CPU).

Recent independent research confirms this design direction: Evaluating AGENTS.md (Gloaguen et al., ETH SRI, 2026; AgentBench repo) found that LLM-generated context files tend to reduce agent performance while increasing cost by over 20 %; human-written minimal requirements can help slightly. Decapod was built independently and without knowledge of ETH SRI's AgentBench research or this paper.

β˜• Like Decapod? Buy us a coffee on Ko-fi πŸ’™

Assurance Model βœ…

Decapod is built around three execution outcomes:

  • Advisory: guidance toward the next high-value move.
  • Interlock: hard stops for unsafe or out-of-policy flow.
  • Attestation: structured evidence that completion criteria were met.

Operating Model βš™οΈ

Human Intent
    |
    v
AI Agent(s)  <---->  Decapod Runtime  <---->  Repository + Policy
                         |    |    |
                         |    |    +-- Interlock (enforced boundaries)
                         |    +------- Advisory (guided execution)
                         +------------ Attestation (verifiable outcomes)

Features ✨

  • Agent-native CLI and RPC surface for deterministic operation.
  • Guided project understanding through structured prompting.
  • Standards-aware execution aligned with project policy.
  • Workspace safety for isolated implementation flow.
  • Validation and completion gates with explicit pass/fail outcomes.
  • Multi-agent-ready orchestration surface for tooling integrations.

Getting Started πŸš€

cargo install decapod
decapod init

Then use your agents as normal. Decapod works on your behalf from inside the agent.

Learn more about the embedded constitution.

Override constitution defaults with plain English in .decapod/OVERRIDE.md.

Contributing 🀝

git clone https://github.com/DecapodLabs/decapod
cd decapod
cargo build
cargo test
decapod validate

Documentation πŸ“š

Support πŸ’–

License πŸ“„

MIT. See LICENSE.

About

The local-first proof-gated control plane for multi-agent teams. πŸ¦€

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • Rust 99.9%
  • Dockerfile 0.1%