> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/documentation-operations/maintenance-policy.md).

# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xyo.network/documentation-operations/maintenance-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.