Welcome to Cavaridge Docs
Welcome. These docs cover the Cavaridge™ platform — every customer-facing product, the public API, MCP integration, and the platform-level concepts (Universal Tenant Model, RBAC, Pulse, the AI gateway).
Where to start
Section titled “Where to start”- MSP admins or technicians → start with Cavaridge Operations, then AEGIS.
- Healthcare practice managers → Healthcare BAA + the no-PHI runtime gate first.
- Developers + integrators → Public API overview and MCP integration.
- Solo operators / consumers → Cavaridge AI or PawVault.
- Anyone who reaches a term they don’t know → the Glossary.
What’s where
Section titled “What’s where”- Platform — concepts that apply across every product (UTM, RBAC, Pulse, the AI gateway, observability, healthcare).
- Products — one root per active customer-facing product.
- Public API — REST surface, versioning policy, idempotency, error contract.
- SDKs — TypeScript / Python / Go (auto-gen when PROD-06 ships).
- MCP integration — connect Cavaridge as an MCP server.
- Guides — cross-product how-tos and integration recipes.
- Changelog — per-product feeds plus the unified rollup.
How these docs work
Section titled “How these docs work”- Searchable. Lunr full-text by default; AI-assisted search lands once Cavaridge AI sandbox key wires up.
- Versioned. Every page is pinned via
versions:front-matter. - Runnable. Pages whose code examples are CI-tested carry
runnable: true. - Honest about gaps. Every “coming soon” has a tracked issue and target window.
Brand standards
Section titled “Brand standards”Cavaridge™ is the trade name. The user-facing AI personality is Ducky.
The internal AI gateway runtime is referenced as the Cavaridge AI gateway
in user-facing docs.