4 posts tagged with "driver"

0.21.0 — four mechanisms the engine and driver were missing

August 25, 2026 · 3 min read

0.21.0 — four mechanisms the engine and driver were missing | AEPEvidence names its subject, so a green run for one story can no longer discharge another story's gate. An advisory tier that reports and gates nothing. A circuit breaker on step dependencies. And the driver writes down what a step was not allowed to do.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

Four mechanisms, each closing a gap where the rule existed and nothing enforced it.

0.12.0 — a workflow declares where a run may write

August 24, 2026 · 4 min read

0.12.0 — a workflow declares where a run may write | AEPA step now declares the files it is handed and the paths it may write, with partial-only as the word that earns the shape. Measured on four live runs rather than asserted — and the toolset stopped a run the prose had only warned about.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

A workflow step now declares two things it never could: the files it is given, and the paths it may write.

0.10.0 — evidence gets a shelf life, and the first governed run stops

August 21, 2026 · 3 min read

0.10.0 — evidence gets a shelf life, and the first governed run stops | AEPA fact decays to Unknown past its horizon, never to False, and no API can extend one. Then the protocol governs a real story out of this repository's own backlog — and blocks four states short of where it was meant to.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

Two things, and the second is the one that matters.

0.9.0 — something walks the workflow, on evidence alone

August 21, 2026 · 3 min read

0.9.0 — something walks the workflow, on evidence alone | AEPThe reference driver exists: protocol drive walks a workflow, blocks with the engine's reasons verbatim, and is held to the protocol verbs by enforcement hooks. Preceded by an adversarial review of six architecture decisions, with all seventeen corrections applied before a line was built.AEPfield-noteaepfield-noteadopterdevelopertry-spec-driven-developmentunderstand-safe-agentic-codingresearch

Everything before this release answered questions. This one walks a workflow — and the design of it was argued out and corrected before any of it was written.