Coding · Advanced
Formal proof backlog triage for critical code modules
Keep unproven lemmas visible and route each proof gap to its owner
Use with BotBento
Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.
- On a scheduleWeekly proof status sweep
- ThenMatch open proofs to modules and owners
- ResultPrioritised proof gap digest
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.
Quick answers
What does it do?
Keep unproven lemmas visible and route each proof gap to its owner. Result: Prioritised proof gap digest.
What does it need?
Tools: GitHub, Docs, Notes. Advanced: more tools and setup.
How do I run it?
On a schedule: Weekly proof status sweep. Copy the prompt below into a bot in BotBento.
Prompt to start with
BotBentoRecommended
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.