Warrants

What one hop of discounting this premise would reach

?premise=<space>:<id>. ONE HOP, bounded by D6: these are the refs whose acceptance changes when every edge FROM this premise is discounted. It is NOT the transitive closure — a claim that then loses its own support is not listed here, and computing that chain is consumer policy the kernel deliberately does not make.

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:read 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:read 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:read — mint a key with it explicitly (POST /v2/workspaces/{id}/keys).

get/v2/workspaces/{id}/warrant-impact

Request

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

Path parameters

idstring required

Query parameters

premisestring required

"<space>:<id>"

Example:memory:mem_123

Response

The refs whose acceptance would change, one hop out

fold_sizenumber required
hops1 required
transitivefalse required
notestring required

Changes

No recorded changes to this operation across all 1 revision of this API.