Active system map

Production signer

Sha256SignerTop specializes the production top around three replicated Sha256LaneLocalCluster instances. Each cluster has four SingleContextWorkEngine contexts and one 64-round SHA-256 compression lane.

The global top selects a cluster only for beat zero, then holds that cluster for the complete frame. Output frames also remain noninterleaved. Local result capture can release a context before a stalled global consumer accepts the final beat; registered ownership preserves the held result.

Production verifier

Sha256VerifierTop specializes three Sha256VerifierCluster instances. Each cluster has four verifier contexts, one compression lane, and an expected-tag transport that aligns each issued token with its exact 64-cycle return.

Any malformed, missing, extra, mistimed, misrouted, or rejected return poisons the cluster. The top registers global poison, broadcasts peer abort, drains identified error completions, and does not silently reuse a suspect context.

What is historical

The ShaTransportFabric module models nine contexts sharing three lanes and has extensive fairness and tag-routing tests. It was an important prototype for parallel scheduling, but the active signer and verifier use twelve contexts arranged as three autonomous four-context clusters.

Do not copy the historical 9-context count into production throughput, state, or resource calculations.

Profile coverage

Evidence boundary

The hierarchy described here is source structure. Mapped instance counts, resource use, timing, placement, route, and physical throughput require the corresponding higher evidence tier.