Skip to content

Data review: 2026-07-14#26

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
data-staging
Closed

Data review: 2026-07-14#26
github-actions[bot] wants to merge 1 commit into
mainfrom
data-staging

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Data review: 2026-07-14

Mode: staged · Scope: all states; no window

metric value
Fetched documents 520
Processed this run 361
Skipped (already settled) 159
Extracted candidates 1
Rejected (out of scope) 0
Published (whole tree) 1
New this run 1
Updated 0
Review queue 0
Est. Gemini cost $0.0416

By state

key count
DL 1

By source

key count
The Hindu 1

Review queue (reasons)

none

Every record is cited to a public source; accused names appear only from court records. Review the data/ diff and data/_review/ before merging. Nothing publishes until a human merges this PR.

@github-actions github-actions Bot changed the title Data review: 2026-07-11 Data review: 2026-07-12 Jul 12, 2026
@github-actions github-actions Bot changed the title Data review: 2026-07-12 Data review: 2026-07-13 Jul 13, 2026
@github-actions github-actions Bot changed the title Data review: 2026-07-13 Data review: 2026-07-14 Jul 14, 2026
@KiranPranay

Copy link
Copy Markdown
Member

Closing: this record is out-of-window/borderline. Under the launch scope (ALL states, 30-day rolling) the correct outcome is to filter it out, not publish. data-staging will be regenerated cleanly by the next supervised run. Superseded by the record-loss fix (#27) and the graduated auto-publish gate (#28).

@KiranPranay
KiranPranay deleted the data-staging branch July 14, 2026 20:43
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