Evidence adjudication engine
The engine separates collection from promotion. Generated observations never modify canonical claim levels automatically.
Promotion rules
ADJ-R01 — community-reported-to-observed
- At least two independent public observations, or one public event linked by GitHub to its achievement detail.
- Material timestamps and attribution are retained.
- No unresolved contradiction directly defeats the promoted statement.
ADJ-R02 — observed-to-confirmed
- Controlled reproduction on at least two independent accounts.
- Positive and relevant negative controls are documented.
- Two reviewers agree and disclose conflicts.
- Processing delay is measured rather than assumed.
ADJ-R03 — any-to-official
- A maintained or preserved GitHub-owned source explicitly states the material contract.
ADJ-R04 — attestation-limits
- Participant attestation alone cannot promote a claim.
- A badge sighting alone cannot prove an exact threshold or qualifying event.
ADJ-R05 — negative-and-inconclusive-evidence
- Negative and inconclusive observations remain visible.
- They may narrow a claim but cannot be silently discarded or treated as proof of non-qualification.
Current decisions
| Decision | Claim | Outcome | Proposed level |
|---|---|---|---|
ADJ-D001 |
CLM-003 |
defer | official |
ADJ-D002 |
CLM-004 |
defer | official |
ADJ-D003 |
CLM-002 |
defer | official |
ADJ-D004 |
CLM-006 |
defer | observed |
ADJ-D005 |
CLM-008 |
defer | official |
ADJ-D006 |
CLM-010 |
defer | official |
ADJ-D007 |
CLM-005 |
defer | official |
Decisions record remaining research after maintainer-reviewed canonical reconciliation. Generated observations never change claims automatically.
ADJ-D001 — CLM-003
GitHub’s live Quickdraw fragment now states the five-minute contract. Further work is limited to issue equivalence and processing-delay edge cases.
ADJ-D002 — CLM-004
GitHub’s linked YOLO event shows that an outstanding review request with zero submitted reviews can still be classified as ‘Merged without a review’. Submitted COMMENT, REQUEST_CHANGES, APPROVE, dismissed-review, and merger-identity cases remain separate controls.
ADJ-D003 — CLM-002
GitHub’s live Pull Shark x4 fragment publishes the complete merged-pull-request milestone table.
ADJ-D004 — CLM-006
GitHub-owned x3 and x4 fragments confirm tier existence, but not the reported 1, 10, 24, and 48 boundaries. The numeric claim remains community-reported pending controlled boundary counts.
ADJ-D005 — CLM-008
GitHub’s live Galaxy Brain x4 fragment publishes the complete accepted-answer milestone table.
ADJ-D006 — CLM-010
GitHub’s Starstruck fragments publish the complete milestone table and retain creator attribution for at least two currently organization-owned repositories. Transfer timing, forks, archival, falling counts, and award persistence remain bounded edge cases.
ADJ-D007 — CLM-005
The broad trigger is official. Two independent GitHub-linked squash cases show that attribution can survive when the final commit retains the account-linked trailer; rebase, stripped trailers, email mismatch, later rewrites, and exact tier counts remain open.