Skip to main content

0.2.1 — the first command needs no arguments

· 2 min read
0.2.1 — the first command needs no arguments | AEPA project describes itself once in .engineering/project.yaml and the CLI finds it. Projects may add principles and profiles of their own, merged over the protocol tree's — without being able to shed what it enforces.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

Source-owned field note · website/blog/2026-08-20-0201-project-discovery.md · revision 8f106fad0926

An adopting team's very first command should not require them to have read the manual. This release makes a project describe itself once, in .engineering/project.yaml, and the CLI find it.

0.2.0-wave-3 — a backend can prove it, instead of claiming it

· 2 min read
0.2.0-wave-3 — a backend can prove it, instead of claiming it | AEPSixteen black-box conformance suites over the command and query surfaces, three levels — and a deliberately broken backend the suites are checked against, because a suite that passes everything tells you nothing.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

Source-owned field note · website/blog/2026-08-20-0141-conformance-and-the-domain-profiles.md · revision 8f106fad0926

Any storage backend can say it implements the contract. This release is about the difference between saying and proving.

0.2.0-wave-2 — every object addressable, every mutation auditable

· 2 min read
0.2.0-wave-2 — every object addressable, every mutation auditable | AEPOpaque identity, logical locators, monotonic revisions, and one command boundary with idempotent replay and conflicts that refuse rather than merge. Plus the audit record that keeps the refusals.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

Source-owned field note · website/blog/2026-08-20-0102-identity-and-the-interaction-contract.md · revision 8f106fad0926

A protocol that decides things has to be able to say which thing it decided about, and who asked. This release makes every object addressable and every mutation auditable.

0.2.0-wave-1 — a task becomes a plan

· 3 min read
0.2.0-wave-1 — a task becomes a plan | AEPThe first release you can run against something. A task plus a document tree produces a plan, evidence decides what may be done and whether the work is finished, and a capability decision names the rule that decided it.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

Source-owned field note · website/blog/2026-08-20-0028-the-execution-core.md · revision 8f106fad0926

0.1.0 was a vocabulary. This is the first release where a question goes in and an answer comes out: a task plus a document tree produces a plan, and evidence decides both what may be done and whether the work is finished.

0.1.0 — the model everything else is built on

· 3 min read
0.1.0 — the model everything else is built on | AEPThe first release is a vocabulary, not a feature. Typed identifiers, a three-valued predicate language, capabilities that default to deny, evidence that carries its provenance, and documents read with syntax separated from semantics.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

Source-owned field note · website/blog/2026-08-19-2337-domain-model-and-document-layer.md · revision 8f106fad0926

The first release does nothing you can run against your own repository. It is the vocabulary everything after it is written in, and the decisions taken here are the ones that could not be changed later without changing what the tool means.