Resolver workbench

Everything on this page runs locally in your browser against the Synthetic fixture catalog — no network, no model calls, no credentials. Fixture execution is a demonstration of the rules, never verification of any real vendor.

snapshot digest: 2c072e9ff5d2e9da5e063e44eb31bdfa95343859f27753170ba00de0c6c43e2c · trustStatus: fixture

1 · Request

Model query (exact ref or alias)

Harness

2 · Your policy (human-authored, explicit)

Declared gateway preference (earliest wins; omitted = tie → refuse)I authored or reviewed this policy and accept it explicitly. The registry never picks a winner on my behalf — my policy decides.

Accept the policy to run — there is no built-in default.

3 · Result

Run the resolver to see a route or a refusal, with its full trace.

Acceptance scenarios — the same bytes as the Node consumer and the test suite

Deterministic: identical inputs always yield identical result and trace digests.