Repository navigation
Keep residual expiration policies unresolved instead of defaulting - #34
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Follow-up to the residuals reported in issue #32, based on merged main ffece8e.
The strict threshold extractor is unchanged. Unsupported policies remain unresolved, never converted or defaulted to 90 days.
Detection-only changes:
Evidence
CI must verify the complete suite and Docker-backed gate on this commit. No model API calls, blind rescores, new domains, retries, README edits or architecture changes.
Limits
This is bounded deterministic detection, not universal natural-language interpretation. Other parenthetical constructions and number vocabularies are not proven covered. Removing the gap cap has quadratic behavior on synthetic repeated expiration predicates without a duration (peer measurement: about 1.9s at 11,000 characters); no real-corpus performance issue observed. The external developer's full 48-template matrix was not independently rerun here.
Refs #32; do not automatically close the issue as universally solved.