Thanks for helping improve the Autonomi developer docs.
- Read
README.mdfor the repo scope, structure, and publishing model. - Read
CLAUDE.mdfor terminology, style, and verification rules. - Use
planning/verification-workflow.mdfor the requiredsource audit -> draft -> verifyworkflow.
- Open a pull request for changes to
main. - Keep each change focused and as small as possible.
- Treat merged upstream code as the technical source of truth.
- Do not document unmerged branches or future behavior as if it is current.
- Keep provenance and evidence narration out of rendered docs prose.
- Identify the page type and relevant source repos before editing.
- Use
current-merged-truthunless a task explicitly activatestarget-manifest. - Update verification blocks when you change a verified page.
- Use terminology from
CLAUDE.mdexactly. - Keep code examples complete, runnable, and explicit about which developer interface they cover.
- Use the four primary interface labels consistently in navigation and overview pages: SDK, MCP, CLI, and Direct Rust.
- Keep Core Concepts tool-neutral and use
How-To Guidesfor shared or cross-interface task pages. - Keep pages interface-pure unless they are explicitly comparison or chooser pages.
- Use tabs for languages or equivalent interfaces within one interface, not for switching between interfaces.
- In user-facing prose, name the specific tool or interface rather than using abstract words like
routeorpath. - Inside each interface section in
SUMMARY.md, use a landing page first and nest child pages beneath it. Add landing pages for How-To Guides or Reference when a section has enough pages to benefit from that extra layer, and omit empty groups.
- Explain what changed and why.
- Call out any upstream repo, ref, or commit drift the change resolves.
- Note any verification work or GitBook rendering checks you performed.
README.mdCLAUDE.mdplanning/verification-workflow.mdrepo-registry.ymlcomponent-registry.yml