Name one boundary
Select memory, routing, interoperability, clarification, or audit—not a vague “AI integration.”
Integration readiness
Prove the client contract before anything can act.
Choose one workflow, exercise six fixed outcomes locally, and keep identity separate from permission.
No network call, no credentials, and no side effect. It proves that your client preserves every resolver outcome and adds a ConceptCode and registry version only after a structurally valid governed resolution.
Exercise every outcome
Resolved, unknown, ambiguous, malformed, request error, and service error all receive explicit records.
Keep action authority separate
The test records a policy version and a non-authorizing result while performing no action.
Step 1 · Select exactly one recipe
Which durable handoff are you preparing?
The recipe determines the fit statement, placement, and benefit metrics in the report. It does not change the six resolver fixtures or the resolved-only identity rule.
What will run
Six fixed local fixtures for every recipe.
Recipe selection changes the workflow explanation and benefit plan. It never changes the evidence cases or makes a non-resolved outcome eligible for identity.
resolved-validunknown-expressionambiguous-expressionmalformed-resolvedrequest-errorservice-error
Keep local proof and deployment evidence separate
A passing self-test proves client behavior—not the live corpus.
Current deployment facts remain available from the status and capabilities endpoints. The local report does not claim that a particular expression will resolve in production.
- Published concepts
- 0
- Reviewed exact expressions
- 0
- Production resolver
- reviewed_exact_registry_first
- Arbitrary-query generalization
- not_production_active