Browse this guideGovern and query the Catalog
Feature libraryUpdated 2026-11-12

Govern and query the Catalog

Every artifact will receive a determined access level before it becomes queryable. Provenance sets the broadest level the system may assign, the typology may narrow it, and a business administrator may make a logged, reversible override. The Review Queue includes the administrator controls for setting an unresolved access level and for manually adding a record.

Administrators can inspect a filed governed record and manage its access from the Artifacts guide.

The automatic rules never widen access beyond the provenance ceiling. A channel involving a customer, for example, cannot automatically produce an internal-only default. An unknown party leaves the ceiling unresolved, so the artifact waits for a business administrator instead of becoming queryable.

An administrator can set a different level only through a recorded override. Raising an artifact to customer-visible access above its derived ceiling, including where no ceiling exists, requires an explicit confirmation and receives its own Daybook event. Clearing an override restores the derived level when one exists; it never guesses a replacement ceiling.

Whole records, filtered audiences

Governance controls which artifacts a caller receives. An authorized artifact is returned whole, exactly as extracted; an unauthorized artifact is absent from the result. Provenience does not redact or trim part of an artifact to fit an audience.

Current Site foundation

The Site database now enforces the design's Catalog read rules below application code. Its curated read surface admits only active principals with access to the relevant project, a sufficient clearance, and a determined artifact access level. An open Review Queue item withholds its artifact, and only artifacts in a source's confirmed current extraction generation are readable.

For SMS/MMS, Govern now assigns a 400 customer-visible ceiling and level when a recorded customer is present, and a 300 internal-only ceiling and level otherwise. An unregistered party leaves the artifact without either value and opens an access-undetermined Review Queue item for that phone number. A text with no recorded parties uses the internal-only fallback. Once its review blockers are resolved, an artifact is readable through api.artifact by an administrator with the required project access.

Confirmed reconciliations are readable only when every constituent artifact, including an outcome ending, is live, governed, and readable at the caller's clearance. A proposal, incomplete chain, or chain containing withheld material is not presented as a conclusion.

Raw sources remain outside ordinary Catalog reads. An active business administrator can inspect an original or attachment from the private Deposit; the Review Queue surface can use that read. It does not make the source available through api.artifact, does not release a held artifact, and grants no Deposit write, update, or delete access. A time-bounded break-glass grant can release an exact raw source or artifact through a named operation; it records the release in the Daybook and still requires project access and an unblocked target.

Staff access rules

The staff role is read-only and limited to the projects where the person has an active roster membership. It can read those projects' records at internal-only and customer-visible, subject to the same review and current-generation rules above. internal-restricted and excluded records, company-level records, records awaiting project assignment, and other projects are outside its access.

Staff roster reads show the names and party classes of active people on those projects. A readable artifact can also show its registered sender's name, even when the sender is not on the project's roster. These people reads never expose registered phone numbers or email addresses, the company roster, or another project's roster. An artifact is still returned whole; these restrictions do not remove contact details someone wrote in its content.

Staff cannot write, submit change proposals, resolve review questions, or read the Review Queue or original sources in the Deposit. Removing a project membership ends access to that project immediately; revoking the principal ends its access without waiting for a token to expire.

These rules are enforced in the database. Staff logins are not available; administrators remain the people who can sign in and connect an assistant.

MCP access

An administrator can connect any AI assistant that can add a remote MCP server and follows the MCP authorization standard. See Connecting an AI assistant for the administrator's steps, and Turn MCP on for how an operator turns it on for a Site. The server can list projects and typology, read a project and its roster, page through or read one governed artifact, and list or read an open Review Queue card. An administrator can also create or rename a project, answer a Which project? or Which category? card, retry a failed extraction, or exclude a card or selected texts. The tool descriptions instruct the assistant to confirm with the person first; that is an instruction, not a check the server enforces. These actions never delete the preserved source.

An MCP agent may propose a roster change or the registration of an unknown number, but a proposal changes nothing until a Site administrator accepts or declines it. The agent can check the status of a proposal made through its own connection. Access levels and access cards, new categories, proposal decisions, people renames, and number deactivation remain Site work.

Successful record results link into the signed-in Site. They contain extracted facts, not the original message text; open the linked source in the Site to read that. Direct actions report the change requested and a Site link rather than reading a record back.

Before rendering a record result, the server checks the returned rows again as the caller. A row that is no longer available is left out; a failed second check fails the tool rather than returning the first read. Every result ends with a Review Queue attention line; for an administrator it also shows pending proposals when there are any. Artifact lists are newest first, hold up to 500 records per page (200 by default), cut near 60,000 characters, and supply a continuation cursor when another page may remain. A full final page can be followed by an empty page.

Provenience does not retain a blanket log of prompts or returned results; it records privileged releases and content-free operational counters instead.

OAuth-backed MCP access is an operator step for each Site: the Railway service, its variables, and the Supabase OAuth and token-hook configuration. Its Site database boundary is in place: an OAuth-client token is refused by default, including for Deposit reads, and can reach only the explicitly approved MCP operations. Those writes retain the OAuth client's identity in the Daybook. The database foundation also binds reads to the caller's Site and applies the Catalog rules above.