[ platform ]
The platform agents and codebases run on.
Route every agent through one harness, review every change with a cited intelligence team, and pay for frontier models only when a check looks like a real violation.
Platform
Agent harness
One control plane every agent runs through—identity, sandbox, constraints, and policy in a single runtime.
Scoped identity
Repos, environments, and services per agent—revoke in one place.
MCP constraints
Live decision graph constraints before an agent writes code.
Sandboxed execution
Isolated runs with a timestamped log for every action.
Policy on every step
Blocked actions cite the decision, owner, and surface.
[ platform ]
Three surfaces, one place to run agents and govern change.
Decree is not a memory layer or a bolt-on policy doc. It is the platform your agents and review workflows share: execution, intelligence, and inference routing wired together.
One control plane every agent runs through.
Scoped identity, sandboxed execution, live constraints over MCP, and policy checked against the decision graph on every action.
Five reviewers, each scoped to a role.
PM, designer, architect, security and compliance, and QA—each reading a different slice of the graph, every verdict citing a specific decision and its owner.
Always-on checks on codebases you can afford to run on everything.
Routes each check to the cheapest model that can do it, spending frontier reasoning only on likely violations.
[ agent harness ]
One control plane every agent runs through.
Scoped identity, sandboxed execution, live constraints over MCP, and policy checked against the decision graph on every action. The same plane coordinates your review agents so every verdict cites the same live decisions.
[ decision intelligence team ]
Role-scoped reviewers on every change.
PM, designer, architect, security and compliance, and QA—each reading a different slice of the graph, every verdict citing a specific decision and its owner.
Ship scope and customer commitments
This change expands billing surface beyond the Q3 commitment.
Flows, states, and interaction contracts
Checkout still assumes a single payment method per cart.
Service boundaries and data ownership
Ledger writes must stay inside payments, not the shared module.
Access, data handling, audit trail
Agent credentials for prod observability were not revoked.
Regression risk and release criteria
SLA test suite does not cover the refactored retry path.
A reviewer that cannot cite a live decision does not comment.
[ token router ]
Frontier models only when the check looks like a violation.
The token router sends each check to the cheapest model that can do it, spending frontier reasoning only on likely violations. That is what makes always-on checks on codebases affordable across every agent action and every review.
[ versus ]
A runtime with no policy.
Retrieval with no enforcement.
The platform: harness, decision intelligence team, and token router on one graph.
[ design partners ]
We are taking five.
Read-only ingestion, no payment, a direct line to the founders.