Interactive evidence · §3.6

The one-way membrane

Two real JavaScript sets hold content-addressed frames. The modeled transfer gate admits verified, non-contradictory public declarations into private state and refuses private-to-public requests.

What you are looking atSeparate public and private frame sets, full computed hashes, and one directional transfer function.
Do thisRead public data inward, try an outward export, then inject and test a conflict.
Watch forInward hashes join the private set; an outward attempt leaves public bytes identical.
What this demonstratesA single transfer API can make enrichment directional and verification-gated while exposing a byte-level privacy assertion.

Scope: this proves the behavior of the transfer gate below. It does not prove that a larger application has no separate export path, side channel, compromised key, or implementation bug.

Live set state

Private estate

    Public federation

      Inward assertion: not run
      Privacy assertion: not run
      Conflict assertion: not run
      The operation log is empty.
      Prove this with any LLM

      Copy this prompt into any model. It requests a self-contained implementation that can be independently verified.

      Create one self-contained HTML file with no dependencies that independently proves a one-way data membrane.
      
      Requirements:
      - Maintain actual separate public and private JavaScript Sets of content-addressed frames.
      - Compute SHA-256 content addresses and frame hashes from canonical JSON in the browser; independently recompute them before assimilation.
      - Permit only verified, contradiction-free public → private assimilation.
      - Refuse every private → public attempt and prove the public set's canonical bytes and count are unchanged.
      - Include a valid public declaration that can be assimilated and a conflicting public declaration that must be refused without changing private state.
      - Display exact counts, full hashes, compared declaration addresses, assertions, and an operation log.
      - Include an isolated deliberate mutation that enables outward writes and makes the privacy assertion visibly fail without corrupting the live stores.
      - Provide reset, keyboard-accessible controls, aria-live feedback, reduced-motion handling, and light/dark theme support.
      
      Do not hard-code pass/fail answers. Derive every verdict from the current sets and recomputed hashes. Return the complete runnable HTML and one plain-language statement of what was proved.