Repository intent, with provenance
Path-scoped rules carry stable IDs, validation state, source, and expiry. Stale or conflicting memory cannot silently become truth.
Repository-aware code review
One thing before you merge.
Ahem remembers the rules your code cannot explain, routes each change to the right AI reviewer, and returns one evidence-backed verdict—not a pile of bot comments.
Read-only review · ZDR model routing · no repository code execution
AHEM REVIEWPR #13 · 7.3s
Require TLS outside local development
securitycorrectnessrelease
CLAIM EVALUATED
Plaintext SMTP remains possible
Rejected · intentional dev/test behavior
Plaintext SMTP remains possible
Rejected · intentional dev/test behavior
✓
SAFE TO MERGE
The changed production path fails closed unless TLS is fully configured.
5/5known regressions caught in the corrected replay
3/3verified clean changes passed
52%less recorded model cost than the full council
How Ahem thinks
More context. Fewer opinions.
Every review starts from a bounded Git change and the few validated repository invariants relevant to it.
The right reviewer for the risk
Ordinary changes get correctness. Auth and tenant boundaries get security. Migrations and deploys get release review.
Evidence outranks votes
High-risk findings face an independent arbiter. Repetition does not make a weak claim stronger.
One merge signal
Useful disagreement, resolved.
✓SAFE TO MERGE
The TLS requirement is enforced outside explicit development and test environments.
Rejected claim
“Plaintext SMTP remains possible.” Intentional in the documented development/test mode and pre-existing—not a regression.
“Plaintext SMTP remains possible.” Intentional in the documented development/test mode and pre-existing—not a regression.
7.3 seconds · $0.0219
Two model calls on a real Syntropy security change. The arbiter rejected the noisy claim and preserved a clean verdict.
Early internal validation on an eight-change Syntropy replay; not a guarantee of future defect detection. Cost comparison uses recorded successful model responses under the tested routing profiles.
Private beta
Let Ahem clear its throat on your repo.
Tell us where your code lives. We’re starting with Forgejo and Gitea teams that care about private, explainable merge protection.