---
title: "State a reason"
method: POST
path: "/v2/workspaces/{id}/warrants"
tags: ["Warrants"]
---

# State a reason

`POST /v2/workspaces/{id}/warrants`

## Request

- Base URL: `https://api.infolang.ai`
- URL: `https://api.infolang.ai/v2/workspaces/{id}/warrants`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer
  - HTTP bearer

`from` bears on `to` with this polarity, because of this reason.

`support` is a reason the target stands. `rebut` attacks the CLAIM. `undercut` attacks an EDGE — its `to` must be a `warrant` ref, and one aimed anywhere else is written and folds INERT (A5: ingest never validates), which the response says rather than refusing. `undermine` attacks a PREMISE and discounts the edges leading from it, one hop.

Keep the returned `edge` id: it is the only handle that can ever withdraw this reason.

An edge is a REASON, with an exact id. Two edges whose prose resembles are two edges and no fold merges them; the fold never reads `reason` at all, which is why it is required — it is written for the human reading the audit, and nothing else will ever supply it.

There is NO delete. Withdrawing a reason is `bottom`, an APPEND that leaves the edge, its defeat, and the history of both in the log forever.

An acceptance status is a joint function of TWO logs — the warrant log and the assertion log the verdict oracle reads — so every read carries both cursors. Two answers are comparable only at equal pairs.

`contested` is in the status vocabulary and CANNOT OCCUR in the current topology: an edge attacks exactly one target, so undercut cycles are closed under their own targets and a support/rebut edge can never be undecided. Do not build a UI state for it.

Requires the `coord:write` scope. Accepts all three lanes: a session JWT (bounded by the caller's role on this workspace) or an `il_*` machine credential whose own scope set, workspace set and validity window cover it — both ceilings apply and neither can raise the other, so a credential carrying `coord:write` is still refused where the role does not permit it.

A credential with no scope record resolves to `LEGACY_DEFAULT`, which does NOT include `coord:write` — mint a key with it explicitly (`POST /v2/workspaces/{id}/keys`).

## Path parameters

- `id` string, required

## Request body

- object
  - `from` object, required
    - `space` 'assertion' | 'memory' | 'source' | 'inquiry' | 'warrant', required
    - `id` string, required
  - `to` object, required
    - `space` 'assertion' | 'memory' | 'source' | 'inquiry' | 'warrant', required
    - `id` string, required
  - `polarity` 'support' | 'rebut' | 'undercut' | 'undermine', required
  - `reason` string, required
  - `edge` string, uuid

## Response `201`

The edge, and whether it will fold inert

- object
  - `record` string, required
  - `authority` 'inference' | 'observation' | 'operator', required
  - `minted` string, nullable
  - `appended` boolean
  - `advisory` unknown
  - `folded_inert` boolean
  - `edge` string, required

## Other responses

- `401`: Missing/invalid credential, or `credential_expired` — the credential is outside its `[not_before, expires_at)` window and must be replaced
- `403`: `insufficient_scope` — the credential's own scope set, or the caller's role on this workspace, does not cover the scope this route requires (the missing scope is named in the message). Or `forbidden` — the credential is not scoped to this workspace, or holds no grant on it
- `501`: The warrant verbs are not compiled into this deployment (`kernel-verbs` is off upstream)

---

[API](https://skmtc.dev/infolang/apis/infolang-api.md) · [All operations](https://skmtc.dev/infolang/apis/infolang-api/llms.txt) · [OpenAPI document](https://skmtc.dev/infolang/apis/infolang-api/revisions/d04bf6de72c8?raw)