| title | AWO Artifact Classes | ||||||
|---|---|---|---|---|---|---|---|
| filetype | documentation | ||||||
| type | specification | ||||||
| version | 2.0.0 | ||||||
| doi | 10.5281/zenodo.18201829 | ||||||
| status | Active | ||||||
| created | 2025-12-20 | ||||||
| updated | 2026-01-09 | ||||||
| author |
|
||||||
| maintainer |
|
||||||
| license | Apache-2.0 | ||||||
| copyright |
|
||||||
| ai_assisted | partial | ||||||
| ai_assistance_details | AI-assisted drafting with full human oversight; revised to align with AWO v2 Design Envelope, Minimal Phase Topology, and revised Workflow Specification. | ||||||
| dependencies |
|
||||||
| anchors |
|
This document defines the conceptual artifact classes required by Aurora Workflow Orchestration (AWO) v2.0.0.
Artifact classes are methodological categories of required outputs associated with workflow phases.
This document defines:
- what artifact classes exist,
- why they exist,
- which phase produces them.
It does not define formats, schemas, storage, tooling, or enforcement.
This document is normative.
All AWO artifact classes MUST satisfy the following principles:
- Explicitness: the artifact is a discrete, identifiable object.
- Persistence: the artifact can be preserved and referenced.
- Traceability: the artifact can be linked to inputs and prior artifacts.
- Role accountability: responsibility for the artifact is role-bound.
- Method over execution: artifact classes describe methodology, not implementation.
Artifact classes are aligned to the Minimal Phase Topology.
Produced by: Workflow Initiator
Purpose:
Declare research intent, initial assumptions, and the decision to operate under AWO methodology.
Produced by: Workflow Initiator and/or Contributor
Purpose:
Define the bounded problem space and explicitly state what is out of scope.
Produced by: Workflow Initiator and/or Contributor
Purpose:
Declare the criteria by which outputs will later be reviewed for sufficiency.
Produced by: Contributor
Purpose:
Capture substantive research work products (analysis, derivations, experiments, drafts).
Produced by: Contributor
Purpose:
Preserve structured reasoning sufficient to explain transformations from inputs to outputs.
Produced by: Reviewer
Purpose:
Evaluate execution artifacts against declared criteria and methodological constraints.
Produced by: Reviewer
Purpose:
Enumerate identified issues, gaps, ambiguities, or violations requiring resolution.
Produced by: Authorized releasing role
Purpose:
Freeze a workflow iteration and declare the set of artifacts complete for that iteration.
The following artifact classes may reference AWO workflows but are not workflow phases.
Produced by: Auditor
Purpose:
Assess invariant compliance, traceability completeness, and reconstructibility.
Audit occurs outside AWO workflow execution.
These artifact classes may appear at multiple points in a workflow.
Produced by: Role responsible for the change context
Purpose:
Record material changes to scope, criteria, or workflow structure with justification.
Produced by: Artifact owner
Purpose:
Declare upstream documents, artifacts, or policies relied upon.
Any change to:
- artifact classes,
- phase alignment,
- or artifact purpose,
constitutes a breaking methodological change and requires a major version increment.