Open a question

prompt is for people; subject is the JOIN — the exact key a memory must carry on its il-subject: tag for recall to relate the two. Neither is ever folded on: the fold reads no character of either, which is what makes similarity cannot retire a question structural rather than a policy.

Keep the returned inquiry id. Every other verb names the question by it (IR1), and a paraphrase is a DIFFERENT question with a different id.

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: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).