Regimes

Declare two regimes in conflict

Two active regimes that cannot both govern. Until an operator rules, BOTH sides' scoped memories annotate inapplicable_until_adjudicated — a dead end no authority, recency or scope count moves. The dead end is the safety property: a system that guessed which contested phase governs is a system that shipped during a freeze somebody was still arguing about.

There is no way to retract a conflict edge; a dispute leaves the live set by adjudication, or by one of its regimes ending or being voided.

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}/regimes/{regime}/conflict

Request

  • Base URL: https://api.infolang.ai
  • URL: https://api.infolang.ai/v2/workspaces/{id}/regimes/{regime}/conflict
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer
    • HTTP bearer

Path parameters

idstring required
regimestring required

Request body

withstring uuid required
conflictstring uuid

Response

The edge that was declared

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.