Make “done” executable
Add static, security, and test gates to every pull request. Encode the first ten unwritten team rules.
IMPLEMENTATION ROADMAP
Five proposed phases from the October 2026 paper. Each phase has an exit gate.
TEAM ADOPTION / NOT A BIG-BANG MIGRATION
The paper separates product implementation from team adoption. A Scrum team keeps each existing ceremony until its ADD replacement produces better evidence.
Add static, security, and test gates to every pull request. Encode the first ten unwritten team rules.
Choose a low-risk area, approve Given/When/Then criteria, and let agents work through controlled pull requests.
Introduce model tiers, per-spec budgets, failure review, and a senior exception rotation.
Move remaining work to the spec queue. Derive state from gates and replace sprint rituals with ADD reviews.
THE STARTING POINT
The paper identifies authorization, idempotency, optimistic concurrency, tickets, telemetry, HTTP, and gRPC as existing building blocks. The phases below describe the additional ADD work.
| Proposed phase | Scope | Exit gate |
|---|---|---|
| 0 · Agent-safe core | Agent principals, OAuth 2.1, task permissions, and leases. | No agent write without a token and a lease. |
| 1 · Agent surface | A stateless MCP server, delegation, and cost recorded on writes. | An agent ships a real ticket end to end. |
| 2 · Specifications | Import spec folders and link tasks to approved specifications. | Every task traces to an approved spec. |
| 3 · Quality gates | Ingest GitHub checks and derive work state from gate results. | Status is evidence-driven. |
| 4 · Orchestration | Tier routing and cost aggregation per specification. | Cost per spec is reported and tasks are routed by tier. |
FIRST MILESTONE
An agent claims a RustGrid ticket through an authenticated API, performs the work, attaches its evidence, and completes the task with an audit trail. This is the first proposed proof point.
Keep the core deterministic. Put model calls outside it. Add task-scoped permissions and leases before expanding autonomy.
Explore the developer foundationTHE NEXT WAY TO BUILD
Start with RustGrid’s execution foundation. Build toward a delivery system governed by specs, gates, and clear ownership.