Keyboard shortcuts

Press ← or → to navigate between chapters

Press ? to show this help

Press Esc to hide this help

Initialized endpoint control protocols

Abstract

Persistent endpoint states, agreed public roots and sender-local bit queries generate actual support and protocol-realized transitions.

Definition 1.1 (A source-local public prefix protocol).

Formalization. D5/S3/ObserverMemory/Algorithms/InitializedControlProtocol.EndpointProtocol (✓ std3).

Source. Repository-derived.

Commentary.

A public bit prefix determines either a tagged sender-local Boolean question or a leaf. A left question reads only the old left state and a right question reads only the old right state. Each leaf output takes only its own old local state and the transmitted Boolean string. Query labels are evaluator data reconstructed from the public prefix, and the leaf outputs never read them as an additional channel.

All universe levels u,v,w,x are arbitrary. rightSender and leftSender test the right and left question tags of a trace entry. The evaluator is PassivePolicyNormalization.execute. Its input and the two local carriers are arbitrary types. Finite fuel is evidence of termination on the actual input; it is not a uniform tree depth or an endpoint runtime argument.

Definition 1.2 (Initialized persistent endpoint compliance).

Formalization. D5/S3/ObserverMemory/Algorithms/InitializedControlProtocol.Controller (✓ std3).

Source. Repository-derived.

Commentary.

The original source is the direct product of the data vector and its control coordinate. The action alphabet includes every data basis translation, the control basis translation, and every established controlRewrite. A fixed complementary pair of submodules supplies the two original readouts.

Reachable is the least predicate containing all initial pairs and closed under successful commits; the formula gives its induction characterization. Each endpoint initializes from its own original projection and reads that projection back exactly. Operational reachability begins with the full local initialization product and closes under successful executions and the two local leaf commits. Both local carriers must be exactly projections of this operational support.

Compliance requires locally selected roots to agree on actual support, finite termination there, both prescribed source readout equations after every execution, and zero-bit basis translations. Neither local carrier nor the root type is assumed finite. The readout equations specify correctness and do not implement a centralized transition.

Definition 1.3 (Actual support determines a total realized step).

Formalization. D5/S3/ObserverMemory/Algorithms/InitializedControlProtocol.step (✓ std3).

Source. Repository-derived.

Commentary.

For an actual reachable pair and a public action, finite termination selects a successful evaluator transcript. The successor consists of the two local leaf updates on its Boolean responses. Operational closure places it back in the actual reachable subtype. Step cost is the transcript length. Existing runWord and Comm supply word execution and cumulative cost.

References