SchemaRouter 0.12.0

SchemaRouter 0.12.0

SchemaRouter 0.12.0 is the stable-core product closure release for the current pre-1.0 architecture.

Version 0.11.0 established first-class bounded typed capability retrieval. Version 0.12.0 closes
that product cycle by freezing the architecture/API boundary, strengthening installed-package and
adapter policy regression coverage, and making the released artifact itself the canonical stable
baseline while research continues independently.

Stable-core boundary

The product architecture is now explicitly frozen around this contract:

Python / OpenAPI / MCP / OPTIMADE / adapter plugins
                         |
                 typed registry
                         |
          bounded capability retrieval
                         |
            agent / application
                         |
              planning/calls
                         |
       validation + local execution policy
                         |
                bound execution

Research may improve ranking/index implementations, shortlist defaults, adaptive depth and
corrective re-retrieval behind this boundary. A benchmark improvement by itself is not sufficient
reason to redesign the public facade.

Public retrieval facade

The current research cycles are expected to preserve:

• SchemaRouter.retrieve(..., k=5)
• SchemaRouter.aretrieve(..., k=5)
• SchemaRouter.retrieve_executable(..., k=5)
• SchemaRouter.aretrieve_executable(..., k=5)
• the equivalent ConfiguredSchemaRouter surfaces.

CapabilityCandidate continues to preserve the registered executable contract, including full
effective input/output JSON Schema, declared parameters and output fields, semantic IDs, optional
units/dimensions/qualifiers, policy metadata and fingerprints.

Retrieval remains side-effect free and does not grant execution authority.

Stronger closure validation

0.12.0 extends the product validation surface so release artifacts themselves exercise the frozen
contract.

The installed wheel/sdist consumer acceptance now verifies:

• sync and async bounded retrieval;
• executable-ready retrieval;
• retrieval produces no tool side effect;
• full input/output schemas are retained;
• registered tool/endpoint fingerprints are retained;
• actual invocation remains a separate operation.

Framework integration regression tests also verify that LangChain and LlamaIndex wrappers cannot
bypass SchemaRouter's local mutation/execution policy.

Research remains separate

Active research continues after the product closure release:

• stronger-agent B2 replication;
• large independently held-out agent-utility generalization;
• final-answer fact/value/unit/provenance quality;
• adaptive shortlist depth;
• execution-state-aware corrective re-retrieval;
• representation/index studies.

Those results may improve compatible internals and future defaults. They do not reopen the product
architecture unless they identify a reproducible correctness, security, policy, execution-authority,
API-integrity or packaging defect.

Compatibility

0.12.0 intentionally introduces no breaking public API change relative to 0.11.0.

Existing planning, invocation, validation, policy, async, batch, streaming, tracing, persistence,
inspection and optional integration surfaces remain available.

SchemaRouter remains Beta / pre-1.0. The stable-core freeze means the architecture is no longer
an active research variable; it is not yet the long-term semantic-versioning commitment implied by
a future 1.0 release.

Release integrity

The automated release pipeline requires the exact release-prep commit to pass protected CI and then:

• creates an annotated v0.12.0 tag at the exact green main SHA;
• builds wheel and sdist from that resolved release SHA;
• clean-installs and smoke-tests both artifacts;
• generates provenance attestations and an SPDX JSON SBOM;
• publishes to PyPI through OIDC;
• publishes GitHub Release assets;
• downloads the public PyPI wheel and sdist and verifies their digests against the trusted build;
• re-installs the exact public release as wheel, sdist, lightweight extras and combined integration
  extras outside the checkout.

The product track is considered fully closed only after those post-publish checks are green.