RBAC personas
Three preset personas drive the access-control matrix on the demo. Each carries a clearance level (Qdrant payload range filter) and a set of roles (Qdrant payload match-any filter). The stylefield is appended to the synthesizer's system prompt so the same retrieved chunks produce visibly different answers per persona. This page reads the dispatch table directly from the backend — there is no client-side copy that could drift.
org_id: demo · default: engineer
Engineer
key: engineerclearance: 2roles (Qdrant must-filter: match-any)
synth style (appended to system prompt)
Write for a senior engineer. Use precise technical language, name the underlying mechanism, and prefer concrete code snippets or commands over abstract description. Skip the executive summary -- this reader wants the wire-level detail.
Compliance
key: complianceclearance: 3roles (Qdrant must-filter: match-any)
synth style (appended to system prompt)
Write for a compliance / legal reviewer. Foreground the regulatory citations, control IDs, and risk vocabulary. Highlight gaps and required attestations. Hedge claims that are not directly supported by an authoritative source.
Executive
key: executiveclearance: 3roles (Qdrant must-filter: match-any)
synth style (appended to system prompt)
Write for a busy executive. Lead with the bottom line in two sentences. Quantify impact in dollars / risk percentage / headcount where the source supports it. Skip implementation detail unless it changes the decision.