2 posts tagged with "adoption"

0.14 — the protocol reads a repository that already exists

August 25, 2026 · 4 min read

0.14 — the protocol reads a repository that already exists | AEPRelease 0.14.0 adds protocol reverse: four verbs that point the tooling at a repository written with none of this in mind. Three of the four write nothing, so you can run them against your own code before deciding anything.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

Every worked example on this site starts from documents that already exist. That is the wrong end for anybody deciding whether to adopt: your repository has a README, a test layout, a CI file and six years of git history, and none of it was written with a protocol in mind.

0.14.0 adds protocol reverse — four verbs that read what a repository already says about itself. Three of the four write nothing at all, which is the part that matters when you are evaluating a tool you do not trust yet: the worst case is a report you disagree with.

0.2.1 — the first command needs no arguments

August 20, 2026 · 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

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.