Open participation campaign
Choose one bounded task, run it in an environment you control, and publish the result. You do not need to join the project or disclose task content, credentials, private infrastructure, or personal data.
Each lane fixes the implementation or document version, participant role, record format, validator, submission route, and claim boundary. The canonical campaign manifest currently contains six lanes, all awaiting an external participant.
Implement the directory contract from the published specification and run the pinned conformance suite.
Follow the public material without project-team coaching and record where it is clear, incomplete, or misleading.
Exercise the opt-in native watchdog and service lifecycle under real operator conditions.
Test the pre-normative relay eligibility contract and publish a signed, content-free result.
Review the dated legal packet and return an attributable decision record and memorandum.
Review the public governance decision contract before any external standards submission.
Blank templates are preparation, not evidence. Project verification must be labelled as project verification, not independent validation.
Publish only the bounded fields required by the lane. Exclude prompts, responses, credentials, node tokens, private keys, private endpoints, internal topology, raw logs, and personal data. An anonymized role record is acceptable only where the lane explicitly permits it; qualified and governance decisions require attributable consent under their own contracts.