Whitepaper V4.1
27. Documentation as Infrastructure
IONON documentation is generated from a canonical source and machine-readable registry, not manually rewritten across five websites.
docs.ionon.ai should be self-hosted. The repository contains Markdown/MDX, contract registries, JSON schemas, release manifests and static assets. CI validates broken links, contract-address mismatches, tokenomics sums, version numbers and status tags before publishing.
V4 adds machine-verifiable release controls: every documentation release produces a manifest containing SHA-256 hashes of the whitepaper, registries and schemas; CI refuses publication if tokenomics do not sum to 100%, a canonical address diverges between pages, a VERIFIED-PUBLIC claim lacks an evidence URL, or a deprecated address appears without a deprecation label.
The self-hosted docs package should include /.well-known/security.txt, /.well-known/ionon.json, JSON Schema files for identity/policy/order/evidence, an OpenAPI contract for public interfaces when those endpoints are released, signed release notes, sitemap/robots, and a local search index so the documentation can operate without a third-party documentation SaaS.
Public docs should expose:
- Concepts;
- Architecture;
- Agent Identity;
- Policy Engine;
- Wallet & Money Router;
- MCP and A2A integration;
- IONON Network;
- Tokenomics;
- Genesis CCA;
- Governance;
- Security;
- Developer APIs;
- Canonical contracts;
- Trust Center;
- Release notes;
- Risk disclosures.