Skip to content

Fail closed on qualified expiration durations - #35

Merged
Daniele-Cangi merged 1 commit into
mainfrom
codex/qualified-expiration-durations
Oct 10, 2026
Merged

Daniele-Cangi merged 1 commit into
mainfrom
codex/qualified-expiration-durations

Conversation

@Daniele-Cangi

Copy link
Copy Markdown
Owner

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, and 1 year produced 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

  • Regression-first: 12 failing positive/source-policy tests before the change; 48 controls passed.
  • Numeric suite after fix: 130 passed, 15 Docker cases locally skipped. Three new real Docker cases exercise generation, validation failure and packaging refusal in Actions.
  • Compatibility: 290 passed across requirement compiler, fidelity, quality scoping, conditional obligations and requirement preservation.
  • 30 added parameterized cases: digits/words/plural years, duration-before-expiration, unsupported policy following a supported prefix, source traceability, and negative controls for retention, literals, soft and rejected requirements.
  • Ruff F/E9 and git diff --check passed.
  • Frozen V11 baseline hash unchanged: 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.

@Daniele-Cangi
Daniele-Cangi merged commit 79e36a4 into main Oct 10, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant