---
title: "What one hop of discounting this premise would reach"
method: GET
path: "/v2/workspaces/{id}/warrant-impact"
tags: ["Warrants"]
---

# What one hop of discounting this premise would reach

`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

`?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`).

## Path parameters

- `id` string, required

## Query parameters

- `premise` string, required: "<space>:<id>"

## Response `200`

The refs whose acceptance would change, one hop out

- object
  - `premise` object
    - `space` 'assertion' | 'memory' | 'source' | 'inquiry' | 'warrant', required
    - `id` string, required
  - `affected` object[], required
    - `space` 'assertion' | 'memory' | 'source' | 'inquiry' | 'warrant', required
    - `id` string, required
  - `cursors` object, required
    - `warrant` string, required
    - `coord` string, required
  - `fold_size` number, required
  - `hops` 1, required
  - `transitive` false, required
  - `note` 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)