---
name: formal-proof-backlog-triage-for-critical-code
description: "Keep unproven lemmas visible and route each proof gap to its owner. A bot keeps a formal-verification effort honest by tracking which proofs are actually finished."
license: CC-BY-4.0
compatibility: "Needs access to: GitHub, Docs, Notes."
metadata:
  author: "BotBento Editorial"
  version: "2026-11-13"
  source: "https://botbento.com/usecases/formal-proof-backlog-triage-for-critical-code/"
  kind: workflow
  hermes:
    tags: ["formal-verification", "code-review", "proofs", "triage", "reporting"]
    category: coding
---
# Formal proof backlog triage for critical code modules

Keep unproven lemmas visible and route each proof gap to its owner

## When to use

A bot keeps a formal-verification effort honest by tracking which proofs are actually finished. It scans proof annotations and build output, matches unfinished, stale or failing proofs to the modules and people responsible, and produces a short weekly list a reviewer can act on.

## Steps

1. On a schedule: Weekly proof status sweep
2. Match open proofs to modules and owners
3. Prioritised proof gap digest

## Instructions

Read the proof annotations and build output in the linked repository each week and list every lemma or module whose proof is missing, stale or failing, with the file path, owner and how long it has been open. Group items by risk area and flag any change since the last run that invalidated an existing proof. Write the digest into the team notes and draft a short message to the owners of the oldest items; hold that message until the user approves it. Never edit, close or delete proof files.

## Source

Summarized in our own words from [AlphaProof Code](https://news.ycombinator.com/item?id=50439193) (Hacker News, checked 2026-11-13). Any results described there are the authors’ own.

From the BotBento use-case directory: https://botbento.com/usecases/formal-proof-backlog-triage-for-critical-code/. Licence: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
