Data integrity
Provenance types, fixture isolation, idempotency, and failure behavior.
#Typed provenance
Financial selectors attach source type, origin, source time, receipt time, cache TTL, and derivation.
#Source audit
npm run audit:data scans production roots for fixture/mock/demo imports and random financial generators. Tests remain isolated.
#Database integrity
Observation uniqueness and decision primary keys enforce idempotency. SQLite quick_check is part of operational diagnosis.
#Fail closed
API errors, stale data, halts, and missing benchmarks withhold model output instead of substituting a value.