OpsTech Platform Documentation

One source of truth for the platform — kept fresh by AI agents.

Pick your audience

Product

Mission, plans, prospect FAQ. For prospects, sales, and the product team who want to understand what the platform offers and why.

→ Product overview

Operational

Runbooks, on-call procedures, incident response. For the ops team running the platform day-to-day.

→ Operational index

Technical

Live API reference (Swagger UI), event-flow diagrams per service, cross-component system map. Auto-synced from opsclaw-product/tools/api-inventory/ on every push to main.

→ Technical index

How this site stays current

Every PR in opsclaw-product that adds, removes, or changes an HTTP route, an MCP tool, or a webhook receiver MUST update the matching OpenAPI fragment and its Mermaid diagram — enforced by the api-drift CI step (check-drift.sh). On every push to opsclaw-product:main touching those artefacts, a workflow (docs-propagate.yml) opens an automatic PR here that vendors the latest snapshot under docs-site/src/content/_synced/. Merging that PR rebuilds the technical section you see above.

Two CI gates protect the rendering surface:

docs-drift.yml Check A (warning): the synced _synced/openapi/ diverges from opsclaw-product:main (snapshot is stale).
docs-drift.yml Check B (failure): a hand-edit to an auto-generated technical/services/<svc>.mdx page was detected via banner mismatch.

Hand-authored sections: Product and Operational are edited normally through PRs to Juwebien/opstech-site. Technical is read-only here.