Do not launch to discover the story
Accord now has enough testnet evidence to be credible, but broad distribution should wait until the public surface is easy to verify from the outside. A launch should not ask readers to believe the protocol. It should route them to receipts, conformance, pilot records, provider onboarding and clear mainnet limits.
That is why manual indexing, HN, Reddit, X, Discord and mcp.so are deferred until the launch readiness gates pass.
What must be polished first
The launch package needs one golden path, consistent status language, Sage and Base proof narratives, provider onboarding, audit-scope clarity and mobile-friendly site pages. Those surfaces matter because most launch readers will not inspect the whole repository.
If status, roadmap, README, pilots and registry entries agree, agents and humans can reason about the project without private context.
Public launch is not mainnet launch
A public launch may announce the open standard, SDKs, schemas, conformance and testnet proofs. It must not imply that real-fund production rails are certified.
Mainnet promotion remains a separate P5 event requiring signed external audit manifests with exact artifacts marked mainnetAllowed: true.
FAQ
Why not post now?
Because the best launch is evidence-led. The remaining work is polish, onboarding and audit clarity, not attention.
Does launch readiness change mainnet status?
No. Mainnet remains NOT CERTIFIED FOR MAINNET until signed audit manifests allow exact artifacts.
Sources and references
Launch readiness document
Canonical launch gate checklist.
Open launch gates
Check what must be polished before HN, Reddit, X, Discord or mcp.so distribution.