Introduction

​

Start here

​

What’s in these docs

• Get started — what the product does (Platform overview), a 10-minute walkthrough per role (Quick start), and the full install + configuration reference (Installation guide).
• Run & operate — day-2 operations: scanner fleet, queues, metrics, readiness, backup (Operations guide); sizing and scale triggers (Capacity model); symptom → resolution (Troubleshooting).
• Security & trust — the complete review package for your security team: Security review, Threat model, every Microsoft Graph permission used and why (Permissions manifest), and exactly what data is acquired, derived, retained, and never stored (Data catalog).
• Reference — every HTTP endpoint with its required permission (API reference), the module architecture (Architecture), and every database table (Data schema).
• Design (UX) — the “Registry” interface’s grounding and specs: the persona & activity reference (Personas & activities), the information architecture (Domain-owner IA), the visual language & review-input spec (Design language), and the relational visualizations (Relational views).
• Licensing & releases — Pricing & licensing (per active user, never headcount) and the release notes.

​

Conventions

• Honesty labels. GET /api/ready reports each integration as mock, live, blocked (enabled but prerequisites unmet), or disabled. The documentation uses the same vocabulary — a capability is described as built + validated live, built + gated, or not built, never vaguer.
• Versioning. Releases are dated (26.7.16.5 = the sixth release cut on July 16, 2026). Your deployment reports its version at GET /api/controlplane/telemetry-preview.
• Demo data. All example people and documents belong to the fictional Meridian Grove Holdings — nothing in fixtures or the demo is real data.
• Source-available. The platform’s full source, tests, and architecture decision records are public at github.com/clarkdickens/FindMyData.