AGENTS.md

This is an LLM wiki in the Karpathy sense — a markdown knowledge base maintained by an LLM, ingesting raw sources and producing an evolving conceptual map.

Seed source: ~57 Slack messages tagged #explainingideaflow across 15 channels from 2022 to February 2026. Ongoing sources: notestream / Thoughtstream captures, talks, blog drafts, conversation transcripts.

Sister wiki: Vision Convo — one long-form conversation expanded into a graph.

Editorial stance

This wiki leans on Jacob's own voice. Verbatim quotes from Jacob are preferred over synthesis when the phrasing is distinctive ("graph database for your brain", "neocortex for the global mind/brain", "the God data structure"). Supporting synthesis fills in connective tissue.

Co-worker framings are included when they sharpened Jacob's thinking (Cody's "O(1) capture and recall", Joe Henke's "medium for thought", Taylor Mitchell's tree-vs-graph argument, Eden Chan's curation) — attributed by name.

External quotes (investors, users reacting to IdeaFlow) are attributed to the source.

Three layers

raw/      — lightly cleaned source excerpts, by year-window. Never overwrite.
wiki/     — LLM-generated pages. Framings, layers, pitches, themes, meta.
AGENTS.md — this file.
log.md    — append-only ingestion record.
index.md  — content catalog.

Page types

Frontmatter schema

---
title: Human-readable title
type: framing | layer | pitch | meta | concept | index
visibility: public | unlisted | private
sources:
  - raw/slack-explainingideaflow-2022-2026.md#2024-03-22
related:
  - wiki/framings/medium-for-thought.md
  - https://wikihub.md/@jacobcole/vision-convo/wiki/projects/ideaflow
audience: investors | users | builders | internal | all
confidence: high | medium | low | speculative
---

Linking

• [[Page Title]] — Obsidian-style wikilinks for intra-wiki. WikiHub renders these.
• Full https URLs for links into the sister vision-convo wiki (cross-wiki wikilinks aren't supported).
• Prefer linking by canonical title.

Risks and mitigations

Codex flagged (and Jacob adopted):

1. Context collapse — co-worker quotes can look more canonical/endorsed than intended. Mitigation: always attribute verbatim; keep co-workers' framings as influence, not doctrine.
2. Internal language leakage — metaphors like "Team Humanity" or "the God data structure" may read grandiose out of context. Mitigation: each framing page opens with what Jacob was actually explaining to whom, and on what date.
3. Metaphor sprawl — too many overlapping images without a canonical synthesis. Mitigation: canonical-terms glossary; each framing cites north-star-thesis.
4. Product/worldview blur — readers may conflate the software with the philosophy. Mitigation: what-it-is-not and system-map draw the line explicitly.
5. Historical vs current — a 2022 framing may read as a 2026 claim. Mitigation: every framing has an explicit first-used date and still-canonical flag; see chronology.

Ingestion protocol

When a new source is added (new Slack export window, a talk transcript, a notestream batch):

1. Drop the cleaned source into raw/. Append to log.md with date + one-line summary.
2. Walk the source. For each new metaphor/framing/pitch:
   • If a framing page exists, add a dated section.
   • If not, create one under the right folder.
3. Update chronology with the new data point.
4. Re-check canonical-terms — new terms may emerge.

Editorial voice

• Jacob's verbatim lines are treasured. Keep them.
• Surrounding prose is the wiki's voice — third person, present tense, no marketing copy.
• When something is speculative or in-progress, say so.
• Date things. 2024-03-22 is part of the data.

What this wiki is for

Jacob, 2025-10-something (paraphrased): "somehow integrating all of the #explainingideaflow tags from notestream and slack into some LLM Wiki which coherently updates the IdeaFlow vision."

So: this is that wiki. It's the substrate under every future pitch, every onboarding doc, every investor update — the canonical place where all the framings live and evolve together.