4.0 KiB
Artifact semantic native fixtures
All three variants have Interlock requirement rationale as the owner trace. Open Review semantics > Artifact links. Work on copies of the original .arcadia files. Exact before/after JSON, source, and core requests sit beside each fixture.
Move and optional metadata
Open semantic-artifacts-move.arcadia. Pair OA Interlock requirement and SA Interlock requirement, then Review this exact artifact pair. Select these three properties independently with Set final value:
- Owner: SA Safety coordination.
- Revision: Present checked, empty text. This is
Some(""). - Fragment: Present unchecked. The disabled
section-4text remains a draft; accepted value isNone.
Before Apply, Keep Presence must produce an explicit conflict with the Owner move. Leave that Presence decision unselected to restore valid preview. Type - into Owner identity, switch rows/tabs, checkpoint and recover; rejected raw input must remain. Repair the Owner identity with the named picker. Apply once and compare exactly with semantic-artifacts-move.after.json/.after.arcadia. Undo/Redo once restores exact source/model/history. The link moves, so subsequent metadata review requires an appropriate trace at the new owner; the old trace must not silently rebind.
Source attachment absence and deletion
Open semantic-artifacts-delete.arcadia. Its OA link still exists, now attached to OA Safety coordination. Review the original trace and explicitly pair the historical OA link with the SA link. The OA picker directly offers this same-layer link, labeled with its current Safety owner and “not attached to reviewed owner”. Take Artifact Presence: the SA link is removed while the OA link remains. The exact after oracle contains eight acknowledged facts (source metadata still exists), not seven retired facts. A genuinely deleted source link would retire unavailable metadata instead, as covered by the core test.
No OA identity means destination-only retention; it must not act as deletion. No fake missing UUID or candidate record is used as a tombstone.
Creation and provisional identity
Open semantic-artifacts-create.arcadia. Choose OA Interlock requirement, then Reserve a new destination counterpart, then Review this exact artifact pair. Take Presence alone remains blocked. Deliberately review Name, Description, Owner, Relation, URI, Revision and Fragment, using Set final value for every field. The seeded values are from the source, with the destination owner and a fresh reserved identity.
The GUI deliberately reserves a random stable UUID, so the initially supplied creation after oracle is a template. Obtain the reserved UUID from its saved recovery seed or the created artifact after Apply, then regenerate the exact oracle against the unchanged fixture base:
. .local/toolchain/env.ps1
.local/native-fixtures/generate-semantic-artifacts-preserved.exe .local/native-fixtures/artifacts-session <reserved-uuid>
Compile the preserved generator using this directory’s README. This mode reads the existing semantic-artifacts-create.json in the explicitly supplied copied directory, preserves that fixture identity, and updates only the request/after oracle using the explicit reserved ID. It must not be called without the UUID after native work, since output-directory-only generation creates new initial fixture identities.
Compare accepted source/model/history exactly. This creation gesture has eight explicit reviews and one complete candidate. Checkpoint/recover before Apply must retain the reserved identity, per-field drafts and excluded state; reservation itself must not add a model record.
Layout checks
At 1100x700 and 1440x900, verify wrapping tabs, pair picker actions, description editor, Owner picker/raw field and optional text toggles. All row actions must remain outside the right scrollbar gutter. Native execution is pending; the generator only validates direct-core preparation and exact source round trips.