12 lines
2.6 KiB
Markdown
12 lines
2.6 KiB
Markdown
# Semantic attachments native fixture
|
|
|
|
Use a working copy of `semantic-attachments.arcadia`; preserve the supplied original and `.after.arcadia/.after.json` oracles. The generator prepared the final result with the current built core, and reparsed both source documents. Twelve elements, two relationships, four pre-existing traces, two final candidates, two owner reviews, no additional impacts.
|
|
|
|
1. Open **Startup ownership rationale**, then Review semantics. In Attachments select **Owned children**, choose **OA Verify interlock** and **SA Verify interlock**, then **Use exact attachment pair**. Choose **Set final value** and set destination Parent to **SA Safety coordination**. This moves only the SA child.
|
|
2. In the batch trace picker open **Navigation endpoint rationale**. In Attachments select **Relationships at source**, choose **OA Request response association** and **SA Request response association**, then **Use exact attachment pair**. Choose **Set final value**, then choose final Source **SA Validated navigation request**. Leave the relationship Target untouched.
|
|
3. The combined preview should contain two decisions/two actual candidate records, with both owner rows included. Apply once. The resulting accepted project must equal `semantic-attachments.after.json`; source must equal `semantic-attachments.after.arcadia` including the leading comment. Undo once restores exact original model/source/history; Redo once restores the exact after state.
|
|
4. Before Apply, optionally open **Interlock direct parent rationale**, review Header Parent with **Keep target**. This must conflict with the ownership Candidate. Exclude the direct row to retain its decision and restore valid preview. Likewise **Association direct endpoint rationale**, Relation Source Keep, conflicts with the owner Incident Candidate; exclude it before comparing final oracle.
|
|
5. Candidate editors must name the actual destination record. Check Properties, Attachments, Reference pairs, exact History and all right-edge actions at 1100x700 and 1440x900. Switch rows and family repeatedly; authored drafts must remain independent. Checkpoint recovery must preserve inclusion, invalid raw input when present, mappings and decisions, and must name existing selected traces correctly.
|
|
|
|
The supplied after oracle includes only the two Candidate decisions in steps1/2. Optional conflict rows must be excluded, and their mere opening/reference mapping must not create extra accepted histories. Artifacts and missing-record creation are outside this fixture. A separate FunctionalExchange port-impact acceptance fixture is still needed.
|