Skip to content

Pressure runtime-private arrival route continuity - #87

Closed
mtc1122 wants to merge 3 commits into
mainfrom
pressure/opaque-arrival-continuity
Closed

mtc1122 wants to merge 3 commits into
mainfrom
pressure/opaque-arrival-continuity

Conversation

@mtc1122

@mtc1122 mtc1122 commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Purpose

Follow closed PRs #85/#86 with a test-only falsifier for whether an opaque runtime-owned witness could distinguish current route coherence without leaking modeled identity into the host.

The proof observes the exact Home-rooted route, source-owned selected designation, and complete ordered membership of every traversed parent. These identities are read only inside a private Rust test module, not a host API. No source/runtime production changes, new syntax, or application route semantics are selected.

Exact-head result

PASS at cf1e25657439cf1e4406f945766c12930cf68373, GitHub Actions run 44204748033: cargo fmt --check, cargo clippy -- -D warnings, cargo test, cargo build, and Python reference tests all green.

The five tests establish:

  • renaming a selected nested folder retains current route coherence;
  • independent Home reselection and create-and-select invalidate it;
  • rearranging an ancestor's stored child membership invalidates it despite an unchanged selected identity;
  • failed action preserves it under transaction rollback;
  • two duplicate-occurrence index routes to one target are distinguished by their witnessed routes (a new explicit gesture must replace the prior host route/witness).

Limitation / interpretation

This establishes only current-state structural and identity equivalence. A round-trip structural mutation that restores the exact previous ordered members could be observationally identical. There is no currently selected member mutation epoch, stable occurrence identity, or runtime-owned arrival-history token. The test also materializes route parents to inspect current membership; no generic production surface or partial-residency cost has been justified.

The choice between current-state route validity and strict historical occurrence continuity remains open. Do not call this a production solution or introduce a public token/check from the test alone.

Decision: close unmerged and freeze as pressure evidence. The next bounded step is to decide whether current-state equivalence is sufficient for Up and, if so, pressure the smallest host-safe runtime-owned yes/no adapter; otherwise identify a concrete indistinguishable-history counterexample that would justify more authority or history.

@mtc1122 mtc1122 closed this Nov 18, 2026
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