INTERNALS · SOURCE

Structural verification

Structural constraints

A constraint declares the component span that corresponds to the query core, the required POS, the whole-token path, and neighboring components. It does not use a registry of exceptional source strings.

Exact and common-prefix paths require both component order and spans declared by the source analysis.

Graph preparation

The decoder reads analyses and component edges for a surface and materializes only nodes required by final context preparation. Shared facts and immutable slices reduce per-query copying.

Limits on nodes, context depth, and payload size bound memory even for malformed resources.

Verification failure

The resolver rejects candidates with no required path and distinguishes indeterminate states, such as graph-limit failures, as Unavailable. Ordinary matcher failures during window extraction or context preparation reject the candidate and are recorded in caller-owned SearchDiagnostics. The native CLI reports affected files on stderr and exits with status 2. These are also distinct from resource-loading errors that stop the search. See results and diagnostics for the ordinary search contract. No lower-precision fallback is applied.

If any source analysis satisfies the constraint, the candidate remains and its analysis index enters provenance.