Skip to main content

​
orova-docs — agent playbook

Public docs (Mintlify). GitHub: orova-ai/orova-docs. Hosted at https://docs.orova.ai.

​
Linear labels (required)

  • Stack: frontend (docs site) unless the ticket is purely a backend contract note — then use backend and still update the matching pages here
  • Env: dev | platform | enterprise — where the bug was observed or where the change must work. Not where we develop first.
  • Type: bug | feature | improvement
Team: Orova AI. Issue IDs: ORO-….

​
Before coding

Every issue needs a Done when section with 3–5 checkable items. Add it on the Linear ticket if it is missing. Do not start implementation until that exists.

​
Verify order (local → dev → platform)

  1. Reproduce, fix, and prove Done when locally (Mintlify preview against this directory).
  2. Only then open a PR. Do not publish docs to “see if it works” unless the ticket says so.
  3. Production docs publish only when explicitly authorized.
When runtime contracts change in orova-api, orova-brain, or the widget, update the matching pages in the same body of work.

​
Pull requests

  • PR title and body must link ORO-….
  • Keep the diff scoped to that ticket.
  • Do not put customer names in commit messages or PR titles.
  • Never merge PRs. Humans merge.

​
Linear status

Do not move issues to In Review, Done, or QA. Humans own those transitions.

​
Branches

Status site: https://status.orova.ai. This repo is not on the customer runtime path.

​
Bugs

Reproduce first. Attach evidence (screenshots) on the Linear ticket before asking for In Review. Do not change Linear status yourself.

​
This package

Mintlify MDX (docs.json). Guides, API reference, SDKs, widget, brain, tools, integrations. No package.json required in this checkout. Never store credentials in Markdown or source.