Limited Edition Jonathan / ob1 + memory
Series ▾
00 Overview & index01 The vision02 Codex deep dive03 Claude Code deep dive04 Comparison05 Fleet Memory v206 OB1 ideas
Ideas · open source

What OpenBrain can borrow.

OpenBrain — OB1 — already aims at cross-agentic memory. Sharing what agents know is part of what it's built for. So these aren't ideas for some other product — they're concrete improvements to something OpenBrain is already reaching for, drawn from how Codex and Claude Code actually handle memory.

Three patterns from the Codex teardown and the portable design transfer almost for free — and OB1's roadmap is already half-reinventing them. This is where we take what the study turned up and point it straight at OpenBrain.

The question was never "should OpenBrain have cross-agent memory" — that's the point of it. The question is how to make the version it's already building genuinely robust.

01 / 04 — the fit

Cross-agent memory is already the point.

Sharing memory across agents isn't a bolt-on for OpenBrain — it's part of the mission. A public thought graph, a searchable directory, repo-driven content, README-to-HTML: a brain meant to be read by people and agents alike. The patterns below just make that robust. One thing to keep straight, though — OpenBrain is a different project from the personal agent fleet:

OpenBrain

The shared, public brain

Curated, durable, shareable knowledge — with cross-agent memory as a core purpose. Repo-driven, source-of-truth in GitHub, meant for people and community. The subject of this page.

The personal fleet

A separate project

Its own private agents and memory, not necessarily tied to OpenBrain at all. The same lessons apply — but it's a different home, covered in Fleet Memory v2.

OB1's roadmap — smart ingest, re-embedding, content-fingerprinting, a wiki compiler, thought-edges — is quietly rebuilding the same pipeline-and-ledger machinery the memory study mapped. So borrow it instead of reinventing it.

02 / 04 — three borrows

Take these, nearly for free.

Borrow 01

The promotion gate

from Codex's selected_for_phase2

OB1's biggest risk as it grows is becoming a dumping ground — every capture lands in the graph, signal drowns in volume. A promotion gate fixes that: raw captures stay in a staging layer; only promoted thoughts become curated wiki/graph nodes. It turns "everything I ever clipped" into "the knowledge I chose to keep" — without losing the raw trail.

Borrow 02

The job ledger

from Codex's jobs table · see the deep dive

OB1 already needs workers for smart-ingest, embedding, re-embedding, and wiki compilation — and the open PRs are each solving lease/retry/idempotency ad hoc. One jobs table with lease_until + input_watermark + retry_remaining makes every one of those pipelines crash-safe and resumable, and gives a single "what's processing / stuck" view. It's the reliability spine the roadmap keeps approximating.

Borrow 03

Provenance + supersedes + scope

from our node_claims + the portable design

A second brain that can't evolve a fact without losing the old one rots. Borrow the claims spine: every node carries source_uri, a fact/inference status, and a superseded_by link. Now OB1 can show why it believes something, evolve it as understanding changes, and never silently contradict itself — the exact integrity a public knowledge base lives or dies on.

03 / 04 — two brains, one bridge

Let them feed each other.

Here's the optional idea — and it's the one place the two separate threads can touch. Keep OpenBrain and the personal fleet independent, but let the fleet promote into OpenBrain: when an agent learns something durable and shareable — a reusable technique, a vetted fact — the consolidation step can publish it into OB1 as a sourced knowledge node.

the bridge
  agents ──▶ the personal fleet (private, scoped, provenance)
                     │
                     │  consolidation promotes the durable + shareable
                     ▼
              OB1 (public knowledge graph + wiki)
                     │
                     ▼
            humans + community + the agents themselves read it back

OpenBrain stays the shared, public brain; the fleet keeps its own private memory. They don't have to connect at all — but if they do, provenance carries across the seam, and an agent can consult either: its own working memory, or the shared brain of vetted knowledge.

04 / 04 — the honest caveat

Keep the two projects separate.

Worth saying plainly, because it's easy to blur: OpenBrain and the personal agent fleet are different projects. The fleet doesn't have to touch OB1 at all — it has its own memory to upgrade. What they share is the playbook, not the database. Improve each on its own terms.

  • Improve OpenBrain's cross-agent memory directly — promotion gate, job ledger, provenance — making the thing it's already building robust.
  • Upgrade the personal fleet on its own track — same lessons, separate codebase; it doesn't depend on OpenBrain.
  • Bridge only if you want to — optionally promote vetted, shareable learnings from the fleet into OpenBrain; never pipe raw agent runs into the public graph.

Do that, and both get better on their own terms — and if you bridge them, they compound: agents get sharper from OpenBrain's vetted knowledge, and OpenBrain gets richer from what the agents prove out in the field.