Production launch acceptance

1. Finalize network, immutable token parameters, verified Semaphore deployment and registrar configuration. Publish a reproducible unsigned deployment package and its hashes.
2. Complete independent security and privacy review, including enrollment abuse, identity recovery, metadata correlation, dependency/artifact integrity, relaying, root updates and effective anonymity.
3. Select and integrate a person-verification provider. Document country access, cost, privacy policy, one-person enrollment, appeals and recovery. Cannabis must not collect identity documents. Review the registrar's operational controls.
4. Exercise the complete claim flow with independent participants and a verified group of at least 128 distinct people. Publish results and resolve material findings. Internal security fixtures do not establish real-person enrollment.
5. Resolve applicable issuance, promotion and privacy requirements; prepare required disclosures and environmental reporting.
6. Verify the owner's portable wallet recovery. Review actual network fees and specifically authorize funded costs. The owner reviews and signs production transactions.
7. Publish verified mainnet token, vesting, enrollment and Semaphore addresses, source/bytecode matches and a common claim opening with at least seven days' notice.
8. Run production enrollment, claim access, monitoring, incident response and an accessible private security-reporting channel.
9. Publish optimistic, factual community announcements, artwork and English video on authorized channels. Facebook and Instagram remain excluded. Approach exchanges only with the actual verified release and applicable requirements addressed.

Completion means functioning production operations and public claims under the published rules. Virality, listings and financial returns cannot be guaranteed.

The compute-service launch additionally requires a real requester-funded workload, protected execution against the worker-operator threat model, independently checked outputs, enforced resource limits and correct settlement of the 1% founder fee. Each advertised runtime and accelerator needs a validated confidential path. The guest-attestation integration and real-hardware validation milestone track part of this work.

Compute backing requires enforceable provider commitments, defined redemption terms, reservations that prevent overbooking, and a completed paid redemption with delivery and settlement evidence. These requirements are part of the production objective. See the compute economy and universal workload client. Consensus and the 99%/1% allocation remain as specified above.