Appendix H — Self-Hosted Documentation Architecture

docs.ionon.ai is part of the security and governance architecture, not only a marketing site.

H.1 Documentation source of truth

The recommended repository contains:

/docs
  /concepts
  /architecture
  /identity
  /policy
  /wallet
  /interoperability
  /network
  /economics
  /genesis
  /governance
  /security
  /developers
  /trust
/data
  canonical-registry.json
  tokenomics.json
  chain-status.json
  release-manifest.json
/schemas
  agent-birth-certificate.schema.json
  policy-passport.schema.json
  order.schema.json
  evidence.schema.json
/assets

CI should fail the build if tokenomics do not sum to 100M, if canonical contract strings diverge between pages, if a live status lacks an evidence link, if links are broken, or if a versioned schema changes without a changelog.

H.2 Public documentation navigation

The external experience should behave like a premium GitBook-class product while remaining fully under IONON control:

Overview → Concepts → Architecture → Agent Identity → Policy Engine → Wallet → MCP/A2A → Network → Tokenomics → Genesis → Governance → Security → Developer → Trust Center → Changelog.

The build should be static-first and deployable behind IONON-controlled DNS/CDN infrastructure. Search can be generated locally from the content corpus so the documentation does not require an external SaaS search provider.

H.3 Machine-readable trust registry

The docs package should publish /data/canonical-registry.json and expose the same content from ionon.ai/verify. Each entry carries chain, address, status, purpose, evidence URL, activation block/version and deprecation state.

References

Whitepaper references