Skip to content

Pressure Cabinet structural Up from arrival routes - #85

Closed
mtc1122 wants to merge 3 commits into
mainfrom
pressure/cabinet-arrival-route-up
Closed

mtc1122 wants to merge 3 commits into
mainfrom
pressure/cabinet-arrival-route-up

Conversation

@mtc1122

@mtc1122 mtc1122 commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Purpose

Test the next Cabinet host-leakage frontier after PR #84 without selecting a path/parent/occurrence feature in advance.

Positive pressure

Adds a bounded source action:

action selectHomeRoute(route: [Int]) {
    selectHome()
    selectFolder(route)
}

This should prove that an explicit Home-rooted runtime-sized route can replay atomically through existing sequence action composition, including after partial-persistence restart and with rollback on a later invalid segment.

Negative pressure

Pins two host-boundary problems before changing either UI:

  1. TUI and browser share one source-owned selectedFolder, but separate surface-local route histories do not compose when navigation crosses surfaces.
  2. Source-owned actions such as createFolder can change selectedFolder without a structural-index gesture, so a host gesture route can stop describing the current selection.

These tests are evidence, not selected language law.

Explicit non-goals

  • no Folder.parent
  • no provenance-as-parent
  • no reverse lookup from selected identity
  • no first-class path
  • no stable occurrence identity
  • no host-visible modeled identity
  • no UI route bookkeeping yet

If this pressure confirms the mismatch, the next question is the exact semantic status of arrival context when selection itself is shared source-owned state.

Result

Pressure confirmed at exact head c86bd5c1b4b52bbac3fa6f65a2bc93db5a0207ac with green CI.

Positive result:

  • Home-rooted runtime-sized route replay works atomically across partial residency.
  • Later invalid segments roll back earlier route steps.

Negative result:

  • surface-local route histories are insufficient when TUI and browser share one source-owned selectedFolder;
  • source-owned actions can change selectedFolder without emitting a structural-index navigation gesture, so a gesture-only host route can become stale without the host being able to repair it honestly.

Conclusion:

The unresolved fact is not a generic path to a folder. It is arrival-context coherence with one shared source-owned selection.

This PR is being closed unmerged as completed pressure evidence.

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