Your chunk boundary can turn a hearing notice into a verdict. You're indexing regulatory histories, and the answer draft says “found responsible” where the retrieved passage only describes an allegation.
The catch arrives before tokenization: the current GCC profile supplies a free-text action description and a decision link. That link doesn't put the decision's contents in your index.
Lab note 107: we want to answer a debugging question. Is the retrieval unit preserving a published action, or quietly manufacturing an outcome label?
Is the passage a hearing or a finding?
Consider the temptation to turn every regulatory-history entry into a classification target. There are fields named finding and outcome in the older field inventory. Convenient names. Very inconvenient assumptions.
Those older structured fields are no longer published and are omitted.…