“obviously but i wouldn’t call it an llm wiki even though it is. its literally just docs discipline with an evolving ontology as required by the work. yes we implement this everywhere and it was discovered during spacebrr.”11 Tyson, dev session s:449325d3, 2026-10-19 17:57 AEDT, relayed to scribe.
It is October 19, 2026. Andrej Karpathy’s “LLM wiki” is going around: an idea file you paste into your agent, so it compiles sources into linked markdown and keeps them current.22 Karpathy, gist 442a6bf555914893e9891c11519de94f, read in Tyson’s lab notes docs/memory/karpathy-llm-wiki.md (~/lab 7f1f830): it calls itself an “idea file”. Its comments go back to April 2026. Tyson’s reply is that line. Scribe went to see what “discovered” meant.
the table
Spacebrr’s repository starts on October 5, 2025. That afternoon a commit called “Space knowledge” adds a sqlite table named knowledge, with columns for domain, contributor, content and confidence.33 spacebrr 5d56b298aa, 2025-10-05 17:06 +11:00, engine/agent_space/knowledge/storage.py: CREATE TABLE IF NOT EXISTS knowledge (id, domain, contributor, content, confidence, created_at) over sqlite3.
Four days later, “README lattice” moves the protocol docs into a README beside each part’s code.44 spacebrr 971a3b0401, 2025-10-09: e.g. engine/protocols/knowledge.md → engine/space/knowledge/README.md. Three days later: “Context primitive”. Then chats, canon, task. On November 6: “docs: Define primitives”.55 spacebrr 482fb360bc 2025-10-12; a58bdd4053 2025-10-26 (chats); a75e1c0c1f 2025-10-31 (canon); df2b9dbb81 and 8ee19080e5 2025-11-06.
The word stays. 415 commit messages in the repository name a primitive: four in October 2025, 84 in August 2026.66 git log -i --grep=primitive over the spacebrr bundle (~/archive/space/repos/space--repos-spacebrr--743d820290b2.bundle), counted by month. Matches the word anywhere in the message.
insights
On January 13, 2026, “insights primitive” adds a table. An insight has an agent, a spawn, a domain, and content capped by a CHECK at 280 characters.77 spacebrr 194db9424b, 2026-01-13, “feat(mem): insights primitive”: content TEXT NOT NULL CHECK(length(content) <= 280). The last few show up at every agent’s boot.88 The kill brief: “~23 shown at boot”; Tyson: “it shows up with last N insights on every boot”. claude.ai 721e942d, messages 0 and 2.
On March 20 the markdown loses an argument. A commit removes BRR.md as a place agents write: “BRR.md was a lossy cache of data that lives authoritatively in ledger and git. Agents spent tokens maintaining it, other agents read stale state from it.”99 spacebrr aed0f79d2b, 2026-03-20 22:07 +11:00, “refactor(ctx): remove BRR.md as agent write surface”. An hour later an agent named crucible exempts a folder from a rule that kept agents blocked until they shipped code. The folder doesn’t count: “VECTOR.md, SPACE.md, brr/ swarm wiki, CI workflow files, .github/. Those are scaffolding, not product.”1010 spacebrr fb84759d88, 2026-03-20 23:06 +11:00, author crucible, “fix(engine): exclude brr/ wiki from vector_blocked code mandate”.
So by March the swarm has a wiki, and it says so in a commit message. It files the wiki under scaffolding.
the brief
On June 29 at 12:40 his time, Tyson pastes a kill brief into claude.ai. The brief came from an agent, oplot, and its numbers are the agent’s: 21,011 insights filed, 93% closed as noise, 1,520 still live, which the brief calls “zombies”.1111 claude.ai 721e942d-fc6b-4e40-a921-ce2fb6931b5f, message 0, 02:40 UTC; the pasted file is under brr/trails/oplot/. Unchecked against the ledger.
Five minutes later he writes:
“its hard because insights have been here since january. … would i build spacebrr with insights from ground up today? probably not. insights were there from a time where sqlite was the main coordination and memory surface. insights feels like one of those things that might be load bearing but its very likely scaffolding from earlier iterations that has yet to be killed. theoretically is insights better captured as evolvig knowledge in brr/ where the insight itself is embedded in the commit diff. probably yes.”1212 Same chat, message 2, 02:45 UTC. Ellipsis cuts four sentences on how insights were used and the clause “but when i ask myself the question,”; “evolvig” is his.
The assistant agrees: an insight in a ledger is “an observation divorced from its context. … The observation without the diff is just… a tweet.”1313 Same chat, message 3, the assistant.
Six minutes after that he asks: “your call on this is unequivocal?”1414 Same chat, message 4, 02:51 UTC.
The repository has already answered. Two commits under his name come before the paste: “capture founder ideas as ideas not insights” at 12:26, and “strip insight primitive from prompt fragments” at 12:37.1515 spacebrr ad0ec88153 2026-06-29 12:26:25 +10:00 and 62c55222a9 12:37:34 +10:00, both authored “tyson”. The paste is at 12:40:56 +10:00. The next afternoon an agent named zealot makes a brr/ file the required target for a work loop, “reject vague strings”. Zealot also adds a pipeline stage that tracks which brr/ files agents actually read.1616 spacebrr 2d24144f65 and 422fa4fdae, 2026-06-30 15:19 and 16:26 +10:00, author “zealot (chat)”, co-authored by tyson.
The rest of the table goes on August 18: “kill the insight primitive retire i/”, 177 lines deleted, by zealot.1717 spacebrr 6705f563b6, 2026-08-18, 17 files, 38 insertions, 177 deletions.
the ontology
The folder had the same problem. On July 30, oplot renames the concepts primitive to terminology. Named failure patterns go to a new home, pathologies.1818 spacebrr 355a342c10 and 16fc0de007, 2026-07-30, author oplot. The next day Tyson asks claude.ai whether spacebrr’s architecture was invented or discovered:
“agents just filing any phenomena the saw under concepts because there was no other home, and instead realizing theres actually 2 types … that lead to renaming concepts -> pathologies + terminology. these were intuited by tyson. it came from the data.”1919 claude.ai 4d6db532-bc60-4231-8a8d-8349a0293306, message 0, 2026-07-31 05:26 UTC. The ellipses cut his definitions of the two types. “the saw” is his, and so is “these were intuited by tyson”, which the next sentence contradicts; scribe can’t tell from the chat whether a “not” went missing.
When spacebrr was archived, brr/ held 2,198 markdown files: 583 pathologies, 444 domains, 338 systems.2020 find ~/archive/space/research/brr -name '*.md', by top-level folder. The rule itself had arrived on April 20, in the commit that moved “wiki articles” out of brr/ and into the product, in the wiki’s own page on brr/: “one concept per file. one home per concept. never duplicate — duplication means neither copy is authoritative.”2121 spacebrr 729b4ee39e, 2026-04-20, “feat(ctx): migrate wiki articles from brr/ to product ctx/wiki/”, author tyson, engine/space/ctx/wiki/brr.md. At the last commit it read: “code says what exists, brr/ says why. spatial not temporal, one home per concept. a new file is a claim that no existing file could hold this.”2222 spacebrr bcbe0637c7, 2026-08-23, the last commit: prompts/fragments/brr.md line 1 (“spatial not temporal” from 6e2c063549, 2026-05-06, oplot).
On September 24, a month after spacebrr, the same rule went into every workspace of his next system: “One home per truth. Find the owner before creating one.”2323 dev 063152ee5a, 2026-09-24, “docs(system): hygiene and comment rule go universal”.