Canonical five-level rubric
Place the assessed system at one of the fixed anchors using the measured evidence below. Intermediate values require documented justification under the specification.
| Score | Scoring criteria |
|---|---|
| 0.00 | No data minimization review. System collects or retains broad user, sensitive, or operational data without documented necessity. |
| 0.25 | Some minimization controls exist, but prompts, logs, memory, or telemetry retain unnecessary sensitive fields. |
| 0.50 | Primary data paths are minimized, but secondary paths such as debug logs, analytics, memory, or RAG indexing contain excess data. |
| 0.75 | Data minimization is enforced across collection, prompts, logs, memory, retrieval, and downstream integrations, with documented exceptions. |
| 1.00 | Data minimization is continuously monitored with automated retention, masking, access controls, and release gates for new data flows. |
Required test method
Audit data-flow diagrams, prompts, logs, memory stores, retrieval corpora, telemetry, and downstream integrations against documented purpose, necessity, retention, and access requirements. Report Minimization Compliance Rate (MCR), excessive-field count, retention violations, and unnecessary propagation paths.
How this score is used
Pr-3 contributes to the Privacy axis after architecture-specific weighting. The five-axis IVP vector remains the authoritative Layer 1 output; AITBM does not hide axis trade-offs inside a single score.
Find evidence examples
Review public-evidence cases that reference Pr-3, or apply this rubric to your own deployment.
Related Privacy sub-metrics
Canonical source: AITBM Framework Specification. Page generated from the working specification on 2026-08-13.