# Agent-Explorable Documentation

Omnius documentation is exposed to agents through project-local AIWG-style bundles under `.aiwg/addons/`.

## Bundles

| Bundle | Purpose |
| --- | --- |
| `omnius-docs` | General Omnius docs entrypoint and feature guides |
| `omnius-rest-docs` | REST API docs entrypoint and endpoint-family map |

## Agent Use Pattern

1. Run `omnius discover "<need>"` or search `GET /v1/discovery`.
2. Expand the stable result with `omnius show <id>`.
3. Use `skill_list` or `/skills` when the entry points to a skill.
4. Open only the referenced guide or endpoint family.
5. Treat source files and live OpenAPI as canonical when docs conflict with code.

## Skills

```text
omnius-docs
omnius-inference-docs
omnius-tools-docs
omnius-integration-docs
omnius-version-compatibility-docs
omnius-realtime-docs
omnius-sponsor-docs
omnius-telegram-docs
omnius-ops-docs
omnius-rest-docs
```

## Maintenance Rule

When adding a major feature, add:

- a human guide or reference page
- a curated discovery override when aliases, relationships, or invocation mode need explanation
- an entry in README if it affects first-run understanding
- a docs skill or trigger if agents should discover it
- validation coverage if the feature has a machine-readable surface