ANDM Conformance
The module hub is the unit of anti-dark-code conformance.
A conformant module hub is a governed software module whose code, specification,
test results, and commit lineage are co-versioned, attributable, and reconstructible.
Required spokes
Spoke type
Required
Conformance requirement
code
Yes
Canonical, versioned implementation artifact. A code update without a corresponding spec update is a conformance violation.
spec
Yes
Markdown definition module. Must include purpose, public interface, contracts, data stores, emitted outputs, invariants, and failure modes.
test-results
Yes
Structured test output against the current code/spec batch. Test results tied to any prior code/spec state are stale and non-conformant.
commit-record
Auto
Auto-created structural primitive. Records actor, batch, operations, spoke CUs, and upward correlation references.
Binary spec-spoke test
If the code spoke were deleted, could an agent regenerate the module from the spec spoke alone? If not, the spec is not conformant.
Minimum checklist
- Hub belongs to exactly one immutable domain.
- Hub manifest declares spoke inventory and ANDM conformance status.
- Every governed operation has an accountable human principal.
- Agent-authored CUs identify both agent id and authorizing human principal.
- Code and spec are co-versioned in the same governed batch when implementation changes.
- Test-results validate the current code/spec batch.
- Commit records link downward to spoke CUs and upward to hub/domain records.
- Rollback, correction, or repair is a new append, not a rewrite or deletion.
- The artifact lineage is sufficient to reconstruct the governed module from genesis.
Blocking conditions
In ANDM-enforcing implementations, non-conformance should block the next governed operation.
The audit record is not an after-the-fact receipt. It is the authorization token for the next
unit of work.
- Missing spec spoke.
- Code update without corresponding spec update.
- Test-results missing, stale, or not linked to spec assertions.
- Missing human principal on an agent-authored operation.
- Commit record absent, mutable, or not cryptographically sealed.
- Hub/domain membership ambiguity.
What conformance does not claim
ANDM conformance does not itself constitute a formal CMMI appraisal, legal certification,
or claim that the software is defect-free. It establishes the governed infrastructure needed
to make comprehension, authorization, quantitative management, and reconstruction auditable
as native properties of the development process.
General Reasoning, Inc.
· Birmingham, Alabama · Open standard · CC BY-ND 4.0 · 2026
Standard identifier: ANDM-v1.0 · CMMI mapping: CMMI-DEV v2.0
Audit substrate reference: Chandra Protocol
Enterprise inquiries: inquiries@genreason.com
