Repository navigation
Fail closed on qualified expiration durations - #35
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
Small detection-only follow-up to issue #32 on merged main
669d630e.Independently confirmed that explicit expiration policies using
3 business days,90 calendar days, and1 yearproduced no numeric contract, generated a 90-day default, and passed local validation with no numeric probe.Extend only the duration recognizer to qualified business/calendar days and year(s). The strict integer-day extractor is unchanged: these policies now retain an unresolved threshold and comparison, source requirement IDs, and the existing ambiguity/numeric_contract_unproven path. No business-day/calendar inference, year-to-day conversion, architecture changes or new domains.
Verification
6f986fdf24ccdf89d2c9563d83e05f1534dce2a4270cb5decf0b39127659179d.No model API calls, blind-baseline rescores, README edits, retries or reverse_chunks-specific rules. Full suite and Docker gate still require CI on this head.
Deliberate exclusions
Do not widen comma/subordinate rules or semicolon handling in this checkpoint. The independently reproduced long-range retention/expiration association remains a separate diagnostic finding: a conservative refusal does not prove the retention duration is an expiration-alert horizon. No claim of universal wording coverage or reproduction of the external 48-phrase list.
Refs #32; do not automatically close the issue.