Disclosures

Record that you went back and told them it was wrong

COEXISTS with the disclosure it names and ERASES NOTHING. The original telling stays in told forever; the thread gains a mark saying a notice was given, and the current line is unchanged (a notice is not an amend).

Named retracted-notice and not retract on purpose: a telling cannot be taken back. The notice takes CONTENT rather than a flag because it is speech too, and it has a body somewhere.

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

post/v2/workspaces/{id}/disclosures/{disclosure}/retracted-notice

Request

  • Base URL: https://api.infolang.ai
  • URL: https://api.infolang.ai/v2/workspaces/{id}/disclosures/{disclosure}/retracted-notice
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer
    • HTTP bearer

Path parameters

idstring required
disclosurestring required

Request body

reasonstring required
memory_idstring

Response

The notice record

recordstring required
authority'inference' | 'observation' | 'operator' required
mintedstring nullable
appendedboolean
advisoryunknown
folded_inertboolean

Changes

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