Menu
Attempt formal correctness proofs for all public cache methods
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit the adaptive window hill-climber and region-resize logic for implementation defects (not algorithm quality)
JSR-107 (JCache) spec-conformance audit
Audit explicit state machines (drain status, node lifecycle, async-value lifecycle) for illegal or missed transitions
Heavyweight history-mining bug audit. Walks the caffeine module's git history chronologically (oldest to HEAD), maintains a forward-tracked issue database, and surfaces concerns introduced by past commits that were never resolved. Catches bugs that snapshot mining cannot — half-fixes invisible from current state, latent+trigger pairs across multi-commit interactions, and partial refactors. Slow (model/effort-dependent; ~24h on Opus + max effort) and rare-run (every several months or before a major release).
Differential audit comparing matched code paths that should behave identically. Spawns one auditor per sibling pair (sync/async, bounded/unbounded, view consistency, bulk vs single, generated node variants, read fast vs slow, adapter conformance) and requires a concrete witness scenario where the two paths diverge observably.
Find places where documented API contracts and the implementation diverge
| name | audit-correctness-proof |
| description | Attempt formal correctness proofs for all public cache methods |
| context | fork |
| agent | auditor |
| disable-model-invocation | true |
Attempt to PROVE the correctness of the cache, not to find bugs.
For each public method (get, put, remove, compute, computeIfAbsent, merge, replace, size, clear):
State the method's specification: preconditions, postconditions, concurrent behavior promises.
Identify the synchronization protocol ensuring the postcondition.
Write a proof sketch: a. Assume the precondition holds b. Identify the critical section(s) c. Show the postcondition is established within the critical section d. Show no concurrent operation can invalidate it before the caller observes
If you CANNOT complete the proof at any step, stop and report:
Gaps in the proof are more valuable than speculative bug reports — a gap tells us exactly where to look.
Do not provide praise or style commentary.
