Ggriotdocs

Query governed data

A governed query reads an active table under its contract. State a purpose that the contract allows and inspect the returned trace.

Before you begin

You need a table that is active and queryable. Open its detail page in Data → Catalog. Read its column names and contract first; a newly uploaded file may still be in a landing or drafting state.

Run the query

  1. Open the query workbench.
  2. Select the table, or use its address in SQL. Include the catalog and domain when the interface asks for them.
  3. Enter a read-only query and declare why you are using the data.
  4. Run it, then inspect the rows and trace. The trace identifies the contract used for the read.

The public API exposes POST /v1/workbench/query. Its request and response schema are in the generated API reference. The address accepted by SQL can differ from the catalog display name while the namespace migration is in progress; use the exact address shown on the table detail page.

Handle a refusal

An unknown table and a forbidden purpose are different failures. Read the returned code and message. If the purpose is denied, choose one allowed by the contract or ask its owner to revise the policy. Do not retry with a blank purpose to bypass a refusal.