Waveframe Labs

CRI-CORE

Enforcement engine for AWO and the Neurotransparency Specification.

Layer 3 — Enforcement

Why CRI-CORE exists

CRI-CORE turns the Aurora Workflow Orchestration method and the Neurotransparency Specification into machine-enforceable rules. Instead of trusting that researchers “followed the method”, CRI-CORE validates manifests, metadata, and logs, and produces cryptographically trustworthy evidence of what actually ran.

Core Capabilities

Validator responsibilities

  • Check that AWO manifests are complete and structurally valid.
  • Verify presence and correctness of metadata headers across files.
  • Compute checksums and provenance for critical artifacts.
  • Record attestation events and approvals as tamper-resistant logs.
  • Emit a machine-readable compliance report for each run.

MVP vs. Long-Term Engine

MVP focus

  • CLI validator for manifests and metadata.
  • Checksum + provenance summary per run.
  • Failure codes that map directly to NTS requirements.

Roadmap

  • Multi-model orchestration support and audit logs.
  • Attestation independence checks between Builder and Reviewer roles.
  • Integration with DOI and archive pipelines (Zenodo, OSF, etc.).
  • CRI-CORE Enterprise for regulated environments.

Repository