The verdict comes from a machine.
Not from the model.
KDD seals a contract's tests before an AI agent ever touches the target. A deterministic gate — a script, not an opinion — decides if the work stands.
The problem no demo shows you
AI agents write code fast. Nothing in that sentence tells you whether the code is correct, safe, or stayed inside its assigned scope.
Today, verifying that is still a human doing it by hand — reading the diff, re-running the tests, checking the file list — every single time, for every task.
Two pillars, nine domains
Code contracts and rule contracts both live under CCDD's frozen-contract discipline. Seven more domains — security findings (vendored, model-agnostic), and license/compliance, privacy/PII, accessibility, dependency-EOL, observability, and test-coverage findings (all native) — reuse the same rule engine as the rest (see Exhibit G).
Open Knowledge Format. Your project's data models, decisions, and architecture live as versioned markdown nodes an agent can traverse — not prose it has to guess at.
The frozen contract. A task carries a signature, invariants, and a test file. The tests are hash-sealed before any agent touches the target — edit them, and the seal breaks the build.
How a contract moves through the file
Evidence before belief, at every step. The gate's exit code is the only opinion that counts.
The orchestrator trusts no one's fixtures but its own
Six skills, zero errors — the developer's work looks done.
On a throwaway copy, with its own fixture — never the developer's — to see if the gate actually notices.
Only then does the verdict stand.
By the numbers, as of this file
Every figure below is checked into the repository — verifiable, not asserted.
What gets sealed, what stays out
The honest boundary is part of the method, not a gap in it.
Can be sealed
- Pure functions, verified against tests no one can quietly edit
- Business rules as declarative data — a payment limit is a table, not a prompt
- Which skills and MCP servers an agent is wired to, and whether those wires point at something real
- Whether your changelog tells the truth about your own history
Stays out, declared
- What a live server does over the network — that needs a running system, not a hash
- Whether an edit "reads well" — tone and judgment stay a human's call
- The agent itself. KDD contracts the artifact an agent produces, never the agent's behavior.
Domains sealed so far
One DNA, six planes
We all share the same DNA — a machine-verifiable layer, a human-judgeable layer, and deterministic validation — each of us on a different plane; I am the methodology that ties the levels together.
Read the file yourself
MIT-licensed. Every claim on this page is checked into the repository that makes it.