A cell transition is accepted under its current state and authority.
Public proof record network
Manufacturing common knowledge
A network is a way to know which receipts became history.
Participants need not run the same interface or trust the same operator. They need a finality rule, a verifiable history, and enough evidence to reject a fork that violates either.
01
The common record
From a local turn to a finalized fact.
Committee members bind the proposed block with hybrid classical and post-quantum identities.
A threshold of authorized members chooses one history under the federation rule.
Turns compose into an aggregate whose public inputs bind the anchored head and history.
A consumer checks the succinct evidence rather than replaying the whole world.
02
Implemented organs
Federation is more than a consensus noun.
Finality
Hybrid quorum certificates
Committee signatures, equivocation refusal, epoch membership, and certificate verification are executable paths.
Key ceremony
DKG and threshold custody
Distributed key generation, FROST signing, threshold opening, revocation, and epoch rotation are protocol components.
Fairness
VRF and beacon
Unpredictable committee choices and public randomness feed elections, games, and allocation.
Succinct history
Recursive verification
The fold and light-verification path is wired; its strongest claim remains conditional on the explicitly named proof-engine floor.
03
Deployment record
Running code is not the same claim as a public network.
exercised
Multi-node federation
The repository carries live-run artifacts for committee finalization and cross-node attested turn streams.
public surfaces
Arcade and development viewers
Some interfaces are public, but their availability does not imply that every turn currently settles through a production federation.
not production
Security-critical network use
The integrated system has no independent external audit and no claim of a stable public mainnet. Current public services are development surfaces.