google-deepmind / google-deepmind/formal-conjectures
Queue triage: current inventory and remaining maintenance
- Dominant language
- Lean
- Stars
- 1.3k
- Forks
- 485
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 327
Description
Snapshot: **11 September 2026, 13:08 UTC**, GitHub's open PR/issue inventory.
| Inventory | Count |
| --- | ---: |
| Open PRs | 478 |
| Non-draft PRs | 408 |
| Draft PRs | 70 |
| PRs with an approved review decision | 15 |
| Open issues | 765 |
| Issues labelled `new conjecture` | 521 |
| Unlabelled issues | 113 |
These are inventory counts, not a fresh build or semantic-review audit. GitHub reported unknown mergeability for 441 PRs, so no corpus conflict estimate is asserted. The original 280-PR / 114-broken-import / 232-unreviewed figures belong to the **7 August** investigation and are not current counts.
| Work | Current disposition |
| --- | --- |
| Board visibility and queue/timing logic | [Open Formal Workflows](https://williamjblair.github.io/open-formal-workflows/); board #2 migration is merged |
| Exact statement/evidence/related-PR joins on FC pages | #5388, acceptance in #5377 |
| Status synchronization and proof-link metadata | Consolidated #4828 |
| Old listed already-stated issues | All 11 numbered issues and #136 are now closed; do not reopen them |
| PRs #4071, #4072 and #4285 | Still open; maintainer review of exact current diffs is needed before any supersession decision |
| Unlabelled issues and branches needing maintenance | Remain explicit triage work; current per-item inspection required |
Use exact repository/module/declaration/revision joins. Do not close fuzzy matches automatically or edit another contributor's branch. An old base or old green check is a reason to revalidate, not proof that a branch fails today.
The board repository was renamed from `fc-review-board` to `open-formal-workflows`. New navigation uses the current name; historical evidence URLs and schema identifiers remain intact. The board's upstream queue is not joined to unrelated fork PRs.
Roadmap: #4394. This issue remains the maintenance inventory, not another toolkit delivery tracker.
Contributor guide
Research direction
Start by reviewing the current inventory and the listed dispositions, then inspect each remaining unlabelled issue or maintenance branch using exact repository, module, declaration, and revision joins. Do not reopen closed issues, edit another contributor's branch, or close fuzzy matches automatically. Done means the remaining triage work has been inspected and its current disposition is recorded without treating old checks as proof.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100