opbox

The registry.* family (2 verbs). 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.

Createregistry.submission.create

PropertyValue
Capabilityother.write
Risk classWrite - autonomy L1
Min. permissionMember
AvailabilityOn demand (MCP tier 2)
IdempotentNo
EgressNone - in-box (pure Postgres, no outbound call)

matterId fail-closed resolve in workspace; submittedAt set when status=SUBMITTED.

Call POST /v/registry.submission.create with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool registry.submission.create.

Updateregistry.submission.update

PropertyValue
Capabilityother.write
Risk classWrite - autonomy L1
Min. permissionMember
AvailabilityOn demand (MCP tier 2)
IdempotentNo
EgressNone - in-box (pure Postgres, no outbound call)

Status machine derives submitted_at/approved_at/responded_at.

Call POST /v/registry.submission.update with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool registry.submission.update.