EPIC: Engineering standards and deterministic review

[kmosoti]

Outcome

Core code follows deterministic standards for contracts, protocols, boundaries, state, idempotency, complexity, observability, and source provenance.

Scope

• Engineering standards as Definition of Done
• Service contract template
• Architecture boundary rules
• Complexity budget notes
• State transition validator pattern
• Result object standard
• Adapter contract test strategy
• Observability field standard
• Idempotency review
• Review score rubric

Source Docs

• docs/07-engineering-standards.md
• docs/03-kanban-board.md: Epic N

Done When

• MVP core cards include contract and complexity expectations.
• External dependencies sit behind protocols/adapters.
• Pure logic is testable without network, filesystem, database, or LLM calls.
• Generated learning content preserves source provenance.