You can't draw various connections / relationships when selecting different diagram projections #30
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sorokin.oleg.edu/ARCADIA-Studio#30
Reference in New Issue
Block a user
For example, when you select 'Containment' projection - you can't draw 'Allocation' relationships using the tools menu on the right
Maybe other similar cases exist, but I am not sure
Codex-ytr83r/root claims the bounded direct Allocation drawing outcome. Current issue has no comments/visible competing claim; will recheck after this claim. Intended distinct work branch: codex/allocation-drawing-ytr83r-20260923 in this Gitea repository, based on the local #31 candidate17f1f89fef4a6bf520f4b09a2116548b967d030e above publishedb868541. That base is not yet published or accepted: #31 desktop1216pass0fail6ignored, remaining lint/build/native checks in progress. Peers should not attempt to consume this local-only work yet.
Source diagnosis and independent critique agree: the direct palette contains four exchange tools and no Allocation tool in any projection. Containment does support Allocation relationships; the existing Create relationship form can create them. A form shortcut alone does not meet the user's explicit draw-from-right-tools request. Selected scope: add one Allocation tool through the existing stamped two-endpoint connection lifecycle, preserving existing forms and allocation-view drag semantics.
Acceptance: OA Entity/Actor→unallocated leaf Activity and SA System/Actor→unallocated leaf Function in Containment; core-valid same-layer endpoints, no non-leaf/occupied-target/reassignment bypass, no reparenting/new work/filter changes; one relation transaction with exact Project/source Undo/Redo and save/reopen; visible line when placement/filter permits; stale/draft/cancel safeguards and relevant projection eligibility. Inspect other similar tool gaps, but do not silently redesign all connections. Independent source/review work can proceed in an isolated checkout while #31 finishes; one compiler and root-only GUI operation remain serialized. #16/#27 ownership remains Codex-956atf; Linux remains user-paused.
Codex-ytr83r/root source checkpoint: candidate
cf37c36be1is pushed on codex/allocation-drawing-ytr83r-20260923, based on #31 source17f1f89. It adds a direct Allocation drawing tool for OA and SA views whose projection includes both performers and work, including Containment. The two clicks create only the validated Allocation relation; existing semantic elements, nesting, positions and saved filters remain unchanged. Mixed traceability placement retains the captured view and permits a visible performer/work pair from either layer, with same-layer target validation.Independent source review covered candidate alternatives and a captured-view synchronization defect; that repair is included before execution. Six focused tests plus exact-source history coverage exercise both layers, eligible projections, invalid/occupied/nonleaf/cross-layer/hidden endpoints, cancellation, stale/modal/draft guards, and the diagram/app-layer combinations. These are test definitions, not a pass claim: the first identified Windows desktop test/lint/build gate is now running on the clean commit. Native two-layer drawing/Undo/Redo/reopen checks remain pending. No overlapping compiler or GUI trial; #31 native processes closed normally before this gate started. Linux remains user-paused.
Codex-ytr83r/root checkpoint: corrected source
301126f609is pushed on codex/allocation-drawing-ytr83r-20260923. Final-02 desktop execution passed: 1,222 tests passed, 0 failed, 6 existing ignored; all six new direct Allocation tests passed. Strict lint and matching builds are still running, so native acceptance remains pending.The preserved final-01 run at
cf37c36failed test compilation with five E0308 errors: Message::Diagram requires Choice, not a bare UUID. No tests ran in that attempt; all 2,760 captured inputs remained unchanged. The repair changes only those five test invocations to the real Choice { id, label } payload. Production and assertions are unchanged, and the tests still exercise the guarded UI message path.Native preparation now handles the complete saved source bundle from the start and binds only the two new relation UUIDs after exact B/O/OS comparison. Source review confirms allocations in this fixture use existing performer modules and Undo restores the prior bundle, so no new or detached module is expected from this sequence. Planned actual OA/SA drawing, occupied-target refusal/cancel, Undo/Redo and fresh reopening still require the final build. #31 handoff is published separately in1087/#27-1090; Linux and integration ownership remain unchanged.
Codex-ytr83r/root checkpoint: all final-02 Windows gates passed at source301126f6098286bf440c1bd1b1ed685753984723: desktop1222 passed/0 failed/6 ignored, strict desktop all-target Clippy, matching GUI and snapshot evaluator builds. Raw source inventories unchanged; prior unchanged core/server workspace evidence remains separately attributed.
The first native trial exercised OA direct drawing, Save, Undo and Redo with four accepted complete saved-bundle/Project checkpoints B/O/B/O. On resuming after the interrupted user turn, neither app nor observer remained running and there was no normal-close or observer-failure receipt. Empty logs do not establish an exit code or close cause. That trial and its fixed relation identity are preserved as partial evidence, not a successful close/reopen claim. A new independent trial is being staged from the same preserved build to finish OA/SA refusal, history and normal close/reopen acceptance. No rebuilding or relabelling of the partial trial. Final portable evidence/handoff still pending.
Codex-ytr83r/root: fresh native trial at301126f6098286bf440c1bd1b1ed685753984723 passed the declared OA/SA Containment workflow. Actual palette drawing, occupied-target refusal/Escape, Undo/Redo and fresh reopen produced nine exact complete saved-bundle/Project checks B/O/B/O/O/OS/O/OS/OS. Both ordinary Alt+F4 closes were observed; app PIDs4604/3092 exited0 with empty logs and unchanged immutable inputs. Complete final bundles and fixed relation identities matched across reopen.
Independent final review found no material blocker and checked source/package/receipt hashes, fixed semantic contracts, lifecycle chains and selected UI captures. Prior interrupted native attempt remains separately preserved with unknown exit cause. Portable evidence collection is running; these results are still local-only until the archive is pushed and linked. Source301126f is already pushed. This is bounded Windows branch acceptance, not combined integration/release, whole-project or Linux acceptance. #27 comments retrieval timed out twice; issue details remain readable and confirm Codex-956atf ownership. No ownership change.
Codex-ytr83r/root delivery: source301126f6098286bf440c1bd1b1ed685753984723 and evidence45605001f690ad9ee2ed786c3cd77ffbde8e10aa are pushed and remotely confirmed.
Portable evidence and reproduction entrypoint. Source branch: codex/allocation-drawing-ytr83r-20260923; evidence branch: codex/behavior-anchor-plan-ytr83r-20260912. The native/gate scope reported in1141 is now available to other machines: desktop1222/0/6, strict lint, matching builds, nine exact complete saved-model checks, two observed normal closes and fresh reopen, independent final review. Linux remains paused; combined integration/release is not claimed.
Run from the archive with Python3 and the documented source commits fetched:
python verify-build.py verify --archive . --repo /path/to/ARCADIA-Studio. Parent portable verification passed604 originals and11036 exact Git source records; independent staged audit verified all610 files including132 ignored logs. No missing nonbinary references/source gaps; omitted binary/runtime references remain explicit. Archive includes interrupted native and failed compilation evidence separately, never relabelled successful. README remote blob8a86af7a512a0561ac2ab8a9e890fe3311f295d7 matches local commit.Contribution is ready for Codex-956atf's #27 integration. Keep this issue open until the identified combined result is verified; no force-push, peer-source replacement or release publication performed here. Picker Escape #35 is separately owned and its gate is running above this source.