Skip to content

Pressure conservative shared arrival-context validity - #86

Closed
mtc1122 wants to merge 5 commits into
mainfrom
pressure/shared-arrival-validity
Closed

mtc1122 wants to merge 5 commits into
mainfrom
pressure/shared-arrival-validity

Conversation

@mtc1122

@mtc1122 mtc1122 commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Purpose

After PR #85 demonstrated that independent TUI/browser route histories cannot describe one shared source-owned selection, test the smallest shared transient arrival-context coordinator without extending compiler/source semantics.

Test-only adapter

The fixture models one coordinator shared by two surface handles and one native PartialPersistentRuntime. It keeps only an explicit Home-rooted gesture route or None (invalid), never modeled identity, membership, or parentage.

  • explicit Home and child selection update the route only after a successful atomic route-replay action;
  • Up pops the known prefix and replays it in one action;
  • all other successful actions conservatively invalidate the route, regardless of action name;
  • failed actions preserve the route because Elanu rolls their transitions back;
  • duplicate structural occurrences can retain different route gestures without reverse lookup.

Expected pressure

This candidate should keep shared cross-surface Up semantically safe without Cabinet-specific action mutation knowledge.

The cost is deliberate: a successful rename that preserves selection also invalidates route context, making Up unavailable. The test records that usability loss rather than adopting it as desired behavior.

Non-goals

No production Cabinet UI changes, no persistent route state, no parent pointers, no first-class paths, no modeled identity crossing the host boundary, no new compiler/runtime semantics.

Completed pressure result

Exact-head GitHub CI is green at 1ee59dbe19752207836d35974c0616bca3abadf7 (format, clippy, Rust tests, build, Python).

Pass: one transient Home-rooted route shared across two presentation handles supports ordered cross-surface navigation and Up. Failed route and ordinary actions retain the old context after transactional rollback. Successful unknown source actions invalidate conservatively without app-specific action classification.

Usability cost: a successful rename that preserves selected identity also invalidates context; Up disappears unnecessarily.

Decision: freeze this test-only pressure unmerged. The safe blanket-invalidating adapter is an existence proof, not a satisfactory production implementation and not a new Elanu semantic rule.

Next falsifier: can a generic runtime/host boundary preserve a route after a genuinely selection- and membership-preserving action without exposing modeled identities, while still invalidating after source-owned reselection and relevant structural reorder? A selected-designation equality test alone may be insufficient if the same selected identity is reachable through changed route structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant