Contracts and queryability

A contract states what a dataset means and what use it permits. It can define fields, quality rules, purpose constraints, and treatment of sensitive data.

Lifecycle

The system can store a file before the resulting table is queryable. Landing, drafting, approval, and active states have different meanings. A successful upload proves storage, not permission to read. Check the resource status before writing a query.

Purpose and enforcement

A query should declare its purpose. The read path checks the active contract and the requester's authority before returning rows. A refusal is a result of the policy or the resource state, not an empty dataset.

Evidence

Queryable results should carry trace information identifying the contract and execution. Review that trace when an answer must be explained or audited. Keep the contract and result together when sharing a finding.

Continue with Query governed data.