Module transport 

Fail-closed transport for four verifier contexts sharing one SHA-256 lane.

Context requests first enter a speculative one-entry launch register. A request is acknowledged only on the following edge, when the unchanged, still-canonical payload is actually launched into the compression lane. The launch edge also writes its exact tag into a 64-entry synchronous expected- return memory. A due bitmap and circular pointer advance across both tokens and bubbles, aligning that tag with the lane’s exact 64-cycle response.

Returned tags are compared with the delayed expected tag before routing. This detects loss, extras, mistiming, malformed ownership, and a perfect swap of two otherwise canonical in-flight tags. Any outbound rejection or return integrity failure suppresses launch, capture, and routing in that cycle. The enclosing cluster registers the failure as reset-only poison and asserts transport_abort to every context on the following cycle.

This is source and behavioral-simulation architecture. It is not generated- RTL, synthesis, resource, timing, route, or hardware evidence.

Structs

VerifyTransport

Expected-tag transport controller with one speculative launch register.

VerifyTransportControl

Narrow resettable control for VerifyTransport.

VerifyTransportInput

Inputs to the four-context expected-tag transport.

VerifyTransportOutput

Observable launch, route, and integrity signals.

VerifyTransportSelection

Fair speculative-capture decision.

Constants

VERIFY_CLUSTER_CONTEXTS

Number of contexts sharing one verifier lane.

VERIFY_DIAGNOSTIC_ISSUE_REJECT

At least one presented context request was noncanonical or changed while held.

VERIFY_DIAGNOSTIC_RETURN_FORMAT

Returned tag was outside the canonical verifier task subset.

VERIFY_DIAGNOSTIC_RETURN_OWNER

Returned tag named a physical context outside this four-context cluster.

VERIFY_DIAGNOSTIC_RETURN_TAG

Returned tag was not bit-for-bit equal to the delayed expected tag.

VERIFY_DIAGNOSTIC_RETURN_TIMING

Lane-valid did not match the token/bubble due in this cycle.

VERIFY_EXPECTED_TAG_ADDRESS_BITS

Exact tag-memory address width for the 64-cycle lane.

Functions

compression_input_equal_kernel

Compare complete compression payloads without relying on aggregate lowering.

select_verify_transport_request_kernel

Select one eligible request, optionally excluding the request being launched.

verify_transport_kernel

Launch-register, expected-tag, and exact-response routing transition.

verify_transport_request_is_canonical_kernel

Validate a request against the verifier subset and its physical assignment.