Record view-local scenario spacing decision

This commit is contained in:
2026-09-13 01:00:40 -07:00
parent 34cdca132e
commit 5bd2c0bec8
+38
View File
@@ -385,3 +385,41 @@ combined tests and native acceptance are not established by this record.
## 2026-09-12 — Cross-machine coordination evidence
User clarification: independent Gitea peer sessions run on different machines and cannot access this session’s `.local` directory. In-thread delegated agents share this workspace. Publish required source, reviews and runtime evidence through versioned Gitea commits or attachments before handing them to peers; verify access and link the exact version. Local paths are provenance only for remote peers. Local compiler, process and native-window observations do not establish another machine’s state or a shared hardware lease.
## Saved Scenario spacing gestures — 2026-09-13
Codex-ytr83r /root. For the next Saved Scenario editing increment, dragging a
lifeline header changes that view's lane x; dragging a message body or label
changes that view's occurrence send-y. Preserve shared Scenario order and all
other saved layout records. Keep semantic reordering explicit in the sequence
outline; do not infer it from crossing another drawn message. Automatic views
retain their existing derived-layout editing behavior.
This follows the user's requirement for directly editable diagrams and the
[existing sparse layout contract](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/src/commit/aed07176ab453b981d5f9c76e504c531f6dd7f42/harness/scenario-layout-contract-candidate.md).
The [native Capella comparison](experiments/capella-scenario-observations-20260913/README.md)
provides bounded primary evidence: receiver-execution movement changed only the
diagram file; separate message/lane Undo restored both files exactly. Two arrow-body
drag attempts did not move that example, so use the drawn body/label as discoverable
Studio targets while distinguishing activation bars and lifecycle markers by role.
This observation does not establish Capella's general crossing or reordering rules.
Reject implicit shared reordering on a Saved spacing drag: another view's unchanged
coordinate records do not ensure unchanged appearance when automatic anchors
recompute. Reject a generic permutation of message coordinates: actions, fragments,
opaque references and previously crossed positions do not supply interchangeable
slots. Reject resetting arrangements to automatic because it discards authored intent.
Preview from one captured accepted Project and visible camera; resolve the complete
candidate geometry without mutating source or history. Commit one existing command
only after a valid release and successful source update. Invalid previews, cancellation
and return to origin preserve accepted values and camera; an ordinary click still
selects its semantic target. Preserve explicit zero/empty/absent overrides and real
Redo. Feasible source-order crossings remain diagnostic, not silently clamped.
Implementation and native acceptance remain pending at this decision. Require
actual same-batch and multi-frame input, stale-token cancellation, preview/commit
geometry agreement, one Undo/Redo and source reopen, plus measured large-model drag
cost. Revisit target affordances or event flow if these workflows reveal accidental
reordering, hidden target ambiguity, camera jumps or unacceptable preview latency.