feat(reference): Multiverseal Twin substrate reference impl [E13/WS-C] - #281
Merged
Conversation
Executable FHRR substrate for the twin contracts (ADR-0014). V=C^D unit phasors, so phase=provenance is literal. bind/bundle/unbind + interferometric diff + unlinkability leakage. Self-test proves, with measured numbers, the four load-bearing properties: - reference-gating: recover 0.348 vs wrong-ref 0.003 / opaque -0.009 (~100x SNR) - ε-unlinkability: cross-context leakage L=0.004 (near-orthogonal) - fringe is the leading indicator: score move 0.00016 vs mean|fringe| 0.020 (~125x) - holographic tamper-evidence: one local write perturbs 100% of the spectrum Linear substrate ONLY; VRF/QEC/impersonation-wall at the contract layer, Sybil/nonlinear policy in a separate layer (WS-F). Built in an isolated worktree.
…to make validate test_mvtwin.py proves the four load-bearing properties (reference-gating, epsilon-unlinkability, fringe-as-leading-indicator, holographic tamper-evidence) with measured numbers and asserts, but nothing invoked it: it lives outside tools/, so pytest tools/ -q (tools-tests.yml) never collects it, and it was on no Makefile target either. A self-test nobody runs in CI proves nothing about the PR that shipped it.
mdheller
force-pushed
the
feat/multiverseal-twin-refimpl
branch
from
August 4, 2026 19:43
8fbd1a1 to
0dccd12
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Multiverseal Twin — substrate reference implementation [E13 / WS-C]
Executable substrate for
schemas/{MultiversealTwin,TwinAttestation,InterferometricDiff}.json(ADR-0014). Turns the twin contracts into a running, tested engine on FHRR (Fourier Holographic Reduced Representations):V = C^Dunit-modulus phasors, so phase = provenance is literal.Proven, with measured numbers (
python3 test_mvtwin.py, D=8192, N=8)Scope & honesty
Linear substrate only. Reference-at-ingest, ε-budget, VRF mint/verify, and the impersonation wall are enforced at the contract/policy layer (ADR-0014); Sybil-resistance / nonlinear trust policy live in a separate layer that must not leak back into this medium (twin spec §H / WS-F). Lands under
reference/(adjacent to the contracts it exercises), so it doesn't touch schema CI. Next increments: VRF-derived references, QEC[[n,k,d]]sharing, and theInterferometricDiffreplay (Fresnel forward-propagation).🤖 Generated with Claude Code