| title | filetype | type | version | doi | status | created | updated | author | maintainer | license | copyright | ai_assisted | ai_assistance_details | anchors | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Aurora Workflow Orchestration (AWO) — Repository Overview |
documentation |
non-normative |
2.0.0 |
10.5281/zenodo.17013612 |
Active |
2025-12-25 |
2026-01-09 |
|
|
Apache-2.0 |
|
partial |
AI-assisted drafting under full human oversight; aligned with AWO v2.0.0 method layer and ARI governance. |
|
Method layer of the Waveframe Labs governance stack.
Defines how research is conducted, not what conclusions are reached.
AWO provides the normative methodological framework for running reproducible, auditable, AI‑assisted research workflows.
It formalizes:
- workflow phases
- artifact classes
- invariants
- contracts
- schema interfaces
AWO does not enforce execution — enforcement belongs to CRI‑CORE.
This repository contains the complete AWO v2.0.0 methodology layer, replacing all v1.x material now archived under /v1-archived/.
AWO answers a single foundational question:
How must research be structured so that results remain independently reconstructible, auditable, and epistemically valid?
AWO governs:
- workflow phase ordering
- artifact production requirements
- role separation boundaries
- reproducibility + falsifiability invariants
- machine‑readable contract surface for CRI‑CORE
AWO does not run workflows or judge correctness.
Recommended reading path:
AWO_OVERVIEW.mdSCOPE.mdWORKFLOW_SPEC.mdARTIFACT_CLASSES.mdARTIFACT_REQUIREMENTS.mdINVARIANTS.mdandROLES.mdGLOSSARY.md,PROVENANCE_MODEL.md,NEUROTRANSPARENCY.md/contracts/— schemas & contract surfaces
Initiation → Scoping → Contribution → Review → Approval → Audit
Phase progression requires:
- required artifacts exist
- metadata is complete
- provenance is intact
- role separation is enforced
Self‑attestation and silent revision are prohibited.
| Layer | System | Responsibility |
|---|---|---|
| 0 | NTD / NTS | Epistemic disclosure & cognitive provenance |
| 1 | ARI | Governance, metadata law, authority boundaries |
| 2 | AWO | Methodology specification (this repo) |
| 3 | CRI‑CORE | Enforcement + attestation engine |
| 4 | Case Studies | Applications (e.g., Waveframe v4.0) |
/
├── contracts/
│ ├── CONTRACT_INDEX.md
│ ├── ARTIFACT_SCHEMA_MAP.md
│ └── schemas/
│ ├── awo.initiation.schema.json
│ ├── awo.execution.schema.json
│ ├── awo.review.schema.json
│ ├── awo.specification.schema.json
│ └── awo.release.schema.json
│
├── docs/
│ ├── ONBOARDING_GUIDE.md
│ ├── FAQ.md
│ └── CHANGE_LOG.md
│
├── examples/
│ └── awo.initiation.example.json
│
├── method/
│ ├── PHASE_TOPOLOGY.md
│ └── README.md
│
├── v1-archived/
│ (historical materials)
│
├── ADR/
│ ├── README.md
│ └── template.md
│
├── CITATION.cff
├── LICENSE
├── SECURITY.md
└── README.md
- All material is licensed under Apache‑2.0
- AI assistance is disclosed per ARI + NTS requirements
- Derived artifacts must preserve metadata and provenance chains
If you use AWO v2.0.0 in academic writing, tooling design, or reproducible-workflow research, please cite:
CFF (preferred)
cff-version: "1.2.0"
message: "If you use this methodology, please cite it."
title: "Aurora Workflow Orchestration (AWO)"
version: "2.0.0"
doi: "10.5281/zenodo.17013612"
authors:
- family-names: "Wright"
given-names: "Shawn C."
orcid: "https://orcid.org/0009-0006-6043-9295"
@software{AWO_v2_0_0,
author = {Wright, Shawn C.},
title = {Aurora Workflow Orchestration (AWO) v2.0.0},
month = jan,
year = 2026,
publisher = {Waveframe Labs},
doi = {10.5281/zenodo.17013612},
url = {https://github.com/Waveframe-Labs/Aurora-Workflow-Orchestration}
}
© 2026 Waveframe Labs · Independent Open-Science Research Entity · ORCID: 0009-0006-6043-9295 · DOI: 10.5281/zenodo.17013612
Governed under the Aurora Research Initiative (ARI)
