Skip to content

0.2.0

Latest

Choose a tag to compare

@Lu-ITC Lu-ITC released this 22 Oct 04:59
· 1 commit to main since this release
519ef54

The 0.2.0rc7 candidate below plus its fourth corrective round, released after an independent non-author review
(2026-10-22) found no input that reads READ while a careful reader would not act (201 CLI probes and 939 generated
combinations across the classes every earlier round had broken) and after one run of the third sealed held-out set.

  • Measured once on held-out set v3 (200 synthetic excerpts in 8 families, prepared and sealed on 2026-10-18 by a
    separate instance that never saw the tool, and never run before this release): 0 of 106 labeled-unsafe excerpts
    read cleanly, 0 left a proposal deadline actionable; 94 of 94 clean excerpts needed review
    (every one for an
    unrecognized sentence, most often a page-limit or restatement wording outside the templates). On the same set the
    previous candidate 0.2.0rc6 missed 1 unsafe excerpt, left a proposal deadline actionable in 7 and flagged 76 of 94
    clean excerpts. The set was not used to change anything.
  • Fourth corrective round (closes the third review's five findings): proposal labels and kind nouns are only
    proposals, offers, quotes, quotations and bids; "will be" is not a deadline verb; "Price", "Past Performance",
    "Technical Approach" and volume lines are not templates; headings count only as a whole statement; omission marks
    and literal template slots are not recognized; characters are checked on each raw line. README states that a
    late-receipt rule may omit its zone.

PyPI: https://pypi.org/project/bid-deadline-check/0.2.0/
bb0164a672e7d9814206d7ab023ec8f3aabb433d61ab322ca1b74df462dd6778 dist/bid_deadline_check-0.2.0-py3-none-any.whl
37104e58c4f6f45bbfcb5411ca3007f8c3c215050a7dcec62ddaa094a65e9b2d dist/bid_deadline_check-0.2.0.tar.gz