Module cluster 

Four-context SHA-256 verifier cluster with fail-closed lane ownership.

VerifyClusterCore keeps the compression lane injectable: it exposes one prepared lane request and consumes one exact-latency lane response. This is the focused behavioral-test boundary. VerifierCluster closes that boundary around one lane implementing the shared CompressionLaneComponent contract; nested SynchronousDQ connectivity adds no protocol register.

Beat zero is fairly allocated from registered idle state and locks one physical context for exactly 35 accepted beats. Keep, last, and job-ID defects remain per-job framing errors inside that context; they never poison the cluster. Generations have separate assigned and next values so beat zero increments the reuse counter immediately while every beat and task of the accepted job continues to use its original assignment.

Results cross a one-entry registered elastic slot. Capturing a child result releases that child before external delivery, and a transferring slot may be replaced on the same edge. The first fatal edge suppresses transfer and turns an already-retained clean slot into an identified transport error before that slot can transfer. Transport, child audit, or ownership failures set reset-only cluster poison. The registered poison aborts every live context on the following cycle and prevents all later frame admission, lane launch, and response routing until shared reset. Already-retained error completions may still drain so software is not left waiting without an identity.

A child response rejection is a containment-edge exception to ordinary ready/fault intuition. Its exact response must first be physically presented, so same-cycle stream credit cannot depend on the rejection without forming a hierarchy loop. One already-advertised beat may therefore transfer while fault rises. That beat is reported accepted, delivered to the selected child, and retains its job identity; registered poison aborts it on the next cycle. Result transfer and capture are still suppressed immediately. Context stream, response, result-grant, generation, and abort fields are constructed as four direct child literals. No dynamically mutated aggregate can couple one protocol’s fault dependency into another protocol field.

external_abort is a registered-parent transition command. On its command edge it changes only cluster D state: poison and its diagnostic are latched, and any frame lock is cleared. It deliberately has no combinational effect on stream, lane, response, result, fault, or diagnostic outputs. The parent must therefore issue it only after withdrawing this cluster’s stream valid and result ready. Registered local poison provides complete containment on the following cycle; at most one lane launch and one routed return per peer may advance on the transition edge, and one internal result capture may also occur. All belong to already-accepted jobs.

The implementation has source and behavioral-simulation evidence only. It makes no emitted-RTL, synthesis, resource, timing, route, or hardware claim.

Structs

VerifierCluster

Four verifier contexts behind one injected exact-64-cycle compression lane.

VerifyClusterControl

Narrow resettable ownership, result, and poison state.

VerifyClusterCore

Four verifier contexts plus transport, with the compression lane injectable.

VerifyClusterCoreInput

Injectable-core input, adding the shared lane’s combinational output.

VerifyClusterInput

External streaming interface for the production verifier cluster.

VerifyClusterOutput

Cluster status, diagnostics, injectable lane request, and registered result.

VerifyClusterSelection

Fair four-way context selection.

VerifyClusterTransportGateInput

Inputs to the independent-fatal transport gate.

VerifyClusterTransportGateOutput

Actual launch, acknowledgement, and response signals after fatal gating.

VerifyResult

One registered verifier result.

Constants

VERIFY_DIAGNOSTIC_CHILD_FAULT

A child latched a transport or final-accounting fault.

VERIFY_DIAGNOSTIC_CHILD_RESPONSE_REJECT

A child rejected a response that passed the cluster’s expected-tag gate.

VERIFY_DIAGNOSTIC_EXTERNAL_ABORT

A registered parent requested cluster-wide transport abort.

VERIFY_DIAGNOSTIC_OWNERSHIP

Registered frame ownership disagreed with child loading state.

Functions

select_verify_cluster_context_kernel

Select one of four eligible contexts with rotating fairness.

sha256_verifier_cluster_kernel

Native-lane wrapper retained for callers of the original free kernel API.

verifier_cluster_with_lane_kernel

Close the injectable core around one exact-64-cycle compression lane.

verify_cluster_core_kernel

Frame ownership, poison, result elasticity, and child/transport connectivity.

verify_cluster_transport_gate_kernel

Gate transport effects for causes independent of a child’s current response.

Type Aliases

ModularSha256VerifierCluster

Production verifier cluster linked to a separately generated full SHA lane.

Sha256VerifierCluster

Production four-context verifier cluster with one inline full SHA-256 lane.