Provenance tracking, validation trust levels, release artifacts, and content integrity — the trust chain from physics constants to simulation outputs.
Ananke models physics with numbers drawn from the real world — bone fracture thresholds, fire heat flux, plague mortality rates. Data governance is the system that tracks where those numbers came from, how well they've been validated, and how trustworthy each API surface is as the library evolves.
Three layers work together:
src/ is traceable to a peer-reviewed dataset or engineering standard. Validation reports in docs/validation-*.md document each source and the expected range the simulation must hit.STABLE_API.md classifies every exported symbol as Tier 1 (stable, semver-guarded), Tier 2 (experimental, may change without major bump), or Tier 3 (planned, not yet implemented). Hosts can decide what risk level they accept.CHANGELOG.md records every change. Content packs carry provenance.sha256 checksums for tamper detection.Use the provenance checklist below to assess readiness of any release before integrating it into a production pipeline.
Data governance in Ananke spans three layers: physics constants (validated against real-world datasets), API stability (covered by semantic versioning and the Tier 1/2/3 contract), and content integrity (provenance and checksums in content packs and validation reports).
docs/validation-*.md)npm run run:validation)STABLE_API.md with Tier 1/2/3 annotationsprovenance.sha256 fielddocs/validation-*.md — each constant has a corresponding validation report with real-world source data.npm run test:coverage to verify coverage thresholds locally before a release.provenance.sha256 in a pack manifest against a recomputed hash of the pack's canonical JSON.test/fixtures/ and import it in a determinism test.