Rule on a conflict (operator-floored)
Names the survivor; the loser's scoped memories become inapplicable_adjudicated while both regimes stay active. Operator-floored, so through this surface it folds inert today for exactly the reason void does.
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).
Request
- Base URL: https://api.infolang.ai
- URL: https://api.infolang.ai/v2/workspaces/{id}/regime-conflicts/{conflict}/adjudicate
- Auth: one of:
- HTTP bearer
- HTTP bearer
- HTTP bearer
Path parameters
Request body
Response
The ruling, with inert when the fold will ignore it
Changes
No recorded changes to this operation across all 1 revision of this API.