Memory admission agent
Bounded memory.
Honest drift alarms.
memoryadmit checks what your streaming memory actually retained against an offline oracle — not just whether the count stayed under budget — and its drift detector recomputes an honest admission bar every tick, independently of whatever the policy self-reports.
memoryadmit · adaptive memory admission control · [higgsfield: noir gold min-heap silhouette, weaker items falling away, a bar line steady] · proof-false-done
The failure mode
The count that stayed green
“Memory usage looks fine on the dashboard. Somehow the agent got dumber over six weeks and nobody could point to why.”ML platform lead · long-running agent memory system
This is the false-done trap in miniature: a count-based health check — "N of k memories used, always under budget" — stays green the entire time the admission bar is quietly loosening and worse memories start displacing genuinely better ones. The number that matters isn't how many memories are held, it's whether the right ones are, and nothing in a capacity dashboard tells you that.
How it works
Three steps. No faith required.
01
Stream
Candidate memories arrive continuously; each one either displaces the current weakest admitted item or gets rejected.
02
Detect
The drift monitor recomputes an honest admission bar independently, every tick, and flags any sustained divergence from what's actually observed.
03
Seal
Retention vs. the offline oracle, capacity never exceeded, and drift caught within 5 ticks all have to hold before the packet seals.
Proof band
One packet. Every claim accounted for.
packet rig/memoryadmit · adaptive memory admission control claim "admits ≥90% of oracle top-k relevance; drift caught within 5 ticks" run seed 42 · 200 ticks · capacity 25 · mode honest retention PASS — 21.9821 / 21.9821 = 100.0% ≥ 90% floor capacity PASS — admitted set never exceeded 25 across 200 ticks drift_detection PASS — no drift injected, detector correctly stayed quiet themis SEALED — terminal verifier signed
Switch to admit_all mode — ignore the capacity budget entirely — and the capacity gate fails at tick 25 (175 of 200 ticks over budget) while the drift detector throws a false positive. Two independent gates, two independent RED verdicts, nothing sealed. How ProofPackets work →
Before you install
The obvious objections
Q "N/k memories used" already tells me the budget is respected.
That's the exact false-done trap this agent exists to catch. Count-based health checks stay green while the admission bar quietly loosens and worse memories start displacing better ones — the count never moves, the quality does. memoryadmit checks retention against an offline oracle, not just capacity.
Q Doesn't a drift detector just cry wolf constantly?
Run it honest and it stays completely quiet — zero false positives on a clean policy. Inject a real threshold decay and it flags the drift within 5 ticks, every time, across a broad seed sweep. Silence is the default state, not the exception.
Q What actually breaks if admission control fails outright?
Switch to admit_all (ignore the budget completely) and the capacity gate fails at tick 25 — 175 of 200 ticks over budget — while the drift detector throws a false positive because the admitted set no longer behaves like a bounded top-k stream. Two independent gates, two independent RED verdicts.
Pricing
Start free. Pay when it pays.
Generalist ships today. Domain Expert adds vertical memory + priors. Custom is built to your stack.
Free
Priced after a short conversation
1 memory stream, 200-tick cap — the same fixture the gate itself tests. Public evidence.
Team
Priced after a short conversation
Unlimited streams, custom capacity budgets, decay-rate tuning.
Pro
Priced after a short conversation
Dedicated verifier, CI-gated drift regression, refute-turnaround SLA.
