What this layer can do, what it refuses, and which values the corpus holds

Two layers. The semantic contract — operations, identity, amounts, dates, contacts, matching — is code-owned and versioned with the schema. The filter value lists are read from the LIVE licensed corpus on every request and stamped with the basis they were read against, so they are never presented as timeless constants. This route returns the COMPLETE lists; the agent runtime is injected a compact, source-aware subset of the same contract and spends no tool call on it. An optional facets query param (comma-separated) restricts both the computation and the response to the named corpus dimensions.