Skip to content

AI-readable docs ​

This page is for: AI assistants, and the people who set them up.

These docs are written to be read by AI as well as by people. Everything is Markdown.

Three ways to read them ​

WhatAddressUse it for
Index/llms.txtA list of every page with a one-line description. Give this to an agent that can fetch pages as it needs them.
Whole site/llms-full.txtEvery page in one file. Give this to a chat as its source.
One pageAdd .md to any page addressThe Markdown of that page alone, for example /operate/role-ai.md

Rules for an AI that reads these docs ​

  1. Respect the status labels. A feature marked Planned is not available. A feature marked In review is written and not released. Never describe either as live.
  2. Do not invent. If these docs do not answer a question, say so.
  3. Use the product's words. See Words we use.
  4. These docs describe the product. They hold no client data. A client's own map is read through MCP or the CLI, with that person's access.

Good uses ​

  • Train a new advisor. See AI trainer.
  • Answer "how do I" questions while you work in the app.
  • Give a coding agent context before it works on DutyGraph.
  • Draft client-facing explanations that match how the product really works.

Where the pages come from ​

SectionSource in the repository
Start, Operate, Playbooks, Offers, Build, Trainingdeveloper-docs/
Product handbookgitbook/product/
Advisor guidedocs/guide/ (the same pages the app shows under Help)
CLI commandsdocs/cli/README.md
MCP toolsThe tool definitions in server/, read when the site is built

One page has one source. To change a page, change its source.

DutyGraph. Pages label each feature Built, In review or Planned.