11 KiB
Communication means native review — 2026-09-06
Goal remains active. Current corrected reverse-scenario native gate PASS on desktop F5ECAEC02BBAFBC6F3BDC6ADEB746AFE91F3A495C6D9564A68DEA41E61AC9246: Behavior context, unchanged architecture view, exact three-file Save/Undo/Redo and reopen. See the final section; earlier trials and their binary-specific limitations are retained below. Tracked fixtures/oracles: fixtures/release1-native/communication-means/README.md.
Initial draw/create/reuse setup: Windows process9800, GUI SHA-256 A5A741349B49D0C90A6BDB0FA7871415133CBCC1B8A4ECF0C4EDDDB99313F2D2, isolated bin-source6-guide/profile and system-only PATH.
Draw and explicit create-port transition
At1100x700/66% zoom opened cm-draw.arcadia. Both participant names and both activity names were readable. Communication means highlighted Rescue team/Control centre and not activities. Clicked Rescue team then Control centre; created one participant relation. Properties renamed it Rescue radio channel. Saved isolated baseline .local/native-qa/cm-create-before/entry.arcadia on first Save submission. Source contains new identity3e576659-3455-4fb5-811e-5f4a326948f4, original generated alias communication_means_rescue_team_control_centre, empty description/items, oriented false, source cm10/target cm11. Independent drawn-baseline whole-model/source check is separate/pending.
Initial fixture instructions incorrectly said choose Selected only before participant mapping. That hid the dependency rows and left only create-port choices. Cancel returned clean accepted baseline. Reopened Required references, explicitly confirmed Rescue team→Rescue radio and Control centre→Control radio. Source reused Existing team socket; target selected Create Standard port · bidirectional. Missing either endpoint kept Apply blocked. Retained both target Names when prose conflicts appeared, then narrowed to Selected only: both endpoint decisions retained and Apply enabled. One Apply created a boundary exchange and one new port. Native SA view showed the connected existing team socket, two Control radio sockets, and named new target port parent Control radio. Existing control socket remained; no interface/allocation action was taken.
Saved .local/native-qa/cm-create-after/entry.arcadia. Independent check create passed full Project and exact complete reachable source with two generated UUID substitutions only; no placement identities. Preserved accepted two-file bundle at .local/native-qa/cm-create-accepted. One Undo then Save matched baseline entry byte-for-byte, SHA25640363373B2443714F38D5825F8FAF53183CF004962059E0B611D01DB8E7F7F7E. The no-longer-included generated traceability file remains on disk under the non-destructive save policy; it is not reachable from the restored entry. One Redo then Save restored both accepted files byte-exact, retaining UUIDs:
- entry.arcadia: FC790673723FE81D049CBCA3EE36A5BDDB09F534D906C18BF3355D72EF23A5C1
- traceability.arcadia: ACAE3DAD95CD3F91A2D4E9FF8D64D7E9BA27888514B2C9DC5793B6941D7B5485
All three transition Save submissions succeeded first attempt (plus baseline Save). GUI clean afterward, stderr length0, no recovery checkpoints; only recent-models.json present. Isolated native SaveAs type_text once left filename empty before submission; reobserved/refocused/reentered successfully. This input-helper observation is not an application save failure.
Both-existing-port reuse, reverse scenario Call/Reply, default-size layout, directional Flow refusal and crash recovery are separate gates; this result does not claim them. Revised reverse oracle predicts GUI automatic destination placements independently and rejects changed geometry/metadata/element/source bytes.
Independent draw baseline check subsequently PASS: typed CreateRelation using initial generated engineering name and alias, then name-only EditRelation, with production source updater after each operation. Actual model supplied only the new UUID. Complete Project and full source equal the saved native baseline; expected entry SHA25640363373B2443714F38D5825F8FAF53183CF004962059E0B611D01DB8E7F7F7E. Log .local/native-fixtures/cm-native-draw-check.log, independent expected bundle/model/exact commands .local/native-fixtures/cm-native-draw-oracle. Orientation/alias counterfactuals rejected by full-model equality; added whitespace rejected by exact-source equality. This closes the separately pending drawn-baseline oracle above.
Both existing ports native alternative
Reopened the exact preserved before entry in the same process/minimum size. Through channel context action, confirmed both participant mappings under Required references, narrowed to Selected only, then explicitly chose Existing team socket and Existing control socket. Both choices remained available in the narrowed scope. No Name reconciliation was required because participant updates were outside the final scope; Apply remained blocked with either endpoint absent and enabled once both were chosen. One Apply showed the boundary exchange connected to the two existing sockets; object count stayed8.
Saved .local/native-qa/cm-reuse-after/entry.arcadia. Independent check reuse PASS full Project/exact complete reachable source with2generated UUID substitutions only,0placements; no new port. Preserved accepted bundle in cm-reuse-accepted. One Undo/Save restored baseline entry exactly (40363373B2443714F38D5825F8FAF53183CF004962059E0B611D01DB8E7F7F7E). One Redo/Save restored both accepted files byte-exact:
- entry.arcadia AE9CDFB1CAAF4EAA8CCFCF9E1603D7CBB2429649B28E827ADAF8190A03E4E08A
- traceability.arcadia 20FA451694101A9060BF2D7F2A6A9F4510C1BA4AC20DF9F363CCB363D3255DEF
All3Save submissions succeeded first attempt, cleanGUI/0stderr/0recoveryJSON. Across create/reuse alternatives6transition saves pass plus drawn baseline Save. Reverse scenario and other previously listed gates remain separate.
Legacy reverse scenario: semantic pass, architecture navigation defect
Process4288, default1440×900, walkthrough GUI SHA256246BACE21E254985EE90EF05132139DD7D6AF75085DE9E58FEB49477A493407D. Opened tracked cm-reverse-scenario.arcadia. SA call ran Control radio→Team radio; dashed Reply ran Team→Control and correlated to Request rescue report. Whole subtree SA→OA confirmed participant mappings to Rescue team/Control centre and boundary mapping to Rescue radio channel, retaining both OA participant Names.
One Apply incorrectly navigated to Architecture, selected the first reused participant instead of the requested scenario, and placed five behavior elements into the existing communication view. Their overlap obscured participant/activity labels and caused three route warnings. This was a material UX failure on this binary. Semantic success below did not close that finding; the corrected native trial is recorded separately below.
Saved .local/native-qa/cm-reverse-after/entry.arcadia. Legacy independent check reverse PASS complete Project and exact source with15generated UUID substitutions, including5placement identities independently predicted by the old desktop placement policy. Accepted copy retained at cm-reverse-accepted. One Undo/Save restored tracked baseline entry exactly, SHA2561ABC4C4CAC37CFB06ED3B12A115F9E7E6A2D3AFFD34B25C355309E5EE465FA40. One Redo/Save restored all three accepted reachable files exactly:
- entry.arcadia F407ED3CA6C34F096B4B0E3463EA0FC9CD2BE75F84C104009CD86EE361BED629
- traceability.arcadia 076CFF57F4A5EFFD5CE99B5008432C2C6ADDC499A8AAE2595C4DEB534AB463A6
- oa/behavior/scenario_oa_cm_200.arcadia E187EDDDD3C814D7DF4879F0C96D784BAB8D7A9F11E1BFECD731F4D1E10364BC
The original report listed only the entry and traceability hashes, but its initial complete-source oracle covered all three files. The third module was subsequently hash-compared after Redo against the preserved accepted copy and passed; its final on-disk hash was independently re-read for this correction.
All three Save submissions succeeded first attempt; filename input required refocusing before submission (one unsupported UIA set_value attempt reported CacheRequest failure without editing the field). Clean GUI, stderr0bytes, no recovery checkpoint. Undo leaves the unreachable generated trace file on disk under the non-destructive save policy.
Manually opened Behavior afterward. OA participant lifelines visibly bind to Rescue team and Control centre, preserving solid leftward call and dashed rightward reply. Selected reply @oa_cm_204 inspector shows exchange Rescue radio channel @cm_50, Reply, receiver @oa_cm_202, correlated call @oa_cm_203, sender @oa_cm_201. Full-model oracle verifies no OA ports were introduced. Native reverse semantics/history passed on this legacy binary; automatic destination navigation and architecture preservation were then revalidated in the corrected trial below.
Corrected reverse scenario: Behavior context and architecture preservation PASS
Process9672, default1440×900, desktop SHA-256 F5ECAEC02BBAFBC6F3BDC6ADEB746AFE91F3A495C6D9564A68DEA41E61AC9246, stage .local/native-qa/bin-source6-behavior-context. Root repeated the same preserved cm-reverse-scenario.arcadia baseline. Whole subtree confirmed both participants and the boundary, retaining both OA Names. Apply immediately stayed in Behavior, selected @oa_cm_200, and displayed the mapped participant lifelines with a solid leftward Call and dashed rightward Reply. Manual Architecture navigation showed the original four readable objects, no overlap and no route warnings.
Saved .local/native-qa/cm-reverse-behavior-after/entry.arcadia. Independent check reverse-behavior PASS: complete Project and exact complete reachable source, ten generated UUID substitutions, zero placement identities. Accepted copy is cm-reverse-behavior-accepted. The separately retained legacy checker still expects fifteen UUIDs/five placements; neither oracle's semantic or source equality was weakened.
One Undo/Save restored the baseline entry exactly, SHA-256 1ABC4C4CAC37CFB06ED3B12A115F9E7E6A2D3AFFD34B25C355309E5EE465FA40. One Redo/Save restored all three reachable files exactly:
| File | SHA-256 |
|---|---|
entry.arcadia |
EC826B9B84616507490AC30E4D57100DD6338DBA2F7071E879A8FB58820A85C5 |
traceability.arcadia |
A56BFEFBCA3CE2259E5EB3B374A4BF6BDD9E2F23442ADEA5892791993997F0FC |
oa/behavior/scenario_oa_cm_200.arcadia |
87DF2C4A62118C326FC0B3A5768075754B643B05EDBC596C0DB5F81A903EC42A |
These final hashes were independently re-read for this report. Root reopened through Home recents and observed the original architecture and mapped scenario cleanly. All three Save submissions succeeded first attempt, with zero stderr and zero recovery checkpoints. Initial Save As filename focus/Ctrl+A/type worked on the first attempt.
This closes the reported reverse-scenario navigation defect on the corrected binary. Ordinary architecture transitions and explicit destination requests remain covered by focused automated tests, not a separate native pass in this trial. Directional Flow refusal and communication-specific crash recovery remain distinct from this result.