Adr deterministic generator contract adopt 2026 04 24
Decision
Adopt deterministic-generator-contract as a mandatory standard for all CAS generators.
Context
- Source:
aw-ideas-to-life-cas-2026-04-24-02 - Finding:
ALIGN-005 - AEM Source:
aem-ideas-to-life-cas-2026-04-26-01 - Decision classification:
system
Problem
CAS generators were producing inconsistent outputs across runtimes and model executions because naming, versioning, and persistence rules were not explicit. This created drift in generated artefacts and made repeated execution difficult to reason about.
Rationale
The contract is required to:
- make generator outputs repeatable
- enforce explicit naming and versioning
- require persistence and date scoping
- reduce nondeterministic behaviour across model changes
- make generator output reviewable and traceable
Next Step
- Enforce the contract in generator prompts.
- Validate compliance through alignment checks.
- Update related artefacts that depend on generator output format or persistence rules.
Traceability
| Artefact | ID |
|---|---|
| Architecture Work | aw-ideas-to-life-cas-2026-04-24-02 |
| Alignment Finding | ALIGN-005 |
| AEM | aem-ideas-to-life-cas-2026-04-26-01 |
| Pattern | deterministic-generator-contract |
| Signal | generator-contract-required |