Maintenance Policy

Ownership, verification, and automated quality controls for XYO documentation.

Ownership

Area	Owner	Review interval
Developer onboarding and cookbook	XYO Developer Relations	Monthly
Public SDK reference	XYO SDK maintainers	Every package release and monthly
Network and operational guidance	XYO Layer One maintainers	Monthly and before Mainnet changes
Release notes	Release owner for the affected library	Every meaningful release

Operational pages must include a clear owner in this table and must be reverified when a related package or network behavior changes.

Automated checks

Every pull request checks:

• internal links and navigation targets;

• balanced GitBook blocks;

• the public npm package allowlist;

• documented package versions and deprecation status; and

• imports used by public SDK examples.

A scheduled monthly run repeats the registry and import checks even when no documentation pull request is open.

Freshness review

The monthly reviewer should:

1. Review pages affected by package releases.

2. Confirm public npm availability and exported entry points.

3. Remove CLI, private-repository, internal-service, and unpublished-API references.

4. Test the primary Local, Sequence, and Mainnet reading paths.

5. Update the verification date and open migration work where behavior changed.