Declare two questions to be one agenda row

IR6: same_as GROUPS THE VIEW and never merges identity. The two questions become ONE agenda row with two members, and both ids keep their own status, their own lineage and their own history forever. Nothing is rewritten and nothing is deleted — and there is no un-same-as verb.

Authority-floored on the same terms as abandon (top authority, or a writer who opened both — self-dedup of one's own rephrasings is always safe), and reported the same way: this route re-reads lineage for effective.

Only an explicit record groups. Embeddings may NOMINATE candidates upstream; nothing in the fold consumes similarity (S3, D2).

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