W0W operators are independent infrastructure participants. They verify report structure, freshness, identity binding, policy commitments, and replay protection before signing. They do not invent QUBE data, custody user funds, or control the POPchain ledger.
Current onboarding posture
- Review the public Command Center, AVS/W0W architecture, and report boundaries.
- Run a testnet-compatible verifier against published report fixtures and evidence roots.
- Register only after operational, key-management, monitoring, and incident contacts are reviewed.
- Start under a staged, non-automatic-slashing policy with bounded task value and explicit incident procedures.
POP is not asking operators to trust a narrative. The intended path is inspectable: observe the records, reproduce verification, then opt in to a clearly scoped role.