Waveframe Labs
Layer 1 — Method

Aurora Workflow Orchestration (AWO)

Aurora Workflow Orchestration defines how research conducted under the Aurora Ecosystem is structured and recorded so that it remains traceable, reconstructible, and reviewable over time.

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

Position in the Aurora Stack

AWO sits between governance and enforcement. It structures research before any validation or execution occurs.

  • 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