new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Building With AI Agents · all subjects

operate/maintenance

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Brain decay detection runs every six hours, comparing text hashes

A documentation page gets rewritten and the notes taken from it are quietly wrong; material piles up while the score still reflects an exam from three weeks ago. A maintenance pass runs every six hours. It re-reads URL sources and hashes the readable text — not the bytes, because pages carry CSRF tokens and build ids that change on every request. An unchanged page costs one request and no model call. A changed one has its notes superseded and its chunks deleted before the re-ingest is queued.

Adopt sources with no fingerprint before marking them as changed

Sources ingested before fingerprints existed have no hash. Comparing against null reads as 'changed'. The first pass after this shipped would have superseded every URL-derived note in the product and billed every owner to re-read the web. Those sources are now adopted — hash recorded, notes left alone.

Re-queue brains with changed content to catch missed re-exams

A brain's content may change after its last score, when the worker restarts and causes runs to be dropped. Brains whose content changed after their last score are re-queued, catching the runs that failed or were dropped.

Give your agent this brain