← Church Machine

Figure 13 — Network Transparency via F-bit and Tunnel Keys

Two Meta Machines with matching namespace entries connected by an encrypted capability tunnel. The F-bit in mSave detects foreign/remote objects and routes access through HTTPS/RPC. GC version bump on either side revokes the tunnel atomically. Outform GTs (type=01) carry the remote endpoint binding.

Two Meta Machines Connected by Encrypted Tunnel Meta Machine A (Local) Caller holds Outform GT SAVE mSave Pipeline Version Match Seal Validation B-bit Check (B=1?) F-bit Detection F=1 → REMOTE! G-bit Reset Seal Recompute + Commit F=1 detected Namespace Entry (Outform Proxy) type=01 (Outform) | F=1 | endpoint=machineB:port tunnelKey=K_AB | version=V7 | perms=RWE HTTPS / RPC Tunnel Interface Encrypt with K_AB, send to Machine B endpoint Encrypted Tunnel TLS 1.3 + K_AB Meta Machine B (Remote) Target actual abstraction mLoad Pipeline Permission Check Bounds Check Version Match (V7) MAC / Seal Verify G-bit Reset CR Write + Shadow validated Namespace Entry (Inform type) type=01 (Inform) | F=0 | local abstraction body version=V7 | perms=RWXE | location=0x1234 Tunnel Receiver Decrypt with K_AB, dispatch via mLoad F-bit Detection in mSave 1 SAVE CR, slot Caller saves GT to c-list 2 mSave checks F-bit Target slot: F=1? F=0 F=1 Local commit Route to tunnel HTTPS/RPC encrypted with K_AB F-bit is set in the namespace entry word1 when FamilyRegistry binds a remote endpoint. Caller code is unchanged. Network transparency: same SAVE instruction, same mSave pipeline — F-bit routes automatically. Tunnel Revocation via GC Version Bump Active Tunnel Machine A: Outform GT v=V7 Machine B: Inform entry v=V7 Versions match → tunnel open GC Runs on Machine B PP250 Phase 4: FLIP Global version → V8 Entry version bumped to V8 Tunnel Revoked Machine A Outform still v=V7 Machine B entry now v=V8 Version mismatch → FAULT Machine A's next SAVE to this entry fails at mSave stage 1 (version mismatch). The tunnel is atomically and silently revoked. No explicit "disconnect" message needed. To re-establish: FamilyRegistry mints a new Outform GT with v=V8 and fresh tunnel key K'_AB. Explicit, auditable, no stale credentials lingering. Outform GT: The Remote Capability Version 7 bits Index 17 bits Perms 6 bits 01 Outform Namespace Entry (word1): F=1 foreign B bind G gc word2+: tunnel key K_AB, remote endpoint URL, FamilyRegistry binding ID Network Transparency Principle The caller's code is identical whether the target is local or remote. The F-bit in the namespace entry routes automatically. mSave detects F=1, encrypts, and tunnels. mLoad on the remote side validates the GT exactly as if local. GC version bump revokes the tunnel atomically — no protocol needed.
Meta Machine A (local)
Meta Machine B (remote)
F-bit detection / revocation
mSave pipeline
Outform GT / namespace entry
Encrypted tunnel