Skip to main content
Court-Attorney (bot_id: Court-Attorney, shown in the UI as Prover Court Attorney) is a built-in Genesis agent registered when the estate ruling overlay is enabled. It helps a decider — a human reviewer, an agent-judge, or an external workflow tool — understand a court docket before ruling. It has no power to settle, adjudicate, or decide anything; its exchanges are recorded as ruling provenance on the docket.In the MCP agent list, its short description is: Court clerk for a ruling docket. Answers a decider’s exploratory questions about the estate before a ruling, and cannot rule, settle or license anything itself.

Purpose

Investigate one Adjudication Court docket on behalf of a decider — show diverging rows, trace downstream marts, and explain what each fork reading implies.

Scope

Lineage, Context Graph document index, and read-only SQL over the estate. No source_contract_tools — cannot emit rulings or license findings.

Design Goals

Governance independence: investigative access only; the decider (human or agent-judge) holds licensing authority through separate court surfaces.
Genesis registers Court-Attorney at startup when the estate ruling overlay is active (the same gate that enables the ruling library and Adjudication Court queue). The Estate workspace nav is shown by default (show_estate: true on GET /api/config/frontend) unless the deployment set features.show_estate to false.
Court-Attorney loads a fixed, direct-tool set — no dynamic manage_context discovery:Court-Attorney deliberately does not include source_contract_tools. It cannot call decide_court_docket, settle rulings, or change authority in any way.
1

Open the docket queue

Humans browse GET /api/estate/court/dockets?estate_id=… in the Estate Human Review GUI, or an agent-judge calls list_court_dockets / get_court_docket from source_contract_tools.
2

Ask exploratory questions

The decider records questions with ask_court_attorney (agent tool) or POST /api/estate/court/dockets/{docket_id}/chat (headless HTTP API). Court-Attorney investigates with lineage, document index, and SQL, then the decider records the attorney’s reply on the same court record (role: attorney).
3

Rule

A human with ratify_source_contract decides via the GUI or POST .../decide / .../adopt (identity from the authenticated session, never the body). An agent-judge may call decide_court_docket only for sub-threshold dockets — emitting a provisional ruling queued for human ratification. Dockets at or above the materiality ceiling are refused for agent decision.
The court record (attorney chat) travels with the docket as ruling provenance — read it through GET /api/estate/court/dockets/{docket_id} or get_court_docket.
These tools are not on Court-Attorney. They belong to the designated Prover Adjudicator agent’s source_contract_tools group. In the UI, this built-in agent is shown as Prover Adjudicator and retains the stable bot_id Adjudicator:Parameter names and return shapes match the Estate court HTTP API where applicable.