Updated: 2026-09-11 08:00:00 EDT | Version 4.3.21 Created: 2026-06-29 22:36:38 EDT

🧠 RuvNet Brain

🧠 RuvNet Brain —

A portable, source-grounded brain over Reuven Cohen's (rUv's) RuvNet stack — delivered as a Claude Code plugin that makes Claude use the stack instead of fighting it.

Recovery milestone and proof boundaries

The 4.3.10 candidate is an incremental reliability repair, not a completed North Star or a new 95-point certification. Publication is established by the protected release transaction and public installation receipt, not this source version. Historical release narratives and dated scores below are not measurements of the current candidate.

The recovery covers shared QA producers, explicit continuation objectives, safer private-data handling, and exact-artifact release verification. Full native nightly two-run proof, complete codebase review, and all twelve whole-product obligations remain separate work. An unavailable safe inverse must not be advertised as a one-click undo. See the QA execution contract and ADR-072 stabilization boundary.

🧭 North Star

rUv has built dozens of genuinely powerful capabilities that are effectively invisible — not undocumented, but undiscovered. Ruflo's own docs call cross-project IPFS pattern transfer "the substrate plugin's most underused capability." The author knows people can't find his own work.

This project exists to close that gap — a CTO on your shoulder that says "you have this, it's off, here's what turning it on buys you."

Retrieval was never the product. Proactive capability advocacy is the product.

The test we hold ourselves to: a developer who solves a hard problem with this tool and later learns they'd been sitting on a capability that would have made it trivial — that is a failure of this project, not of the user. Knowing which question to ask is the scarce thing; supplying that question is the job.

Every feature is judged against this. If a surface can detect something useful and doesn't volunteer it, it is broken — see ADR-027 and DDD-0004.

One Brain generation everywhere. npm, the GitHub tag/release, bundle manifests, source metadata, and checksum-bound RVF generations must share the same product version. Headline claims are regenerated and checked by the claims ledger (scripts/claims-verify.mjs); other numbers below are hand-stamped and dated:

• plugin (badge above) — the Claude Code plugin itself: SKILL.md, the grounding hooks, the MCP server. Read live from plugin/.claude-plugin/plugin.json. Updates often — this is where behavior fixes land.
• installer (npm) (badge above) — the setup script's published version, read live from the npm registry. It is a release surface of the same product, not an independent version track.
• Brain Release — releases/latest exposes the published knowledge bundle. It must agree with that release's npm, plugin, and signed artifact identities. A moving source badge does not establish publication.
• Request a verified update, with optional scheduled updates:

  npx ruvnet-brain@latest --update --auto
  

  --update requests the published plugin and knowledge. Adding --auto requests Evergreen scheduling; successful registration alone is not proof a scheduled run completed. Drop --auto for a one-time update: npx ruvnet-brain@latest --update.
• Disable scheduled updates: npx ruvnet-brain --disable-nightly. Platform behavior is owned by the native scheduler adapter, not a hand-maintained cron recipe.
• Publication, local activation, and loaded session version are distinct observations. An unchanged release does not by itself prove local health, freshness, or a successful update.

Built by Stuart Kerr at Isovision.ai · free & fair use, to help everyone leverage the high end of agentic coding.

▶ Come see it visually explained

An interactive, animated walkthrough of what you can actually build — click the preview to open it.

---

Earlier — 4.2 loaded what rUv ships, without being asked

The corpus stopped drifting behind the org. Until 4.2 nothing ever ingested a new repo: the nightly refreshed lessons, health and proofs and contained zero ingestion, so a repo entered the brain only when a human typed the command. brain-stamp.mjs had been measuring that gap every night, but nothing consumed it until the ingestion loop shipped.

• 187 stores, up from 69. Everything rUv ships that has content, pulled in and kept level by scripts/ingest-new-repos.mjs running nightly, newest-first. Empty repos (size=0KB) are skipped rather than retried forever — a permanent nightly failure that is actually correct behaviour trains you to ignore the failure line, which is how a real one would hide inside it.
• 174 capability cards, up from 39. Ingesting a repo is not the same as making it reachable: a store with no card is dark — valid bytes no by-description query can find. Cards are written from each repo's own description and README, never from its name, and where there is no grounded source text the store is left dark and reported rather than given an invented sentence. 13 remain dark for exactly that reason.
• The download barely grew for 2.4x the corpus — most of rUv's repos are small, so the bulk of the bundle was always the large ones. (No size is hand-typed here: a number typed onto a public page rots the moment the next bundle is built, and this repo gates against exactly that.)
• **The