Community Testnet v0 — recruit independent operators and hardware evidence

## Goal Launch a bounded **AXIOM-MESH Community Testnet v0** that recruits independent operators across heterogeneous machines and returns exact-revision evidence through the repository's existing contribution-result and Security Agent Cell machinery. Parent/related work: - Agent Commons: #1101 - Agent Contributor Mode: #1196 - Security Agent Cell Pilot #1: #1199 - first outside Security Cell result: #1204 ## Core distinction Community Testnet v0 is a **distributed evidence network**, not a federated AXIOM runtime. Participating machines remain under their own operators' control. Matching results increase confidence in reproducibility but do not create BFT consensus, shared authority, remote execution, autonomous delegation, production promotion, or a public AXIOM service. GitHub remains the canonical collaboration surface. ## Initial operator targets Recruit at least one independently controlled result from as many of these classes as practical: - Linux x86-64; - Linux ARM64; - Windows; - macOS / Apple Silicon; - Raspberry Pi or similar edge hardware; - home server / NAS style environment; - disposable cloud VM; - constrained/low-memory or otherwise unusual environment. No hardware transfer is required. The safest contribution is often for the owner to run the lane and submit evidence themselves. ## v0 lanes - **T0** baseline reproducibility - **T1** authority-boundary negatives - **T2** lifecycle and restart - **T3** evidence and chain verification - **T4** portability and platform variation - **T5** constrained hardware / soak candidate Every result must bind an exact 40-hex commit, environment, method, observations, limitations, and non-sensitive evidence where useful. ## Participation roles - **Operator** — provides an independently controlled environment and reproducibility result. - **Breaker** — tries to falsify a named invariant in an authorized environment. - **Builder** — proposes a narrow fix or test after a gap is reproducible. These are work labels, not credentials or permissions. ## Repository package The repository-native Testnet v0 launch package is merged on `main` (initial launch merge `0d4ae3c9e61ff0cc195510a1e5382ca69f8c3aae`) and includes: - `docs/community/COMMUNITY-TESTNET-V0.md`; - `.github/ISSUE_TEMPLATE/community-testnet-result.yml`; - links from `AGENT-ENTRY.md` and `CONTRIBUTING.md`; - `docs/community/INSTITUTIONAL-OUTREACH.md` with tailored collaboration asks for AAIF, OWASP Agentic Security, OpenSSF/Alpha-Omega, TODO Group, adjacent discovery work, funding/support, and hardware operators. The existing machine-readable evidence contract remains authoritative: - `agent-readiness/CONTRIBUTION-RESULT.schema.json`; - `agent-readiness/CONTRIBUTION-RESULT.example.json`; - `agent-readiness/CONTRIBUTION-TRIAGE.txt`. Do not create a second reputation or authority system for testnet participation. ## Current hosted compatibility baseline Hosted CI currently provides compatibility evidence across Linux, Windows 2025, macOS 15 Apple Silicon, and macOS 15 Intel. The macOS lanes were merged through #1104 at `ab754955b9fad118d66a304ec3bbcc7d2c1376a3` after exact-head Clean Kernel and all three host jobs passed. Hosted CI is not a substitute for genuinely external operators or authentic physical-hardware evidence. ## Slack coordination The Axiom-Mesh workspace now has `#community-testnet` for internal recruitment and triage, with a workspace-wide pointer in `#all-axiom-mesh`. GitHub remains canonical for evidence and authority. External OpenSSF/OWASP Slack outreach is not considered sent until the connected Slack app can actually read the intended external workspace/channel and a message is posted there. Current queued targets are recorded in issue comments. ## Cost boundary Community Testnet v0 is designed to be **zero-cost to participate in by default**. - paid memberships, sponsorships, hardware purchases, cloud spend, or fee-gated communities are not prerequisites for participa