The generated.* family (1 verb). Every verb enters through the one front door: it is capability-checked, permission-checked, scope-checked and audited before it runs (see Security & permissions). Each entry below lists its capability, risk class (which fixes the minimum autonomy level), the minimum caller permission, its availability tier, whether it is idempotent, and any outbound egress.
Getgenerated.get
| Property | Value |
|---|---|
| Capability | doc.read |
| Risk class | Read - autonomy L0 |
| Min. permission | Member |
| Availability | On demand (MCP tier 2) |
| Idempotent | No |
| Egress | None - in-box (pure Postgres, no outbound call) |
| Render schema | Yes - drives an inline chat artefact and a GUI panel |
The gated single-read of an audited generation snapshot: returns the FULL
record incl the coverage report (the INV-9 gate verdict + filled/missing vars), the fidelity check
(the INV-5 self-re-parse verdict), the PINNED template version (R11 snapshot-not-live), the payload
snapshot the generation ran with, and the failure reason on a BLOCKED/FAILED row. RLS-scoped + an
explicit workspace_id = $ predicate; a cross-workspace / missing id reads back as not-found
(no generated document '<id>'), the same verdict for both (anti-enumeration). A BLOCKED/FAILED
snapshot is STILL readable (the failure audit is retained, INV-9). Computes nothing (INV-14).
Input { id } (fields ending in ? are optional)
Call POST /v/generated.get with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool generated.get.