Control framework · v0.1.0
Controls that can be tested, evidenced and owned
Each requirement names a decision boundary, a practical test and the evidence a reviewer should expect. The machine-readable source is available as JSON and YAML.
Identity and authorization
| Control | Requirement | Minimum evidence |
|---|---|---|
| ID-01 | Bind every request to an authenticated human or service identity. Refuse before retrieval when identity is absent. | Authentication log; request trace |
| AU-01 | Apply policy before schema or semantic context is shown to the model. | Policy decision; retrieval trace |
| AU-02 | Check every object and operation in the parsed query against current policy. | Parsed query; decision; execution trace |
| AU-03 | Separate read and write authority and keep writes disabled by default. | Grant record; source privileges; refusal test |
Semantics and query safety
| Control | Requirement | Minimum evidence |
|---|---|---|
| SE-01 | Resolve material metrics to versioned definitions approved by named owners. | Definition; approval; answer trace |
| SE-02 | Record the version and provenance of each material definition used. | Definition history; answer trace |
| QS-01 | Allow only approved statement classes and a single statement. | Parser verdict; refusal trace |
| QS-02 | Use a source principal that independently limits reachable data and actions. | Source grants; independent probe |
| QS-03 | Enforce query time, row, memory and cost limits. | Limit configuration; execution log |
Verification, refusal and lineage
| Control | Requirement | Minimum evidence |
|---|---|---|
| VE-01 | Increase verification strength with decision impact and report its state. | Risk policy; verification trace |
| VE-02 | Never represent an unavailable verifier as a pass. | Outage test; answer payload |
| RF-01 | Refuse questions that require absent measures, dimensions or definitions. | Question set; refusal trace |
| RF-02 | Refuse without revealing restricted object names or values. | Response; disclosure review |
| LN-01 | Retain the query, objects, policy, meaning, data state and verification result. | Trace; query; lineage record |
Operations
| Control | Requirement | Minimum evidence |
|---|---|---|
| OP-01 | Trigger regression evaluation after material schema, semantic, policy, model or data changes. | Change record; evaluation report; release decision |
| OP-02 | Revoke access or disable the agent without deploying code. | Revocation log; kill-switch test |
Implementation note: a product feature can support a control, but the organization operating the system still owns configuration, review, evidence retention and risk acceptance.