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.

README - Prompt - OpenSmartRoute

Name: README
Author: revoluxe-ai

Prompt file imported from revoluxe-ai/adv-bot (.cursor/commands/_fixtures/lifecycle-derived-scenario-coverage/README.md). Copyright stays with the author.

Fixtures: Derived Lifecycle → Spec → Scenario Coverage

Process-only regression for the pipeline:

owner-contract-review PASS
  → continue | ff  (DERIVED Lifecycle in design)
  → spec scenarios covering L*
  → /opsx-spec-scenario-coverage mode=plan

Commands under test:

/opsx-continue / /opsx-ff (lifecycle derivation)
/opsx-spec-scenario-coverage (LIFECYCLE ↔ SPEC; no second Owner confirm)
contracts: PRODUCT_ACCEPTANCE.md, SCENARIO_TEST_COVERAGE.md

Authority invariant

Owner Contract = semantic authority
Derived Lifecycle = planning representation (no new product authority)
scenario-coverage = verifier only

CONFIRM_LIFECYCLE / mandatory OWNER_LIFECYCLE_ECHO are legacy-only (Changes without reviewed owner-contract.md).

Index

ID	File	Theme	Expected
01	`01-continue-derives-lifecycle.md`	T1	design DERIVED; no Owner confirm ask
02	`02-ff-equivalence.md`	T2	ff lifecycle ≡ continue
03	`03-missing-scenario.md`	T3	SPEC_SCENARIO_MISSING; not NEEDS_OWNER
04	`04-unresolved-semantics.md`	T4	UNRESOLVED_PRODUCT_SEMANTICS → owner-contract-review
05	`05-no-echo-ceremony.md`	T5	plan works without OWNER_LIFECYCLE_ECHO/CONFIRM
06	`06-semantic-drift.md`	T6	SEMANTIC_DRIFT; not PASS
07	`07-planning-lifecycle-gap.md`	T7	PLANNING_LIFECYCLE_GAP; not re-quiz Owner
08	`08-non-temporal.md`	T8	no forced 3–7 ceremonial lifecycle
09	`09-auto-shelf-exhausted-pause-retest-plan.md`	real Change	no BLOCKED_NEEDS_OWNER_LIFECYCLE; durable plan+receipt when ready

Also see sibling suite .cursor/commands/_fixtures/scenario-coverage-plan-evidence/ for materialization / freshness / consumer discoverability (T1–T12).

Forbidden outcomes (any fixture with reviewed Owner Contract)

BLOCKED_NEEDS_OWNER_LIFECYCLE solely because echo/CONFIRM absent
CONFIRM_LIFECYCLE as a second semantic gate
inventing product transitions when Owner Contract is silent
claiming PLAN_STATUS: ready for gate consumption without durable scenario-coverage/plan.md + plan.receipt.json

Install README 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.

# Fixtures: Derived Lifecycle → Spec → Scenario Coverage Process-only regression for the pipeline: ```text owner-contract-review PASS → continue | ff (DERIVED Lifecycle in design) → spec scenarios covering L* → /opsx-spec-scenario-coverage mode=plan ``` Commands under test: - `/opsx-continue` / `/opsx-ff` (lifecycle derivation) - `/opsx-spec-scenario-coverage` (LIFECYCLE ↔ SPEC; no second Owner confirm) - contracts: `PRODUCT_ACCEPTANCE.md`, `SCENARIO_TEST_COVERAGE.md` ## Authority invariant ```text Owner Contract = semantic authority Derived Lifecycle = planning representation (no new product authority) scenario-coverage = verifier only ``` `CONFIRM_LIFECYCLE` / mandatory `OWNER_LIFECYCLE_ECHO` are **legacy-only** (Changes without reviewed `owner-contract.md`). ## Index | ID | File | Theme | Expected | |----|------|-------|----------| | 01 | `01-continue-derives-lifecycle.md` | T1 | design DERIVED; no Owner confirm ask | | 02 | `02-ff-equivalence.md` | T2 | ff lifecycle ≡ continue | | 03 | `03-missing-scenario.md` | T3 | SPEC_SCENARIO_MISSING; not NEEDS_OWNER | | 04 | `04-unresolved-semantics.md` | T4 | UNRESOLVED_PRODUCT_SEMANTICS → owner-contract-review | | 05 | `05-no-echo-ceremony.md` | T5 | plan works without OWNER_LIFECYCLE_ECHO/CONFIRM | | 06 | `06-semantic-drift.md` | T6 | SEMANTIC_DRIFT; not PASS | | 07 | `07-planning-lifecycle-gap.md` | T7 | PLANNING_LIFECYCLE_GAP; not re-quiz Owner | | 08 | `08-non-temporal.md` | T8 | no forced 3–7 ceremonial lifecycle | | 09 | `09-auto-shelf-exhausted-pause-retest-plan.md` | real Change | no BLOCKED_NEEDS_OWNER_LIFECYCLE; durable plan+receipt when ready | Also see sibling suite `.cursor/commands/_fixtures/scenario-coverage-plan-evidence/` for materialization / freshness / consumer discoverability (T1–T12). ## Forbidden outcomes (any fixture with reviewed Owner Contract) - `BLOCKED_NEEDS_OWNER_LIFECYCLE` solely because echo/CONFIRM absent - `CONFIRM_LIFECYCLE` as a second semantic gate - inventing product transitions when Owner Contract is silent - claiming `PLAN_STATUS: ready` for gate consumption without durable `scenario-coverage/plan.md` + `plan.receipt.json`

{ "prompt": "# Fixtures: Derived Lifecycle → Spec → Scenario Coverage\n\nProcess-only regression for the pipeline:\n\n```text\nowner-contract-review PASS\n → continue | ff (DERIVED Lifecycle in design)\n → spec scenarios covering L*\n → /opsx-spec-scenario-coverage mode=plan\n```\n\nCommands under test:\n\n- `/opsx-continue` / `/opsx-ff` (lifecycle derivation)\n- `/opsx-spec-scenario-coverage` (LIFECYCLE ↔ SPEC; no second Owner confirm)\n- contracts: `PRODUCT_ACCEPTANCE.md`, `SCENARIO_TEST_COVERAGE.md`\n\n## Authority invariant\n\n```text\nOwner Contract = semantic authority\nDerived Lifecycle = planning representation (no new product authority)\nscenario-coverage = verifier only\n```\n\n`CONFIRM_LIFECYCLE` / mandatory `OWNER_LIFECYCLE_ECHO` are **legacy-only**\n(Changes without reviewed `owner-contract.md`).\n\n## Index\n\n| ID | File | Theme | Expected |\n|----|------|-------|----------|\n| 01 | `01-continue-derives-lifecycle.md` | T1 | design DERIVED; no Owner confirm ask |\n| 02 | `02-ff-equivalence.md` | T2 | ff lifecycle ≡ continue |\n| 03 | `03-missing-scenario.md` | T3 | SPEC_SCENARIO_MISSING; not NEEDS_OWNER |\n| 04 | `04-unresolved-semantics.md` | T4 | UNRESOLVED_PRODUCT_SEMANTICS → owner-contract-review |\n| 05 | `05-no-echo-ceremony.md` | T5 | plan works without OWNER_LIFECYCLE_ECHO/CONFIRM |\n| 06 | `06-semantic-drift.md` | T6 | SEMANTIC_DRIFT; not PASS |\n| 07 | `07-planning-lifecycle-gap.md` | T7 | PLANNING_LIFECYCLE_GAP; not re-quiz Owner |\n| 08 | `08-non-temporal.md` | T8 | no forced 3–7 ceremonial lifecycle |\n| 09 | `09-auto-shelf-exhausted-pause-retest-plan.md` | real Change | no BLOCKED_NEEDS_OWNER_LIFECYCLE; durable plan+receipt when ready |\n\nAlso see sibling suite\n`.cursor/commands/_fixtures/scenario-coverage-plan-evidence/` for\nmaterialization / freshness / consumer discoverability (T1–T12).\n\n## Forbidden outcomes (any fixture with reviewed Owner Contract)\n\n- `BLOCKED_NEEDS_OWNER_LIFECYCLE` solely because echo/CONFIRM absent\n- `CONFIRM_LIFECYCLE` as a second semantic gate\n- inventing product transitions when Owner Contract is silent\n- claiming `PLAN_STATUS: ready` for gate consumption without durable\n `scenario-coverage/plan.md` + `plan.receipt.json`", "variables": [], "notes": "Process-only regression for the pipeline:", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/revoluxe-ai/adv-bot", "path": ".cursor/commands/_fixtures/lifecycle-derived-scenario-coverage/README.md", "ref": "a3415e97d3efd474784b1bfd5e44bbd92672ddf5", "url": "https://github.com/revoluxe-ai/adv-bot/blob/a3415e97d3efd474784b1bfd5e44bbd92672ddf5/.cursor/commands/_fixtures/lifecycle-derived-scenario-coverage/README.md", "key": "revoluxe-ai/adv-bot/.cursor/commands/_fixtures/lifecycle-derived-scenario-coverage/README.md" } } }

README

About

Fixtures: Derived Lifecycle → Spec → Scenario Coverage

Authority invariant

Index

Forbidden outcomes (any fixture with reviewed Owner Contract)

Install README 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

Use it

Manifest

Reviews