Serialized circuit-evaluator machine front end #
Definitions for validating one self-delimiting input pair code input and
staging its two components on three work tapes. The higher-order dispatcher
places an evaluator core inside the valid branch, so malformed outer inputs
can never fall through into that core.
The language decided by evaluating a paired tagged-family code and input. Malformed outer pairs and malformed inner codes are rejected.
Equations
Instances For
The serialized circuit evaluator uses three work tapes.
Equations
Instances For
Work tape containing the tagged family code after staging.
Equations
Instances For
Work tape containing the primary input and, later, memoized wire values.
Equations
Instances For
Work tape reserved for the evaluator's unary gate counter.
Equations
Instances For
Rewind a validated paired input and split its two components onto the code and wire tapes. This machine assumes the outer input is canonical.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Validate and stage a paired input. Malformed inputs take a frame-preserving rewind branch and retain the validator's zero verdict.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Validate and stage a paired input before invoking core. The core occurs
inside the valid branch, so it is unreachable on malformed outer inputs.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Concrete front-end bound derived from the current validator, rewind, splitter, and conditional-composition contracts.
Equations
- Complexity.CircuitCode.Machine.pairStageTime inputLength = 4 * inputLength + 16
Instances For
Front-end overhead when the valid branch additionally invokes a core with the supplied time bound.
Equations
- Complexity.CircuitCode.Machine.evalFamilyTMWithTime inputLength coreTime = 4 * inputLength + coreTime + 17
Instances For
Fresh machine tapes before validation begins.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Auditable result of the pair-staging front end. The output is parked at cell one with its start invariant intact, so a later core can safely overwrite the staging verdict. Invalid encodings retain fresh work tapes and a zero verdict. Valid encodings expose appendable code and wire prefixes, including the left markers needed by later rewind proofs.
Equations
- One or more equations did not get rendered due to their size.