Waveframe Labs
Foundational Methodology — Maintenance Mode

Aurora Workflow Orchestration (AWO)

Aurora Workflow Orchestration documents how research conducted within the original Aurora Ecosystem was intended to be structured and recorded so that it remains traceable, reconstructible, and reviewable over time.

Current status · 2026-09-01

AWO is preserved as a published methodology and part of CRI-CORE's research lineage. Current CRI-CORE does not execute AWO workflows, and AWO is not a dependency of the Waveframe product runtime.

What AWO Defines

AWO translates epistemic and governance requirements into a repeatable methodology. It specifies workflow phases, artifact classes, and role boundaries without enforcing correctness or legitimacy.

AWO is procedural, not normative. It does not define truth, authority, or compliance outcomes.

Core Responsibilities

  • Define workflow phases and valid transitions
  • Specify required artifact classes and minimum structure
  • Encode role separation boundaries (e.g., no self-approval)
  • Integrate Neurotransparency requirements at defined workflow points
  • Produce deterministic inputs for downstream validation and enforcement

Original Aurora Position

AWO was designed to sit between governance and enforcement. This hierarchy records the original research architecture, not the current Waveframe product dependency graph.

  • L0 — Governance & Epistemics: ARI, NTD, NTS define authority and necessity
  • L1 — Method: AWO structures workflows and artifacts
  • L4 — Enforcement: CRI-CORE validates artifacts against upstream contracts
  • L6 — Research Outputs: Case studies demonstrate AWO in practice

Specification & Archive