ARCADIA-Studio/harness/release-capability-core.md

R2 capability and mission core milestone — 2026-09-05

Status: the bounded R2 core contract is integrated and tested. Graphical authoring, source/API parity and native workflow verification are separate integration gates; this report does not claim the release or the larger semantic audit is complete.

Frozen interface

• Kind::OperationalMission, OaBody::Mission: OA mission; default counterpart is Kind::Mission / SaBody::Mission. Both are root semantic records. Scenarios may use either mission as their context.
• CapabilityInclude { source, target }: including capability → included capability.
• CapabilityExtend { source, target, condition: String }: extending capability → extended capability. Blank/whitespace conditions produce warning missing_extension_condition; conditions also use the ordinary text-validity checks. Draft extensions remain editable.
• CapabilityGeneralization { source, target }: specific capability → general capability.
• MissionInvolvement { source, target }: OA Entity/Actor → OperationalMission; SA System/SystemActor → Mission.
• Existing MissionCapability { source, target }: OperationalMission → OA Capability, or SA Mission → SystemCapability.
• TraceKind::Mission: canonical OA OperationalMission → SA Mission. The transition planner creates this typed trace in either direction. Existing explicit Capability ↔ SA Mission mappings remain available and use Manual traces; Mission→OA now defaults to OperationalMission while reusing a uniquely existing explicit Capability trace.

All new relations reject cross-layer, wrong-family and self endpoints. Inclusion and generalization each reject directed cycles in their own graph, including transitive cycles. They remain independent of containment and of one another. Extension is conditional augmentation; no separate extension-cycle restriction was invented beyond the audited no-self rule.

The ordinary relation endpoint visitor performs transition mapping, reidentification, deletion and reference checks for all four new variants. New mission bodies have no hidden references. No new registry, transaction type or projection path was needed. Semantic relationships remain directed diagram edges; they do not create visual/semantic parenthood. The schema stays version 2 temporarily during interface integration; the release migration/version change belongs to the language integration worker.

Verification actually run

With CARGO_TARGET_DIR=D:/CodexBuilds/Capella2-01a06e2e:

cargo test -p oa-core --locked --test workflows --test review_regressions --test process_diagnostics --test release_capabilities
cargo clippy -p oa-core --all-targets --locked -- -D warnings

Observed: 51 tests passed (28 workflows, 15 prior regressions, 1 process diagnostic, 7 new capability/mission tests); strict core Clippy passed. Modified test files were formatted with Rustfmt edition 2024.

The new release_capabilities.rs exercises both perspectives and directions, exact endpoint preservation and extension condition propagation, atomic cycle rejection with redo/history retained, invalid condition rejection and undo, typed Mission trace defaults and legacy mapping reuse, complete mission-map dependency transitions, scenario/artifact/placement/trace references across UUID changes and deletions, counterpart survival after source deletion, and projection direction independently of nesting.

The first broader run exposed the old regression expectation that reverse SA Mission creation defaults to OA Capability. That test now explicitly preserves Capability as an alternative in both directions and verifies the new OperationalMission default. An initial full-core run also found the complete source fixture missing new relation kinds; the independently owned language worker is updating that fixture. This report intentionally does not count an unobserved final full-core/source run as passing.

Remaining release obligations

Integrate the usable mission/capability graphical workflow, readable direction/condition labels and source/API constructors/specification. Then verify the actual native mission map workflow and conduct independent review. R1 contextual process/chain topology, R3 semantic drift/reconciliation, R4 reusable scenarios, R5 state/event semantics and R6 data contracts remain required by the release audit.