runs in your browseroperating regulations · dispute SLAApache-2.0 · zero-dep

Disputes resolve by the clock, not the loudest voice.

A network needs operating regulations, not just code: a standard reason-code taxonomy, a response SLA per code, and a deterministic outcome. Miss your deadline and the dispute auto-resolves against you; respond in time with evidence and it goes to arbitration. Liability lands on the issuer (who deployed the agent) or the provider (who did the work) — by rule, not negotiation.

openeddeadline
Resolution (live)
liable party
auto-resolved
requires evidence
rules version

Honest scope. A deterministic rulebook engine — it computes deadlines, the response status, and the liability assignment from the reason code + the SLA window; it does not adjudicate a contested dispute (that's arbitration — a human/panel, which the kernel deliberately leaves to liable_party: null). It extends the fault kernel (which attributes where a failure originated) with the timed network process around it. Reason codes + windows are overridable per network via policy. Source: flowdesk-rules-kernel.js.