Retrieval index
Your records are chunked and embedded into a tenant-isolated vector index. The same query never crosses tenant boundaries.
Cited answers grounded in your tenant's records. Agents that propose changes, and a human approves before they touch your data. Every action is logged.
The Copilot is a tool, not a vibes machine. Three properties hold for every interaction, including agent runs.
Every factual claim resolves to a record in your tenant, clause, document, evidence, finding. URLs that survive a tenant export.
Anything that writes data is staged as a proposal. A human approves. Tenants can require dual approval on sensitive entities.
Prompts, retrieved sources, model output, approval decisions, and final state, all stored, all exportable.
Retrieval reads from your scoped requirements, controlled documents, validated evidence, audit reports, findings, CAPAs and risks. Citations resolve to live records.
Three artifacts cover this: the Q4 2025 complaints trend report (chart + commentary), the management review minutes from January, and two CAPAs opened from recurring root-cause patterns. The internal audit found this clause conformant with one OFI on data granularity.
Agents can draft audits, CAPAs, risk entries, document outlines, and evidence links. Each is staged as a proposal that a human reviews, diff visible, full citations.
The Copilot runs scheduled passes for things that are easy to forget: expiring evidence, overdue findings, untreated high risks, stalled CAPAs. Surfaced as actionable cards, never as noise.
The pieces that make the trust guarantees real.
Your records are chunked and embedded into a tenant-isolated vector index. The same query never crosses tenant boundaries.
Every retrieval is post-filtered against the requesting user's site, role, and scope memberships before reaching the model.
Generated writes are persisted as `ai_action_proposals` with diff, source list, and reviewer assignment. The model never writes directly.
Prompt, retrieved sources, model output, decisions, and resulting record IDs land in `ai_audit_log`, exportable as CSV/PDF for any audit window.
A 45-minute working session. Bring an open finding and the related documents. We index, you ask, the team approves.