Waveframe Labs
Deterministic enforcement and provenance validation.
Layer 3 — Enforcement

CRI-CORE

CRI-CORE is the enforcement engine of the Aurora ecosystem. It transforms governance rules and workflow requirements into machine-verifiable guarantees.

Why CRI-CORE Exists

Modern research workflows rely on trust that methods were followed correctly. CRI-CORE replaces trust with verification by mechanically validating manifests, metadata, and execution logs.

Instead of asserting compliance, CRI-CORE produces cryptographically trustworthy evidence of what actually ran.

Core Capabilities

  • Validate AWO manifests for completeness and structural correctness.
  • Verify required metadata headers across all artifacts.
  • Compute checksums and provenance fingerprints for critical files.
  • Record attestation events as tamper-resistant logs.
  • Emit machine-readable compliance reports per execution.

MVP vs. Long-Term Engine

MVP Focus

  • CLI-based validator for manifests and metadata.
  • Checksum and provenance summary per run.
  • Deterministic failure codes mapped to NTS requirements.

Roadmap

  • Attestation independence checks (Builder vs Reviewer).
  • Multi-model orchestration audit logs.
  • Integration with archival pipelines (Zenodo, OSF).
  • CRI-CORE Enterprise for regulated environments.

Repository