Skip to content

v0.3.0 — procurement red flags

Choose a tag to compare

View all tags
@gulmezeren2-byte gulmezeren2-byte released this 17 Jul 16:08
· 10 commits to main since this release
v0.3.0
362b675

Procurement red flags. ihalent flags surfaces the per-award risk signals that transparency and audit work looks for — the same family as single-bid, generalised:

ihalent flags awards.jsonl
ihalent flags awards.jsonl --low-discount 5      # widen the near-estimate band
ihalent flags awards.jsonl --json

Each flag is a reason to open the file, never a verdict:

  • single_bid — one valid bid: no competing offer.
  • low_discount — the contract landed at or above the public estimate (negative discounts included): no downward price pressure.
  • no_estimate — no estimate was published, so the award can't be audited.
  • high_dropout — many firms took the documents, almost none submitted a valid bid.

An award can raise several at once; the ones raising the most flags — and the most money — sort to the top, and the coverage travels with the counts. On the bundled example it surfaces a real award that closed 2.96% above its estimate.

Available three ways: the CLI command, a flags MCP tool, and ihalent.analytics.risk_flags.

Full changelog: https://github.com/gulmezeren2-byte/ihalent/blob/main/CHANGELOG.md

Assets 2
Loading