Support maintained reusable libraries across independent projects #8

Open
opened 2026-09-11 17:44:14 +00:00 by Codex-956atf · 1 comment
Collaborator

Owner: Codex-956atf /root for the existing library contribution and integration; active implementation follows the current canvas/checking milestones. This extracts the maintained-library portion of issue1 comment412 after the user's request to split that oversized issue. It is a required product capability, not acceptance of the existing finite prototypes.

Outcome: reusable model libraries with pinned identity and dependency closure, explicit local editing/detach behavior, and three-way updates that preserve user work and explain conflicts. Graphical/textual/REST representations must remain consistent. Checked model/persistence integration is tracked in issue7; shared language.rs source-navigation work remains peer-owned in issue6.

Acceptance: use one library in two independent projects and two instances; preserve exact original and qualified identities; reopen offline with the pinned dependency closure; update an upstream version while preserving local changes; explicit conflicts and unchanged inputs on refusal; detach/edit workflows with clear provenance; exact Undo/Redo/save/source/API round trips and usable contextual selectors/help. Define and independently review lifecycle/identity/update semantics before production integration. Existing design/prototype evidence remains linked from harness/STATE.md and durable topic records; no production completion is claimed.

Live ownership/dependencies/results belong here, with specifications and evidence versioned. Windows work continues; all Linux/WSL setup/download/build/check activity remains user-paused until the user reports networking resolved. VPN remains untouched.

Owner: Codex-956atf /root for the existing library contribution and integration; active implementation follows the current canvas/checking milestones. This extracts the maintained-library portion of issue1 comment412 after the user's request to split that oversized issue. It is a required product capability, not acceptance of the existing finite prototypes. Outcome: reusable model libraries with pinned identity and dependency closure, explicit local editing/detach behavior, and three-way updates that preserve user work and explain conflicts. Graphical/textual/REST representations must remain consistent. Checked model/persistence integration is tracked in issue7; shared language.rs source-navigation work remains peer-owned in issue6. Acceptance: use one library in two independent projects and two instances; preserve exact original and qualified identities; reopen offline with the pinned dependency closure; update an upstream version while preserving local changes; explicit conflicts and unchanged inputs on refusal; detach/edit workflows with clear provenance; exact Undo/Redo/save/source/API round trips and usable contextual selectors/help. Define and independently review lifecycle/identity/update semantics before production integration. Existing design/prototype evidence remains linked from harness/STATE.md and durable topic records; no production completion is claimed. Live ownership/dependencies/results belong here, with specifications and evidence versioned. Windows work continues; all Linux/WSL setup/download/build/check activity remains user-paused until the user reports networking resolved. VPN remains untouched.
Owner

This is a part of #1

This is a part of #1
Sign in to join this conversation.
No labels
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sorokin.oleg.edu/ARCADIA-Studio#8