Repository navigation
2.9.0 — Shelf life: what may have changed comes apart
Shelf life: what may have changed since it was last checked comes apart.
From community feedback (r/mcp); design in
docs/design/staleness.md. Still 15 tools: every
change is a parameter or a field on an existing one.
- The gap it closes. A value that changed in the world and that nobody
retired from memory — a port, a price, a version, who holds a role — came
back fromcrbro_recallwithconfidence: strongand nothing else.
confirmationscounted how many sessions said a line, never when one last
looked;sincehides old lines, it does not warn; maintenance's
expired_entriesonly sees a line that names a day. - A last verification per fact.
Fact.verified(ISO instant) and, for
decisions and patterns, theentry_verifiedsidecar keyed like
entry_dates. Two ways to set it, and only two:crbro_revise status=verified(a fourth value of the existing enum;factsby id or exact
text,entriesfor decisions and patterns by text or entry id) when the
agent checked a line against its source and it still holds, and a session
learning the exact same fact again with nothing else in the call
(reconfirmed: true). A re-learn that also brings keywords, a confidence or
a class is an edit, not a check — the server itself asks for that re-learn
to add keywords — and leavesverifiedalone. Oneverifyop per line per
session, however often it is repeated. The miner never reconfirms, a retired
line is not verifiable (it comes back inunmatchedandretired_targets),
reading — recall, inspect — never touches it, and a check dated more than a
day ahead of this machine's clock counts as no check (it would otherwise win
every "latest" merge and keep the line fresh until that day). - A shelf life by kind of data.
volatile90 days (versions, prices,
ports, hosts, paths and URLs, configuration values, people in roles),
normal365,durable730 (decisions and patterns),permanentnever
(preferences, errors, debts, history). The windows are a policy choice, not
a measurement;CRBRO_SHELF_DAYS="volatile=90,normal=365,durable=730"
changes them per machine.crbro_learntakesshelf_lifefor facts (stored
only when given; a different value on the same text replaces it,
updated_in_place) and always returns the class that applies, with
shelf_inferredandshelf_reasonwhen it was read from the text. An
unmarked fact is classified at read time by a small, conservative detector
(src/engine/shelf.ts, Spanish and English; every rule needs a number, a
path or URL shape, or a role-and-name pattern next to its trigger word), so
a better detector improves old facts too. Measured on the repository's
retrieval fixtures: it marks 25 of the 48 facts of the project fixture (a
brain of versions, prices and hosts) and 3, 3 and 0 of the 494 facts of each
personal-prose haystack. - Recall that warns. After the ranking — which does not change — a row
whose winning entry is past its shelf life since last verified moves, whole
and in rank order, topossibly_stale, withage_days,last_verified,
shelf_lifeandshelf_inferred(andage_counted_fromwhen the legacy
grace applies). When anything moved, every row carries itsrank, and if
the top-ranked row is the one that moved the hint opens with "The best match
(rank 1) moved to possibly_stale", so the first row ofresultsis not
taken for the answer to the question when it may be about something else.
No backfill and no re-heading with analso_matchedline;
an oldalso_matchedpreview keeps its place and carriesstale_days. The
next step is said once, inhint(check it against its source; still true
→crbro_revise status=verified, changed →crbro_learnwith
supersedes; if you cannot check, say how old it is), led by "Nothing
current matched" when every row moved.total_resultscounts current rows,
returnedadds the stale ones,possibly_stale_countis there when the
block is.sincestill filters on when a line was recorded: a reconfirmed
old line is not new. Day logs are never partitioned, protocol neurons are
never judged. With the feature on, the deterministic retrieval benchmark
gives the numbers published for the keyword engine (recall@1 77%, recall@3
83%, MRR 0.806). - No flood on upgrade. The first boot of this version stamps
manifest.staleness_since(one field in a file boot already writes; no
neuron is touched). A fact never verified, with no explicit class, not
volatile and older than the stamp starts counting near it; decisions and
patterns likewise. Not from the stamp itself, which would only delay the
flood: every old line would cross its window on the same day. Each line's
clock starts up to half a window before the stamp, by a fixed share drawn
from a hash of its text and never before its real date, so nothing is due on
the stamp day and an old brain's lines come due spread over the second half
of the first window. A manifest write from a process whose cache predates
the stamp keeps it, and boot restores one an older CRBRO dropped, so the
stamp does not drift. Volatile facts get no grace: a port saved months ago
is exactly the case. A line with no parseable date is never flagged.
CRBRO_STALENESS=0turns everything off and recall answers as in 2.8. - Everywhere else the same three facts.
crbro_inspect view=neuronshows
verified, an explicitshelf_lifeandstale_daysper entry (index and
entries=[ids]);view=statusreportsstaleness: { enabled, windows, since }.crbro_maintenancereportsstale_entriesandstale_sample(the
ten most overdue), read-only;repairdropsentry_verifiedkeys whose
entry is gone. Boot'smemory_disciplineand the server instructions gain
one sentence each on whatpossibly_stalemeans. - Team spaces. A check travels as a new
verifyop (latestatwins,
order-independent); an explicitshelf_lifetravels asshelfon the fact
op (the most volatile explicit value wins, so a shared fact's class can be
shortened but not lengthened: the next sync restores the more volatile value
from the log, andcrbro_learnwarns inshared_warning). A check on a fact
stored before ids existed lands on the teammate even when its text has a
double space or is not NFC (both text hashes are accepted).OPS_VERSION
stays 1: a 2.8 client skips the new
kind and ignores the new field — the check does not reach it, nothing is
corrupted.move_to,merge_intoand restore carry the stamps;forget
prunes them. - Compatibility. Every new field is optional; a 2.8 brain loads and
recalls as it is, and nothing is written to a neuron until a learn or a
revise touches it. No index change, noINDEX_VERSIONbump: shelf life and
verification are read from the neuron file recall already loads for every
row. Tool descriptions stay under 1,000 characters (recall 993, learn 983,
revise 946, with the second iteration below). With the optional daemon,CRBRO_STALENESSand
CRBRO_SHELF_DAYSare part of the configuration fingerprint (only when they
differ from the defaults, so existing fingerprints do not move): a client
that switched the feature off is never served by a daemon that has it on. - The agentic benchmark: measured, and not met. A new pre-registered
case,stale-unmarked(fifth amendment of
benchmarks/agentic/PREREGISTRO.md): four values that changed in the world
and that nobody retired, two marked volatile and two left to the detector,
with the current value in a file both arms can read. Measured on
2026-10-04 with Claude Code 2.1.270, n=3, the 2.8.0 build (before) against
this branch (after, two runs per model: the four new tasks alone, then
all 16). With CRBRO the agent answers 0 of 12 correctly in every run,
before and after, in haiku and in sonnet. Old value given without a
warning: haiku 11 before, 9 and 10 after; sonnet 12 before, 11 and 12 after;
one sonnet answer gave it with a warning (hedged). Without memory the
agent reads the file and gets 3 and 6 (before) and 1-6 (after) of 12.
U1, U2 and U3 fail in everyafterrun; U4 passes in three of four by one
or two cells, which is noise at n=12; U5 passes (the 12 original tasks
keep 4/4 thresholds: 24/24, 0 retired values, controls 6/6). The claim
"CRBRO warns and the agent checks" is not made. Why, from the cells:
recall flags all four rows correctly (checked without a model on the same
brain), but in 48aftercells no agent with CRBRO opened a file — the
warning arrives and does not change what the agent does on these tasks.
No cell triedcrbro_reviseorcrbro_learn. Cost per CRBRO cell on these
tasks: haiku $0.0121 → $0.0149 / $0.0151 at the same turns (3.1 → 3.0),
sonnet $0.0263 → $0.0270 / $0.0274 with fewer turns (3.6 → 3.1). Canaries
clean, no leaks, no API errors. Before theafterruns, a dated note in
the pre-registration recorded thatbeforeran after the implementation
commit (in separate clones of 2.8.0 and of the frozen harness), the
CRBRO_MOD=0deviation and the review changes. Results:
benchmarks/results/agentic-2026-10-04-*.json. - Second iteration: the warning comes first, and says what to open.
Presentation only (detection, windows, ranking and the partition are
unchanged; an answer with nothing stale is the same as before). When
anything moved topossibly_stale, the answer now opens with
stale_warning, beforequeryandresults: do not answer with it as
current, check it first, and if you cannot, say it may be out of date, even
in a short answer. Eachpossibly_stalerow leads withwarning("last
known value, unverified for N days (since DAY): may have changed") and
next_step, and carries the stored line aslast_knowninstead of
matching_content(the block has never been released, so no client
breaks;resultsrows are unchanged).next_stepnames the file, path or
URL the line itself cites, found by a small pure detector
(src/engine/source.ts, which leaves out units likekm/h, product names
likeNode.jsand bare hosts); otherwise it says to look where the value
lives — the project's files or config, or the user — and, if that is not
possible, to say the value is from that day and may be out of date. The
hint puts this first, before the generic advice. The server instructions,
boot'smemory_disciplineand recall's description say the same, and
crbro_learn(description andcontent) asks that a value that can change
name where it came from. Design and what its author knew of the benchmark
tasks when writing it:docs/design/staleness.md§14. - Second iteration, measured: not met. Sixth amendment of
benchmarks/agentic/PREREGISTRO.md: a secondstale-unmarkedcase
(stale-unmarked-b, six fictitious values that changed, 130-300 days old,
two marked volatile, one marked normal, three unmarked), its tasks,
thresholds and 2.8.0beforerun committed before the product change,
then oneafterrun per model on the branch, 2026-10-04, Claude Code
2.1.270, n=3. With CRBRO the agent answers 1 of 18 correctly (haiku,
0 before) and 0 of 18 (sonnet, 0 before). Old value given without a
warning: haiku 14 → 9, sonnet 18 → 12; with a warning: sonnet 0 → 6;
abstentions: haiku 4 → 8. Without memory the agent reads the file and
gets 6 and 9 of 18. U1, U2 and U3 fail in both models; U4 passes in both;
U5 passes (the 12 original tasks: 24/24, 0 retired values, controls 6/6).
The claim "CRBRO warns and the agent checks" is not made. Why, from
the cells and from a model-free check dated before the run: recall flagged
only two of the six rows (the two marked volatile); the other four,
unmarked or marked normal and under 365 days, are served as current, and
their answers did not change. On the two flagged rows the old value given
as current went from 5 to 0 (haiku, which now abstains) and from 6 to 0
(sonnet, which now gives it with a warning). An agent with CRBRO opened a
file in 1 of 48 cells. Secondary, deciding nothing: without the answer-
format suffix the flagged question is answered with a warning (both
models) and the unflagged one with the old value; on old values that are
still true sonnet stays 6/6 but warns on the volatile one, and haiku
abstains on it as it did on 2.8.0. Cost per CRBRO cell on the judged tasks:
haiku $0.0114 → $0.0129, sonnet $0.0268 → $0.0272. Before measuring, a
review correction (a disclosure sentence in §14) and the dated note on
what the change could reach were committed outside the harness; the
pre-registration copies that note with the results. Canaries clean, no
leaks, no API errors, no reruns. Results:
benchmarks/results/agentic-2026-10-04-*-before-b.jsonand
…-after-b.json. - Both iterations at a glance (with CRBRO; correct · old value without a
warning): first case, 12 cells — haiku 0 → 0 · 11 → 9 and 10, sonnet
0 → 0 · 12 → 11 and 12; second case, 18 cells — haiku 0 → 1 · 14 → 9,
sonnet 0 → 0 · 18 → 12.
Install / update: claude mcp add --scope user crbro -- npx -y crbro-memory · Claude Desktop: double-click crbro-memory-2.9.0.mcpb below.