This directory contains Intent Contracts as defined in ADR-006.
An Intent Contract is a human-readable, unambiguous declaration of:
- what a non-trivial class is meant to do,
- what it must never do,
- its invariants,
- and its failure semantics.
Intent Contracts are architectural artifacts. They are not implementation documentation.
An Intent Contract is mandatory for:
- Core domain classes
- Architectural boundary classes
- Orchestration components
- State-owning components
- Classes that enforce invariants
- Classes that modify semantics or transformation
Trivial value objects and pure utility functions do not require one.
Each contract must define:
- Purpose
- Responsibility Boundary
- Invariants
- Explicit Non-Responsibilities
- Failure Semantics
- Observable Effects (if applicable)
Contracts must be clear enough that:
- Tests (ADR-005) can be derived from them.
- Architectural violations can be detected.
- Silicon-based agents cannot reinterpret intent (ADR-007).
UNFAOPostProcessorManager.md— Pipeline orchestration manager (read → transform → validate → save)
Intent Contracts are governed by:
- ADR-006 (Intent Contracts for Non-Trivial Classes)
- ADR-003 (Authority of Declarations)
- ADR-005 (Testing Doctrine)
If a class changes meaning, its Intent Contract must be updated.