Blast radius — who was told this memory
This memory was compromised; here is exactly who was told, when, and through what channel, with each thread's current state.
index.complete is ALWAYS false, permanently, and that is not a bug: the disclosure verbs are keyed by thread and by audience, never by content, so this answer is reconstructed from the gateway's own index of the disclosures IT recorded. A disclosure written directly through the /coord/v1 passthrough is a real telling this answer cannot see. Read index.reason before acting on the result.
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).
Request
- Base URL: https://api.infolang.ai
- URL: https://api.infolang.ai/v2/workspaces/{id}/memories/{memoryId}/disclosures
- Auth: one of:
- HTTP bearer
- HTTP bearer
- HTTP bearer
Path parameters
Response
Every telling of this memory the gateway indexed
Changes
No recorded changes to this operation across all 1 revision of this API.