How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

22-reconciliation-no-graph-mutation - Prompt - OpenSmartRoute

Promptv1.0.0

22-reconciliation-no-graph-mutation

Name: 22-reconciliation-no-graph-mutation
Author: revoluxe-ai

A second full post-write inventory / routing refresh / scenario re-audit on the same fingerprint is a liveness violation.

by revoluxe-ai(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from revoluxe-ai/adv-bot (.cursor/commands/_fixtures/supervisor-sequential-bug-mission/22-reconciliation-no-graph-mutation.md). Copyright stays with the author.

22 — Reconciliation without graph mutation cannot loop (SUP-LIVE-004)

WRITER_RETURNED
WRITE_SCOPE_RECONCILED already computed for this snapshot
DURABLE_SUPERVISOR_STATE_FINGERPRINT unchanged
no TASK_ADDED / DEPENDENCY_* / CORRECTION / REAUDIT graph mutation

Expected

FURTHER_RECONCILE_ROUTE_LOOP=FORBIDDEN
do not re-enter: reconcile → route → reconcile
next must be DISPATCH | EXPLICIT_BLOCK | SUPERVISOR_NO_PROGRESS
  (or no-op that immediately produces one of those)

Negative

A second full post-write inventory / routing refresh / scenario re-audit on the same fingerprint is a liveness violation.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# 22 — Reconciliation without graph mutation cannot loop (SUP-LIVE-004)

```text
WRITER_RETURNED
WRITE_SCOPE_RECONCILED already computed for this snapshot
DURABLE_SUPERVISOR_STATE_FINGERPRINT unchanged
no TASK_ADDED / DEPENDENCY_* / CORRECTION / REAUDIT graph mutation
```

## Expected

```text
FURTHER_RECONCILE_ROUTE_LOOP=FORBIDDEN
do not re-enter: reconcile → route → reconcile
next must be DISPATCH | EXPLICIT_BLOCK | SUPERVISOR_NO_PROGRESS
  (or no-op that immediately produces one of those)
```

## Negative

A second full post-write inventory / routing refresh / scenario re-audit
on the same fingerprint is a liveness violation.

Installed into a catalogue, chosen by a router

Install 22-reconciliation-no-graph-mutation and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

revoluxe-ai-adv-bot-22-reconciliation-no-graph-mutation-d6c9f1.prompt.jsonjson

{
  "prompt": "# 22 — Reconciliation without graph mutation cannot loop (SUP-LIVE-004)\n\n```text\nWRITER_RETURNED\nWRITE_SCOPE_RECONCILED already computed for this snapshot\nDURABLE_SUPERVISOR_STATE_FINGERPRINT unchanged\nno TASK_ADDED / DEPENDENCY_* / CORRECTION / REAUDIT graph mutation\n```\n\n## Expected\n\n```text\nFURTHER_RECONCILE_ROUTE_LOOP=FORBIDDEN\ndo not re-enter: reconcile → route → reconcile\nnext must be DISPATCH | EXPLICIT_BLOCK | SUPERVISOR_NO_PROGRESS\n  (or no-op that immediately produces one of those)\n```\n\n## Negative\n\nA second full post-write inventory / routing refresh / scenario re-audit\non the same fingerprint is a liveness violation.",
  "variables": [],
  "notes": "A second full post-write inventory / routing refresh / scenario re-audit on the same fingerprint is a liveness violation.",
  "metadata": {
    "source": {
      "provider": "github-cursor-commands",
      "repository": "https://github.com/revoluxe-ai/adv-bot",
      "path": ".cursor/commands/_fixtures/supervisor-sequential-bug-mission/22-reconciliation-no-graph-mutation.md",
      "ref": "a3415e97d3efd474784b1bfd5e44bbd92672ddf5",
      "url": "https://github.com/revoluxe-ai/adv-bot/blob/a3415e97d3efd474784b1bfd5e44bbd92672ddf5/.cursor/commands/_fixtures/supervisor-sequential-bug-mission/22-reconciliation-no-graph-mutation.md",
      "key": "revoluxe-ai/adv-bot/.cursor/commands/_fixtures/supervisor-sequential-bug-mission/22-reconciliation-no-graph-mutation.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/revoluxe-ai-adv-bot-22-reconciliation-no-graph-mutation-d6c9f1/manifest?version=1.0.0

About

22 — Reconciliation without graph mutation cannot loop (SUP-LIVE-004)

Expected

Negative

Use it

Install 22-reconciliation-no-graph-mutation and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews