CLI · MATCHING

Boundary policies

Smart boundary

smart consumes particle and ending transitions after the core and verifies the POS sequence of source components when required. A compact resource is mandatory when the query program declares structural capability.

It preserves completed tokens and permitted internal components while rejecting substrings that accidentally occur inside another POS. It does not resolve semantic ambiguity.

Token boundary

token requires Unicode word boundaries at the core start and the end of all consumed material. It excludes component-internal matches and suits independent-token checks.

The matcher checks the boundary after consuming permitted particles or endings. It does not simply stop at the end of the lemma string.

Any boundary

any imposes no left or right token boundary and returns spans verified by generated programs. Use it for broad collection and recall-oriented automation.

Relaxing boundaries does not change the morphology rules. Combine --literal --boundary any for literal substring search.