update_workspace

The workspace's complete new currency-reading policy, or omitted to leave it unchanged. Whole-block like knowledge_graph: an empty object resets to the USD default, and {"default": null} is how the policy is cleared to assume nothing. Applies from the next ingestion onwards: amounts already extracted as ambiguous stay that way until their file is re-ingested, since the catalog records what a past extraction could read.

The workspace's complete new knowledge-graph policy, or omitted to leave it unchanged. Supplying it replaces every field it holds, so send the block read back from the workspace with your edits applied rather than only the key you are changing.

The workspace's complete new ledger-understanding policy, or omitted to leave it unchanged. Whole-block like knowledge_graph. Turning the trigger off stops future ingestions chaining a run; it never refuses an explicit one, and it does not withdraw a report already measured.

The workspace's complete new retention policy, or omitted to leave it unchanged. Whole-block like knowledge_graph: a field you leave out reverts to its default, so send the block read back from the workspace with your edits applied. A changed derived_ttl_days is applied to files already ingested (their expiry is recomputed from ingestion time, so a shorter TTL can expire them at the next sweep), and null clears their expiry. source_ttl_days is evaluated at each sweep, so it applies to existing files immediately. job_ttl_days applies to jobs created after the change; payloads of existing jobs keep the expiry they were given.

A workspace's access-control setting, chosen once at creation.

labels = [] is the default and means no filtering at all — no classification pass at ingestion, no filter clause at retrieval, and Coverage reports nothing. A workspace that does not need document-level access control should not pay for a classification that always returns the same answer.

Coverage reporting is always strict: whenever the gate withholds candidates, the response says so in counts and label names. A silently narrowed answer is the failure mode this platform exists to prevent, so there is no opt-out.

How this workspace's documents should be read where they leave a currency open.

Extraction never converts an amount and never invents a currency: one whose currency the source does not state is recorded as ambiguous with no value, so it matches no amount filter. New workspaces default to DEFAULT_WORKSPACE_CURRENCY (USD), so a corpus that writes every total as a bare $900.00 and names a currency nowhere is filterable out of the box. Set default to another ISO code to change the reading, or to null to assume nothing — an amount whose currency the source never states then stays ambiguous rather than being read as USD.

A workspace's knowledge-graph build policy.

The defaults keep the whole corpus in scope and build the graph after every ingestion, so fact search and deep search have it to navigate by. Set auto_build=false for a workspace that builds only on request. exclude_path_prefixes and exclude_categories are the workspace-wide skip rules a file's graph_inclusion can override — a file matching either is left out of the graph corpus unless it is explicitly include\ d.

A workspace's retention setting, chosen at creation and editable afterwards.

derived_ttl_days anchors on ingested_at and source_ttl_days on created_at — one anchor each, not configurable.

When this workspace understands its general ledger — table and column roles, the journal key and its balance proof, and the integrity battery. A workspace configured before this block existed reads back the default.