The policy in one sentence
Accord v0 is alpha, testnet-first software and NOT CERTIFIED FOR MAINNET.
That sentence should appear consistently in docs, site copy and AI-facing summaries because ambiguity around money movement is dangerous.
Why signed manifests matter
A rail implementation can include scripts, contract bytecode, compiled trees and operational assumptions. A signed audit manifest gives the SDK and operators a concrete identity to check before allowing production behavior.
Without that evidence, the safe default is denial.
What builders can do today
Builders can run local demos, mock rail flows, conformance tests, MCP tool gating prototypes and testnet experiments. Those activities are valuable because they validate the protocol lifecycle without pretending the mainnet risk review is complete.
Teams preparing for production should focus on audit evidence, verifier assumptions, spending policy, signer operations and incident response before any real-fund deployment.
FAQ
Can I use Accord with real funds today?
The current public status says no by default. Real-fund production use is blocked until signed audit manifests allow it.
Are dangerous overrides acceptable for production?
No. Overrides are for research and controlled testing, not production guidance.
Check public status
Confirm the current production gate before any real-fund workflow.