ContractSpec docs

OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

AI index

Approve a review record

Terminal-approve a review record; emits one audit event and dispatches the SEAMS §3.7 subject-kind callee (when applicable).

field.key.label
Approve a review record
field.version.label
field.type.label
field.title.label
Approve a review record
field.description.label

Terminal-approve a review record; emits one audit event and dispatches the SEAMS §3.7 subject-kind callee (when applicable).

field.tags.label
review,approve,mutation
field.owners.label
field.stability.label
public

Approves a review record. Terminal at the record level — re-opening requires a fresh review (no `review.reopen` in v1.0).

Per SEAMS §3.7 (S-07): when `subject.kind` resolves a downstream callee (`governance.policy.activate` ∨ `workflow.run.resume` ∨ `agent.set-autonomy`), the handler dispatches it via the `lib.companyos-runtime` outbox. The dispatched op runs under the original reviewer's auth context (§1.2); the handler pre-checks the reviewer's capability at decide-time per Q-03 and refuses with `FORBIDDEN` when the downstream capability is missing — prevents the "approved but inert" state.

Capability: `review.act` (+ implicit downstream capability where dispatch applies). Per SEAMS §1.5, missing capability returns `FORBIDDEN` — auditor persona sees the button disabled with a read-only tooltip.

Idempotency: `idempotencyKey` is required. Replays return the original result; differing payload on replay → `IDEMPOTENCY_FAIL`.