Form templates

The form-template.* family (6 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.

form-template.create

author a new DRAFT form template. { key, title, description?, schema }.

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

form-template.edit

re-draft a DRAFT template’s schema/title/description. { id, title?, description?, schema? }. Only DRAFT templates are editable (a published version is immutable, R11 - mirrors board.edit).

Call POST /v/form-template.edit with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool form-template.edit.

form-template.get

one template. { id }.

Call POST /v/form-template.get with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool form-template.get.

form-template.list

list templates (optionally filter by status). { status? }.

Call POST /v/form-template.list with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool form-template.list.

form-template.publish

validate the DRAFT schema, forward-mint an immutable FORM Version, DRAFT->ACTIVE, point current_version at the minted version. { id, changelog? }. R11 snapshot-not-live.

Call POST /v/form-template.publish with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool form-template.publish.

form-template.validate

run validate_form_schema without persisting. { id } or { schema }.

Call POST /v/form-template.validate with a JSON body; returns JSON (or { error, code }). Also exposed as the MCP tool form-template.validate.