---
title: "What is still outstanding"
method: GET
path: "/v2/workspaces/{id}/agenda"
tags: ["Inquiries"]
---

# What is still outstanding

`GET /v2/workspaces/{id}/agenda`

## Request

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

The commander's board: every question still being asked, one row per equivalence class, with each row's prompt and subject resolved.

**Read `outstanding` as ROWS.** It counts equivalence classes, not questions (IR6). Counting questions would double-count every rephrasing anybody ever linked; `live_questions` sits beside it for the cases where the other number is wanted, and never in place of it.

**Cost.** One agenda read plus one lineage fold per question, because `AgendaRow` upstream projects `{representative, status, members, live}` and neither `subject` nor `prompt` — so the only place either appears is the `Open` record. `folds` reports the total. That is a missing upstream projection, not a design.

**And it is only the live half of the board.** `inquiry_agenda` returns classes with a live member and nothing else, so answered and abandoned classes are invisible to every argument-free read there is — `retired.reason` states the gap and the ask.

**Refining a question is not answering it, and similarity cannot retire a question.**

`narrow` marks the parent `narrowed`, which is a LIVE status: the parent STAYS on the agenda (IR2). `split` leaves the parent `superseded` with recorded lineage, never `answered` (IR3) — and never `split`, a status in the wire vocabulary that the fold never produces.

An `answer` must NAME an assertion (IR4), and a memory NEVER answers a question by arriving on its subject key. The match would be exact, which is exactly why it looks defensible; the rule it breaks is IR4. Pass `answers_inquiry` on a `remember` to state one.

An agenda ROW is an equivalence CLASS, not a question (IR6): two questions joined by `same_as` are ONE row with two members, and `outstanding` counts ROWS. `same_as` groups the VIEW and merges no identity, no lineage and no history.

`abandon` and `same_as` are authority-floored; a below-floor record is written and folds INERT, never rejected (D4). There is NO delete: reopening an abandonment is an append that cites ONE specific abandon record.

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

## Response `200`

The outstanding rows, resolved

- object
  - `rows` object[], required
    - `representative` string, required
    - `status` string, required
    - `prompt` string, nullable, required
    - `subject` string, nullable, required
    - `questions` object[], required
      - `inquiry` string, required
      - `prompt` string, nullable, required
      - `subject` string, nullable, required
      - `status` string, nullable, required
      - `live` boolean, required
    - `live_questions` number, required
    - `retired_questions` number, required
    - `grouped` boolean, required
  - `outstanding` number, required
  - `live_questions` number, required
  - `fold_size` number, required
  - `folds` number, required
  - `index` object, required
    - `complete` boolean, required
    - `reason` string
  - `retired` object, required
    - `visible` false, required
    - `reason` string, required
  - `degraded` boolean
  - `degraded_reason` string

## 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 inquiry 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)