name	audit-arithmetic
description	Audit for arithmetic and boundary bugs (overflow, off-by-one, drift)
context	fork
agent	auditor
disable-model-invocation	true

Assume there is at least one arithmetic or boundary bug in this code.

Audit for:

Off-by-one errors
Incorrect inequality direction (< vs <=, > vs >=)
Overflow / underflow (int, long, specifically nanoTime arithmetic)
Implicit narrowing or widening conversion
Incorrect rounding or truncation
Sign errors
Sentinel value collisions (can a valid value equal a sentinel?)
Counter drift (can a counter diverge from the quantity it tracks over a long-running cache?)
Timer wheel bucket arithmetic (modular arithmetic, wrap-around)
Frequency sketch counter saturation and reset arithmetic
Hill climber / adaptive sizing: window vs main partition adjustment (percentage calculations, rounding, overshoot, oscillation)
FrequencySketch table size calculation (ensureCapacity rounding to power of two, interaction with maximumSize)
Weight delta computation in UpdateTask (sign conventions, can intermediate sums overflow when weights are near Integer.MAX_VALUE?)

For each suspected issue:

Provide a concrete input (specific key, value, weight, time values)
Show step-by-step evaluation through the code
Show expected vs actual behavior
If it requires billions of operations, state the count needed

Ignore style and performance. Only report high-confidence defects supported by evaluation traces.

المزيد من هذا المستودع

نفس المستودع

audit-adaptivity

ben-manes/caffeine

Audit the adaptive window hill-climber and region-resize logic for implementation defects (not algorithm quality)

2026-06-1717.7k

audit-jcache-conformance

ben-manes/caffeine

JSR-107 (JCache) spec-conformance audit

2026-06-1717.7k

audit-state-machine

ben-manes/caffeine

Audit explicit state machines (drain status, node lifecycle, async-value lifecycle) for illegal or missed transitions

2026-06-1717.7k

audit-temporal-walk

ben-manes/caffeine

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).

2026-06-1717.7k

audit-sibling-divergence

ben-manes/caffeine

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.

2026-06-0217.7k

audit-contract-drift

ben-manes/caffeine

Find places where documented API contracts and the implementation diverge

2026-04-2717.7k

name	audit-arithmetic
description	Audit for arithmetic and boundary bugs (overflow, off-by-one, drift)
context	fork
agent	auditor
disable-model-invocation	true

Assume there is at least one arithmetic or boundary bug in this code.

Audit for:

Off-by-one errors
Incorrect inequality direction (< vs <=, > vs >=)
Overflow / underflow (int, long, specifically nanoTime arithmetic)
Implicit narrowing or widening conversion
Incorrect rounding or truncation
Sign errors
Sentinel value collisions (can a valid value equal a sentinel?)
Counter drift (can a counter diverge from the quantity it tracks over a long-running cache?)
Timer wheel bucket arithmetic (modular arithmetic, wrap-around)
Frequency sketch counter saturation and reset arithmetic
Hill climber / adaptive sizing: window vs main partition adjustment (percentage calculations, rounding, overshoot, oscillation)
FrequencySketch table size calculation (ensureCapacity rounding to power of two, interaction with maximumSize)
Weight delta computation in UpdateTask (sign conventions, can intermediate sums overflow when weights are near Integer.MAX_VALUE?)

For each suspected issue:

Provide a concrete input (specific key, value, weight, time values)
Show step-by-step evaluation through the code
Show expected vs actual behavior
If it requires billions of operations, state the count needed

Ignore style and performance. Only report high-confidence defects supported by evaluation traces.