497fab8e25a1dbdd2a61951004591194d20e819e
new file mode 100644
index 0000000..eec140e
@@ -0,0 +1,97 @@
+---
+title: AGENTS.md — schema for this LLM wiki
+visibility: public
+---
+
+# AGENTS.md
+
+This is an **LLM wiki** in the [Karpathy](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) 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](https://wikihub.md/@jacobcole/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
+
+| Type | Folder | Purpose |
+|------|--------|---------|
+| `framing` | `wiki/framings/` | One durable metaphor Jacob has used ("graph database for your brain") |
+| `layer` | `wiki/layers/` | Functional scale (personal / team / collective cognition) |
+| `pitch` | `wiki/pitches/` | Audience-specific translation of the vision |
+| `meta` | `wiki/meta/` | Pages about this wiki itself (design history, sources) |
+| `concept` | `wiki/` (root) | Cross-cutting single-page entries (north-star-thesis, what-it-is-not, system-map, chronology, canonical-terms, open-questions, use-cases) |
+
+## Frontmatter schema
+
+```yaml
+---
+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.
new file mode 100644
index 0000000..9367e91
@@ -0,0 +1,77 @@
+---
+title: IdeaFlow Vision — Index
+type: index
+visibility: public
+---
+
+# IdeaFlow Vision
+
+> An LLM wiki synthesizing how Jacob Cole has explained IdeaFlow over the years — drawn from the `#explainingideaflow` tag corpus (Slack 2022→2026, notestream captures, talks, docs). Sister wiki to **[Vision Convo](https://wikihub.md/@jacobcole/vision-convo)** (one long conversation, expanded into a graph). This wiki is the longitudinal archive — same core vision, many angles, many audiences.
+
+## The thesis in one breath
+
+> "Now, what I'm actually building is a massive-scale collective cognition system for humanity. But one of the pieces it takes is a personal knowledge management system."
+> — Jacob, March 2024
+
+## Start here
+
+- [[north-star-thesis]] — what IdeaFlow is really for, in one page
+- [[system-map]] — personal → team → humanity, the three scales
+- [[chronology]] — how the framing evolved 2022→2026 (refined, matured, forked — not changed)
+- [[what-it-is-not]] — category-confusion prevention
+
+## Framings (one page per durable metaphor)
+
+Each framing is a way Jacob has explained IdeaFlow to a specific audience at a specific moment. They don't contradict; they rotate the same object to reveal different faces.
+
+- [[framings/graph-database-for-your-brain]]
+- [[framings/medium-for-thought]]
+- [[framings/neocortex-for-the-global-brain]]
+- [[framings/bicycle-for-the-mind]]
+- [[framings/notebook-for-our-minds]]
+- [[framings/god-data-structure]]
+- [[framings/open-source-knowledge-graphs]]
+- [[framings/team-humanity]]
+- [[framings/gestalt-capture-to-gestalt-processing]]
+- [[framings/sparks-of-motivation]]
+
+## Layers (the functional stack)
+
+- [[layers/personal-cognition]] — a notebook that augments your intelligence
+- [[layers/team-cognition]] — collective brain for a company
+- [[layers/collective-cognition]] — Humanity 3.0
+
+## Pitches (the same idea, dressed for the room)
+
+- [[pitches/elevator-summary]] — 30 seconds
+- [[pitches/best-pitch]] — Jacob's own "best pitch" (flagged `#explainingideaflow #best #pitch`)
+- [[pitches/for-investors]] — VC framing
+- [[pitches/for-users]] — user framing
+- [[pitches/for-builders]] — builder / collaborator framing
+
+## Meta
+
+- [[meta/design-history]] — how this wiki was scaffolded, and why
+- [[canonical-terms]] — glossary, to reduce metaphor sprawl
+- [[use-cases]] — concrete examples
+- [[open-questions]] — unresolved tensions
+
+## Raw
+
+- [raw/slack-explainingideaflow-2022-2026.md](raw/slack-explainingideaflow-2022-2026.md) — lightly cleaned Slack excerpts carrying the `#explainingideaflow` tag
+
+## Cross-links to Vision Convo
+
+This wiki's framings and pitches cite vision-convo pages extensively. Landmark entries:
+
+- [IdeaFlow (project page)](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/ideaflow)
+- [Collective Intelligence](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/collective-intelligence)
+- [Sparks of Motivation](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/sparks-of-motivation)
+- [Vision for the World](https://wikihub.md/@jacobcole/vision-convo/wiki/themes/vision-for-the-world)
+- [LLM Wiki as Medium](https://wikihub.md/@jacobcole/vision-convo/wiki/themes/llm-wiki-as-medium)
+- [Doug Engelbart](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/doug-engelbart)
+- [Jack Park](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/jack-park)
+
+---
+
+Schema: [AGENTS.md](AGENTS.md) · Ingestion log: [log.md](log.md) · All pages CC0.
new file mode 100644
index 0000000..1ddb7ef
@@ -0,0 +1,16 @@
+---
+title: Ingestion Log
+visibility: public
+---
+
+# Ingestion Log
+
+Append-only. Newest entries at the top.
+
+## 2026-04-20 — initial scaffold
+
+- **Sources ingested:** `#explainingideaflow` tag corpus from `~/code/ideaflow-slack-wiki/work/window-*` (private local archive). Extracted ~57 Jacob messages + supporting co-worker quotes spanning 2022-05-11 → 2025-10-22.
+- **Pages created:** index, AGENTS, log, 10 framings, 3 layers, 5 pitches, 4 meta/concept (north-star-thesis, chronology, canonical-terms, system-map), raw excerpts file, meta/design-history.
+- **Sister wiki cross-links:** vision-convo (62 pages).
+- **Design decisions:** see [[meta/design-history]] and beads ticket `wikihub-4i3b`.
+- **Deferred:** notestream/Thoughtstream ingestion (Hasura-backed). Blog posts on `ideaflow.blog`. Talk transcripts.
new file mode 100644
index 0000000..15c1302
@@ -0,0 +1,244 @@
+---
+title: Slack — #explainingideaflow (2022-2026)
+visibility: public
+---
+
+# `#explainingideaflow` — Slack excerpts, 2022 → Feb 2026
+
+> Lightly cleaned excerpts from IdeaFlow's Slack workspace (dataset stopped Feb 2026). Excerpts are Jacob's own messages unless otherwise attributed. Reactions and side chatter trimmed. Links preserved where load-bearing. Processed from the private local archive at `~/code/ideaflow-slack-wiki/` — not everything in that archive is reproduced here; only messages carrying `#explainingideaflow` or its variants, plus the immediately surrounding context when needed.
+>
+> Naming variants observed: `#explainingideaflow` (57), `#explaining-ideaflow` (2), `#explainingideaflow-` (1), and typo-variants.
+
+---
+
+## 2022
+
+### 2022-05-11 — Rise of Superman
+Source book: *The Rise of Superman: Decoding the Science of Ultimate Human Performance* (Steven Kotler) and the *Flow in Sports* book. Jacob tagged these as foundational.
+
+> `#explainingIdeaflow`
+> Ideaflow as a tool for **capturing the fleeting beauty of the world** — `#missionStatement`.
+
+---
+
+## 2023
+
+### 2023 — capturing fleeting beauty
+Jacob, `#design`:
+> Ideaflow as a tool for gathering and focusing **sparks of motivation** `#explainingideaflow-` — critical when not abundant `#best`
+> — gestalt capture system → gestalt processing system for society
+
+> See http://gestaltexplanation.jacobcole.net/ for background.
+
+### 2023 — the idea-capture app
+Jacob, `#general`:
+> the idea capture app `#Marketing #Explainingideaflow` **never lose another idea again**
+
+### 2023 — TFT as web surfboard
+Jacob (`#ts-user-feedback`): `#write tft as web surfboard @blog #explainingIdeaflow`.
+
+### 2023 — transcription aware of the lexicon
+Jacob:
+> in transcription, concatenate multiword hashtags, iff they are in the lexicon `#Tweak` — e.g. if `#explainingIdeaflow` exists and you said "hashtag explaining ideaflow" it will not just do `# #explaining ideaflow` but greedily consume til `#explainingIdeaflow`
+
+---
+
+## 2024
+
+### 2024-01-XX — Laurel Touby conversation (Gestalts, demand aggregation)
+Jacob, after a conversation with investor Laurel Touby:
+> `#Conversation with Laurel Touby` — Gestalts, demand aggregation, and how can ai help you leverage your resources (e.g. that you've taken notes on) to advance your goals in life. https://www.loom.com/share/c06a0d28a079497ebca7145cc43fbe41 `#ExplainingIdeaflow #Good`
+
+Bullet unpacking of the conversation (compressed):
+- There's a reason people take notes — goals, health, travel, love, learning, self-growth (~20 categories).
+- AI can help get these done with less friction.
+- If you're fundraising, AI could suggest the top 3 people in your network to reach out to — your own knowledge base × the world knowledge graph.
+- *"Listen to conversation … take notes … put things where they needed to go. See patterns in what I'm looking for. See them across other users."*
+- Like having an assistant with me all of the time.
+
+Related projects cited: Braintree / Pearltrees (`#mindmappingSoftware #relatedproject`). Demo: https://develop.ideaflow.app/shared/48dROzHrSd
+
+### 2024-01-27 — `#explainingIdeaflow` graph
+Jacob, to Cody Hergenroeder:
+> `#explainingIdeaflow` @Cody Hergenroeder https://ideapad.io/explaining-ideaflow/graph?snapshot=explaining-ideaflow-graph
+
+### 2024-01-28 — Suggestion Board for the World
+Jacob, `#SuggestionBoardForTheWorld`:
+> `#explainingIdeaflow #SuggestionBoardForTheWorld` https://www.loom.com/share/98a8f09fe732451fb602678f8802bd3a conversation with Agu
+
+### 2024-01-29 — Laurel Touby Rough (feature list)
+`#Feature #good #ExplainingIdeaflow #vision`
+- auto tag notes
+- Apple Notes import
+- and all the proper names
+- doing things with the data — automating things
+- suggesting events, hints, reminders, people you haven't been in touch with
+- "Know you're looking for a job similar to xyz where you used to work"
+- "Potential investors for fund founders"
+- "Meeting founder tech investor tag"
+- "Want to know what your goals in life are"
+- "Share across people — anonymize; others interested in travel have shared these notes about these places"
+
+### 2024-02-XX — O(1) capture and recall
+Phil asked what "O(1)" meant for the augmented output. Jacob: "augmented reading/consuming of information." Phil: "complexity estimate for users to interact with information they've put in Ideaflow, right? More conceptual than mathematical?" Jacob: "yeah. everyone would prefer to read well-organized entanglement than a bunch of messy notes."
+
+Cody:
+> "O(1) capture and recall is how I've been phrasing it to myself on the product level."
+
+(Relates to the earlier Joe Henke framing from this thread: *"First build a medium for thought, then there are things you can build in world with it."*)
+
+> "It shows how Ideaflow is a whole frame to represent and track and augment all collective human intellectual effort. Also, would love to expand more on how I see our mid term vision a lot as Joe put it this morning. First build a medium for thought, then there are things you can build in world with it `#explainingideaflow`"
+
+### 2024-02-15 — end-to-end support system for the creative process
+Jacob, `#explainingideaflow`:
+> "Reducing intelligence to generation is like reducing software to print() statements." This is what http://Ideaflow.io is building: an end-to-end support system for the creative process. http://gestaltexplanation.jacobcole.net @IdeaFlowGraphs
+
+### 2024-02-27 — high-quality thinking on the Internet
+Jacob:
+> How can we create a space for **high-quality thinking and writing on the Internet**? `#explainingideaflow`
+
+Joe Henke (response): separating the raw "notes" graph (bullets) from the "semantic" graph (garden). Sometimes you want the exact prose (pathos); sometimes you want to interact with content as directly as possible (logos).
+
+### 2024-02-27 — backlinks mental model
+Jacob:
+> `#explainingideaflow` — an insight about why backlinks shouldn't be subordinated in our new product from Taylor, derived from graph view https://www.loom.com/share/90978ee76192423d85cf7e55fd049618
+
+Taylor Mitchell: "In most outliners, when you 'expand' a node, you're showing its children. This is different from graph database explorers, where when you 'expand' a node, you're showing all related nodes, not just children. In the new product, that's the behaviour we're introducing …"
+
+### 2024-03-XX — ultimate CEO dashboard / collective brain for a company
+Jacob:
+> We could call our app the **ultimate CEO dashboard** — and collective brain for a company.
+
+### 2024-03-XX — Team Humanity
+Jacob — user story:
+> We are just building an übertool/dashboard/collaboration platform to house, track, and support all the thinking that happens online in really large, multi-tiered organizations like Alphabet or Verizon … One such organization happens to be the entire planet earth's, ie **Team Humanity**. Which, whether we are conscious of it, or not, is a team/corporation. But right now, since we don't think of it as such, and we don't use IdeaFlow tools, it's not a very efficiently run organization. But if we have this tool, team humanity can move more efficiently towards its OKRs. Like getting everyone's needs met, and working together to discover/cluster everyone's needs.
+
+### 2024-03-22 — best pitch
+Jacob, `#explainingideaflow #best #pitch`:
+> Now, what I'm actually building is a **massive-scale collective cognition system for humanity**. But one of the pieces it takes is a personal knowledge management system. You can tell it anything and it organizes it into a structure that makes sense and you can find it again. I'm running a seed-based startup in the Bay Area and we recently launched and I'd love to show you guys. It takes just a second.
+>
+> *(What is it?)* It's called… I don't really understand. Well, it's like Obsidian, but AI-powered and better ergonomics. Like, Obsidian is very hackery and complicated. Imagine Obsidian, but optimized for quickly capturing new thoughts and with a much simpler organizational paradigm, but also power.
+
+Same thread:
+> `graph database for your brain`
+
+And later:
+> **Tool to discover the path of wisdom** and empower people to act on it? Build a **neocortex for the global mind/brain**; for the Internet? — this covers suggestion board — supporting you in acting on your goals — organizer of information that comes into your life — system to track and coordinate all human scientific and practical endeavor — human activity — **align the world to the path of wisdom** `#explainingideaflow`
+
+### 2024-03-28 — the actual bicycle for the mind
+Jacob:
+> `#explainingIdeaflow` The actual **bicycle for the mind** — https://www.loom.com/share/65b35692499e4bfcbcf718c23a7851a5
+
+### 2024-03-28 — Contacts + conversation notes
+Jacob, `#userstory #explainingIdeaflow #pitching`: Contacts populated by taking notes on conversations. Draft 1 https://www.loom.com/share/1ad59d3260a541ecb4b4c807c5dca075 · Clean version https://www.loom.com/share/37b4d5887bd14987a374e7060a5871d5 · cc Ridhi Kantelal.
+
+### 2024-03-XX — quick capture, quick sort
+Jacob:
+> `#explainingideaflow` Quick capture, quick sort. @Cody mock jack's UX idea for folders on mobile (can do with tags).
+
+### 2024-04-XX — split view (external vs personal notebooks)
+Jacob:
+> Two different user stories: browsing the external web, and browsing your own thoughts/commentary on it. But they are fundamentally the same kind of structure. There's a reason the memex had two screens. I wonder if we would be less confused about the global vs personal stuff if we baked in a **split view** explicitly into our markup. Left side = browsing external stuff, right side = your personal notebooks.
+>
+> `#explainingideaflow`
+
+### 2024-05-23 — an idea flow for every community
+Jacob:
+> "**create an idea flow for every community**" `#explainingideaflow`. Have a chat feature just for messaging and/or a Slack bot. Have a superconnector.network-style chat interface for each community and globally.
+
+### 2024-XX — conversation-notes demo
+Jacob:
+> I was just helping a guy at a Founder meetup import all of his conversation notes from Sublime Text into old IdeaFlow. And I realize that there's really no tool where you can take conversation notes naturally on one side, and it builds a knowledge base for you on the other side that's awesome. `#mewUseCase #explainingIdeaflow`
+
+### 2024-10 — Open source knowledge graphs
+Jacob:
+> `#explainingIdeaflow` — starting the **open source movement for knowledge graphs**, e.g. Open Supply Chains.
+
+### 2024-10-XX — Alex Kayyal quote (Lightspeed)
+Jacob, citing Alex Kayyal, Lightspeed Ventures (former MD Salesforce Ventures):
+> "What I think you're doing is really cool. Sort of what **Google did for the Internet but for information not on the web but in people's minds**." `#~AlexKayyal #supportingQuote #ExplainingIdeaFlow`
+
+### 2024-12 — debate outlines
+Jacob, `#explainingIdeaflow #debateoutlines`: "time sensitive use of Mew to make a debate outline" — https://www.loom.com/share/ad19fdd406964818bdbbcdc3a0805a27
+
+---
+
+## 2025
+
+### 2025-04-23 — Saanya Ojha tailwind tweet
+Jacob, `#explainingIdeaflow #pitching #vc #tailwind`:
+> On this fine Friday, allow this VC to pitch you a business idea born out of personal frustration. I'm a dedicated DAU (only because we don't yet track Hourly Active Users), and yet these models barely know me. At this point, I feel like a traveling salesman from the 1800s, lugging a little suitcase of context from one AI to the next …
+
+(Quoted from Saanya Ojha's LinkedIn post; Jacob framed it as a VC themselves articulating IdeaFlow's thesis.)
+
+### 2025-04-XX — ideaflow.blog
+Eden Chan:
+> Soft launching ideaflow blog! Primarily for managing all the content for `#explaining-ideaflow` and the expansion pack of projects / past writing (eg. content from jacob's google docs) to potential collaborators. https://ideaflow.blog
+
+### 2025-05 — Charlie Munger seamless trust (Eden)
+Eden Chan, quoting Munger, tagged `#explaining-ideaflow`:
+> "A seamless non-bureaucratic web of deserved trust" as "the highest form that Civilization can reach." Characterized by "totally reliable people correctly trusting one another." This contrasts sharply with bureaucratic systems, which carry "so much dysfunction and evil." Such a web yields "enormous efficiencies" … The Japanese manufacturing success is cited as an example. https://mew-edge.ideaflow.app/charlie-munger-archive
+
+### 2025-05 — notebooklm insights pipe
+Eden:
+> Pro tip: you can dump it into this explaining-ideaflow node and then copy-paste everything as text into NotebookLM to generate even more insights — https://mew-edge.ideaflow.app/g/all/24d3f0ba/ed8473dd
+
+### 2025-06 — user-story self-reference
+Jacob, `#ExplainingIdeaFlow`:
+> Also, I often say, man, I'm writing all this stuff down and I hope someday AI can process it all and make sense of it and tag it and surface all my tags and stuff because on this thread I'm going to say `#usecase`. Tons of my friends have said this. We are actually building that software!
+
+(In the same thread, Jacob: "Everyone uses ProseMirror. We could offer **GraphMirror**.")
+
+Extended vision in the same thread:
+> All my Slack messages that I send should end up in a non-privileged place in my thought stream, ultimately — but everything is in a stream. It all gets a timestamp, but it should be hidden from my main timeline by default. Everything I ever write or produce should end up in my thought stream.
+
+### 2025-06 — mew hosting every website's backend
+Jacob:
+> Some vision for mew as a centralized organized database that hosts the backend of every website. https://www.loom.com/share/84d4c988669d40a0a5ff5a467302ac31 — `#ExplainingIdeaFlow #bizdev`
+
+### 2025-06 — #memex #ai
+Jacob:
+> `#memex #ai` — https://www.livescience.com/technology/computing/this-obscure-80-year-old-machine-might-be-the-key-to-unlocking-the-full-potential-of-ai-today `#cool #explainingideaflow`
+
+### 2025-07 — Semantic Web why-now
+Jacob, `#ExplainingIdeaFlow #whyNow #SemanticWeb`: linked Kurt Cagle sharing Kingsley Uyi Idehen's Semantic Web essay on LinkedIn. The underlying why-now: LLMs finally close the "markup burden" gap that killed the 2000s Semantic Web.
+
+### 2025-10 — notebook for our minds
+Jacob:
+> One key to this whole project is that we built a really cool frictionless text editor kind of like Obsidian that's actually good for taking meeting notes (almost! if we give it a little bit of love). But it also serves as a legitimate place to hold structured data on people etc, and bidirectionally links into systems of record on them, and hide complexity. It's a **notebook for our minds**. `#explainingideaflow`
+
+### 2025-10 — hypergraph store for LLMs
+Jacob, `#paperidea #explainingideaflow`:
+> It helps language models — https://x.com/rohanpaul_ai/status/1976409349476995158 — do this equipping them with a hypergraph store.
+
+### 2025-10-21 — meeting-notes first time in history
+Jacob:
+> Tejas and I just took the first well-organized meeting notes that were ever taken in human history because there was never a structure that could properly well-organize them before. Including connections added and citing exactly where relations were created from. `#explainingideaflow #meeting #best` — https://www.loom.com/share/7dcd477bb5954e0b894bd16781e01f16
+
+### 2025-10 — the God data structure
+Jacob:
+> `#Quote #explainingideaflow` — GPT-5 with no prompting just produced this relationship map as well. It just did exactly what we're saying here. It did all the things we're saying … without structured data output, you know? But it has it implicit in the answers. It just had no medium — medium where it could express all the things it notes. Hmm. That's, uh, that's a good line.
+>
+> Ultimately, we're creating **the God data structure**. Our God data structure should be able to contain everything in the world. (Eg. Google Maps paths and regions, category theory etc.) `#RearchitectingTheWeb` — building the **Gopher backbone**.
+
+### 2025-XX — Slack-bot as idea harvester
+Jacob, `#explainingIdeaflow`:
+> Our Slack bot listens to conversations and builds a database of ideas from across the company, and suggests connections to others who have related ideas. It also can harvest the unstructured Slack information as a knowledge base.
+
+Follow-ups in the same thread:
+- Public curated lists of information beneficial to the world.
+- Export all of your networks (LinkedIn, texts, contacts, email) and search it all from one place; form an alliance among friends to query the best intro path to anyone.
+
+### 2025-XX — xkcd 3175 joke
+Jacob, `#explainingIdeaflow`: https://xkcd.com/3175/ `#lol`
+
+### 2026 (early) — continuing cadence
+The tag remained active through Feb 2026 across `#biz`, `#random`, `#codys-corner`, `#learning-everyday`, `#mew-product`. See the private local archive at `~/code/ideaflow-slack-wiki/` for the long tail.
+
+---
+
+## Notes on what's *not* in this file
+
+- **Customer / sales thread content** tagged `#explainingideaflow` — intentionally kept in the private archive. If any public usage is needed, paraphrase rather than quote.
+- **Early years (2015-2021):** the `#explainingideaflow` tag was less used; the relevant framings from that period live in Jacob's Google Docs and pre-Mew artifacts (e.g., http://gestaltexplanation.jacobcole.net/) rather than Slack.
+- **Notestream / Thoughtstream captures:** not yet ingested. See the deferred item in [[../log|log]].
new file mode 100644
index 0000000..46bfb5d
@@ -0,0 +1,65 @@
+---
+title: Canonical Terms — glossary
+type: concept
+visibility: public
+related:
+ - wiki/north-star-thesis.md
+ - wiki/chronology.md
+---
+
+# Canonical Terms
+
+A working glossary. The point is to reduce metaphor sprawl by *acknowledging* that different words mean different things even when they gesture at the same region.
+
+## Object-level
+
+- **IdeaFlow** — the company and the product family. Public-facing name.
+- **Mew / Mew Lite / Mew Edge** — internal/experimental product names for the graph product.
+- **Thoughtstream** — the voice-first capture product (develop.ideaflow.app; stage-api.ideaflow.app).
+- **Entanglement** — earlier-generation prototype (2023-2024) that informed the graph UX.
+- **Gopher backbone / GraphMirror** — speculative names for the graph-editor primitive, framed as a cross-app substrate.
+
+## Data-model terms
+
+- **Node** — the atom. Can be text, a tag, a person, a place, a page.
+- **Relation / edge** — a typed connection between nodes.
+- **Graph** — the union.
+- **Zone / active zone** — a node with sublist-inheritance semantics; stands for "context you've focused on right now."
+- **Gestalt** — a cluster of nodes that coheres into a single recognizable pattern. Predates Mew; see http://gestaltexplanation.jacobcole.net/.
+- **Spark (of motivation)** — the atomic unit of intent. See [[framings/sparks-of-motivation]].
+- **God data structure** — Jacob's maximalist framing for the graph: one structure capable of representing everything in the world, including Google Maps paths, category theory, etc.
+
+## Cognition terms
+
+- **Capture** — getting a thought out of your head and into the system.
+- **Recall** — getting a thought back into working memory when you need it.
+- **O(1) capture and recall** — Cody's shorthand for the product-level requirement: both operations should feel costless.
+- **Cluster** — finding the attractor under a bunch of related sparks.
+- **Augment** — the Engelbart word. Substrate + human > substrate alone or human alone.
+- **Suggestion / surfacing** — the substrate proactively showing you something relevant you'd otherwise miss.
+
+## Scale terms
+
+- **Personal cognition** — individual-layer applications. See [[layers/personal-cognition]].
+- **Team cognition** — organization-layer. See [[layers/team-cognition]].
+- **Collective cognition / Humanity 3.0** — civilization layer. See [[layers/collective-cognition]].
+- **Team Humanity** — the conceit that humanity is one multi-tiered organization with OKRs; IdeaFlow is the tool that makes it legible. See [[framings/team-humanity]].
+- **World Quest** — the World-of-Warcraft framing for civilization-scale coordination; inherited from Jacob's mentor Jack Park. See [vision-convo → jack-park](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/jack-park).
+
+## Vocabulary inherited from elsewhere
+
+- **Bicycle for the mind** — Steve Jobs' Engelbart-style frame, claimed verbatim.
+- **Medium for thought** — Joe Henke's framing (January 2024); widely adopted as house vocabulary.
+- **Memex** — Vannevar Bush (1945). Repeatedly invoked.
+- **Open Supply Chains** — one example application of the "open-source KGs" movement. See [[framings/open-source-knowledge-graphs]].
+
+## Deprecated / retired
+
+- **"The idea-capture app — never lose another idea again"** (2023 marketing) — superseded by cognition-layer framing.
+- **Mew** (product name) — used internally; the public name is now IdeaFlow.
+
+## Rules for adding to this glossary
+
+1. A term enters here when it appears **three or more times** in the `#explainingideaflow` corpus, or when it's load-bearing in a pitch.
+2. Each entry gets: a one-liner definition, the origin/coiner when known, and a pointer to the framing page if it has one.
+3. Terms that retire move to "Deprecated / retired" rather than being deleted — past essays still reference them.
new file mode 100644
index 0000000..9d28690
@@ -0,0 +1,100 @@
+---
+title: Chronology — how the vision evolved, 2022→2026
+type: concept
+visibility: public
+related:
+ - wiki/north-star-thesis.md
+ - raw/slack-explainingideaflow-2022-2026.md
+---
+
+# Chronology
+
+> "The vision hasn't necessarily changed longitudinally, but it has been **refined** and has **evolved and matured**, and more **forks have been discovered**, with more **details and realizations**."
+> — Jacob, 2026-04-20, scoping this wiki
+
+That framing is the backbone of this page. The north star has been stable. The vocabulary, the wedges, the audiences, and the *visible* surface have compounded.
+
+## 2022 — the mission statement era
+
+- **"Capturing the fleeting beauty of the world."** Jacob's earliest `#missionStatement / #explainingIdeaflow` framing, posted alongside *Rise of Superman* and *Flow in Sports* as source material.
+- Undercurrent: sparks of motivation as treasures; the app as a tool for **gathering and focusing** them.
+
+This is the seed. The 2026 civilization-scale framing is a mature plant; the seed was already there.
+
+## 2023 — the marketing-tagline era
+
+- **"The idea-capture app — never lose another idea again."** The consumer-facing framing.
+- **"Gestalt capture system → gestalt processing system for society."** The ambition is already plural — personal capture is instrumental to collective processing.
+- The transcription-aware-of-the-lexicon bug ticket (*"concatenate multiword hashtags, iff they are in the lexicon"*) is itself a micro-expression of the vision: structure sneaks into capture.
+
+## Early 2024 — product-shape emerges
+
+- **"First build a medium for thought, then there are things you can build in world with it."** (Joe Henke's phrasing, January 2024 — became house vocabulary.)
+- **O(1) capture and recall.** (Cody Hergenroeder's product-level shorthand, February 2024.)
+- **Backlinks shouldn't be subordinated.** (Taylor Mitchell's tree-vs-graph argument, February 2024 — became doctrine.)
+- **End-to-end support system for the creative process.** February 2024, responding to the "intelligence = generation" reduction.
+- **Suggestion Board for the World.** January 2024, first major upward-scale framing.
+
+## Mid 2024 — scale reveals itself
+
+- **Graph database for your brain.** March 2024, during the "best pitch" drafting session. Instantly iconic; survived verbatim through to 2026.
+- **Neocortex for the global mind/brain.** March 2024. Personal-scale's mirror image at the civilizational layer.
+- **Tool to discover the path of wisdom.** March 2024. The moral framing.
+- **Massive-scale collective cognition system for humanity.** March 2024. The [[north-star-thesis|north-star]] line — tagged `#best #pitch` by Jacob himself.
+- **The actual bicycle for the mind.** March 2024. The Jobs/Engelbart inheritance, claimed.
+- **Quick capture, quick sort.** March 2024. The UX-level distillation.
+- **Create an idea flow for every community.** May 2024. The "community Slack bot" vision takes shape.
+
+## Late 2024 — external validation
+
+- **Alex Kayyal (Lightspeed):** "Sort of what Google did for the Internet but for information not on the web but in people's minds." October 2024. First time an investor articulated the thesis back in public-quotable form.
+- **Open source movement for knowledge graphs.** October 2024. The ideological stance crystallizes.
+- **Debate outlines:** the "use Mew as a civic-infrastructure layer" experiment.
+
+## 2025 — platform ambitions
+
+- **ideaflow.blog.** April 2025 (Eden). Public pipeline for `#explaining-ideaflow` content + related past writing.
+- **Munger seamless-trust quote** (Eden, May 2025). Cross-linked into the vision — Berkshire as proof that the trust-web is civilizationally higher-performing than bureaucracy. IdeaFlow's graph is the trust-web's substrate.
+- **Notebook for our minds.** October 2025. The aesthetic compression.
+- **Meeting notes first time in human history.** October 2025 (after Jacob+Tejas demo). Frontier claim about *what kind of object* a well-organized meeting record is.
+- **The God data structure / Gopher backbone / GraphMirror.** October 2025. Maximalist framing — the substrate wants to contain everything.
+- **Slack bot as idea harvester / internal-Twitter surfacing / innovation-management demo.** October-November 2025. Team-cognition layer productized.
+
+## Early 2026 — where we are now
+
+- **Hypergraph stores for LLMs** (October 2025 continuing). The observation that LLMs themselves want this substrate.
+- **`#ExplainingIdeaFlow #whyNow #SemanticWeb`.** The why-now is codified: LLMs close the markup gap.
+- **Vision Convo wiki** (April 2026). Karpathy LLM-wiki pattern applied to Jacob's full worldview recording. Sister wiki to this one.
+- **This wiki** (April 2026). The longitudinal archive proper.
+
+## Refinements (not changes)
+
+The vision is the same. What has matured:
+
+| Dimension | 2022 | 2026 |
+|-----------|------|------|
+| Name for the object | "the idea-capture app" | "massive-scale collective cognition system for humanity" |
+| Core metaphor | sparks of motivation, fleeting beauty | same, plus graph, neocortex, God data structure |
+| Scale of ambition | personal KM | personal ↔ team ↔ humanity substrate |
+| Why-now | implicit | **LLMs close the markup burden gap** |
+| Wedge | consumer KM app | enterprise team-cognition |
+| Open/closed stance | unstated | explicit open-source KG movement |
+| Co-authors of vocabulary | Jacob | Jacob, Joe (medium for thought), Cody (O(1)), Taylor (graphs over trees), Eden (Munger, blog pipeline), Tejas (meeting notes) |
+| Place in history | "mission statement" | **continuation of Engelbart/Berners-Lee lineage** |
+
+## Forks discovered along the way
+
+- **GraphMirror** as a ProseMirror-for-graphs offering. (A toolmaker wedge.)
+- **Mew hosts every website's backend.** (A Firebase-like wedge.)
+- **Public curated lists beneficial to the world.** (A civic-infrastructure wedge.)
+- **Alliance graph across friends' networks.** (A social-capital wedge.)
+- **Slack → IdeaFlow → internal-Twitter surfacing.** (An internal-developer-feed wedge.)
+
+Not all forks will be pursued. The point of a forks-discovered frame is: the substrate is general enough that its application surface keeps expanding *without* the substrate itself changing.
+
+## Related
+
+- [[north-star-thesis]] — the stable spine
+- [[canonical-terms]] — the vocabulary that accreted
+- [[framings]] — each major metaphor as its own page with its `first-used` date
+- `raw/slack-explainingideaflow-2022-2026.md` — the underlying evidence
new file mode 100644
index 0000000..8f876c7
@@ -0,0 +1,58 @@
+---
+title: Framing — "the actual bicycle for the mind"
+type: framing
+visibility: public
+first-used: 2024-03-28
+audience: all
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2024-03-28
+related:
+ - wiki/framings/medium-for-thought.md
+ - wiki/framings/graph-database-for-your-brain.md
+---
+
+# "the actual bicycle for the mind"
+
+## The line
+
+Jacob, 2024-03-28:
+
+> "`#explainingIdeaflow` **The actual bicycle for the mind** — https://www.loom.com/share/65b35692499e4bfcbcf718c23a7851a5"
+
+## The lineage
+
+Steve Jobs' famous framing: the computer as a bicycle for the mind. Jobs was quoting Engelbart's augmentation thesis, dressed for consumer consumption.
+
+Jacob's word is **actual** — implying that the personal computer, as it turned out, *didn't* deliver on that promise. It delivered email, spreadsheets, and web browsing. It did not deliver a substrate that makes thinking cheaper and better.
+
+The claim: IdeaFlow *does*. Not because the phrase is ownable but because Jacob is claiming the lineage directly — Engelbart → Jobs (partially) → IdeaFlow (fully).
+
+## Why it works
+
+1. **Instantly legible.** Anyone who's heard Jobs's line knows what this means.
+2. **Claims a lineage.** Engelbart's augmentation project. A big room to stand in.
+3. **Humble about scope.** A bicycle isn't a spaceship. It's the right-sized vehicle for the right-sized task. The claim is proportionate to the ambition.
+
+## Where it sits
+
+- **Layer:** personal cognition, primarily. Extends upward by analogy.
+- **Audience:** all, across registers.
+- **Register:** works both casual and formal.
+
+## What it pairs with
+
+- [[medium-for-thought]] — the infrastructural version of the same claim.
+- [[graph-database-for-your-brain]] — the data-model of the bicycle.
+- [[notebook-for-our-minds]] — the aesthetic of the bicycle.
+
+## What's *different* from Jobs's framing
+
+Jobs: the computer is a bicycle for *any kind of mind-work*, not specifically thinking.
+
+Jacob: the bicycle is for **thinking as cognition**, not information-handling. The emphasis on *actual* is the correction.
+
+## Related
+
+- [[../north-star-thesis]]
+- [[../chronology]] — where this framing slots in the March 2024 burst
+- [Doug Engelbart (vision-convo)](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/doug-engelbart)
new file mode 100644
index 0000000..c169b5d
@@ -0,0 +1,50 @@
+---
+title: Framing — "gestalt capture system → gestalt processing system for society"
+type: framing
+visibility: public
+first-used: 2023
+audience: all
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2023
+related:
+ - wiki/framings/sparks-of-motivation.md
+ - wiki/system-map.md
+---
+
+# "gestalt capture system → gestalt processing system for society"
+
+## The line
+
+Jacob, 2023 (`#design`):
+
+> "Ideaflow as a tool for gathering and focusing sparks of motivation `#explainingideaflow-` — critical when not abundant `#best`
+> — **gestalt capture system → gestalt processing system for society**"
+
+With a pointer back to http://gestaltexplanation.jacobcole.net/ — a pre-Mew artifact spelling out the gestalt theory.
+
+## Why it works
+
+1. **Names the two-stage structure directly.** Capture isn't the goal; processing is the goal; capture is instrumental.
+2. **Foreshadows the three-scale stack** ([[../system-map]]). *"for society"* is the third-scale claim made in 2023, three years before [[../framings/team-humanity]] crystallizes.
+3. **"Gestalt"** is the precise word — a pattern that coheres, larger than the sum of its parts, meaningful *as a whole*. Sparks become gestalts; gestalts are what society needs to see.
+
+## Where it sits
+
+- **Layer:** crosses all three (the arrow in the phrase *is* the system map).
+- **Audience:** philosophers, product people.
+- **Register:** mission-statement-y.
+
+## What it pairs with
+
+- [[sparks-of-motivation]] — the atomic unit that gets captured.
+- [[medium-for-thought]] — the infrastructural version of the same claim.
+- [[../system-map]] — the structural version.
+
+## Lineage
+
+Gestalt is a term from early-20th-century psychology (Wertheimer, Köhler). Jacob had been writing about *gestalts* as the unit of coherent pattern since at least the gestalt-explanation essay (pre-2023). The 2023 framing ties the product's purpose directly to that long-running thread.
+
+## Related
+
+- [[sparks-of-motivation]]
+- [[../canonical-terms]] (Data-model terms, Cognition terms)
new file mode 100644
index 0000000..46ea344
@@ -0,0 +1,54 @@
+---
+title: Framing — "the God data structure"
+type: framing
+visibility: public
+first-used: 2025-10-XX
+audience: builders
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2025-10
+related:
+ - wiki/framings/medium-for-thought.md
+ - wiki/framings/open-source-knowledge-graphs.md
+ - wiki/canonical-terms.md
+---
+
+# "the God data structure"
+
+## The line
+
+Jacob, October 2025:
+
+> "Ultimately, we're creating **the God data structure**. Our God data structure should be able to contain everything in the world. (Eg. Google Maps paths and regions, category theory etc.) `#RearchitectingTheWeb` — building the **Gopher backbone**."
+
+## Why it works (when it works)
+
+1. **Maximalist by design.** IdeaFlow's data model wants to be expressive enough to represent spatial regions, mathematical categories, social relationships, and everyday text. The phrase telegraphs the ambition.
+2. **Developer-legible.** "God object" is a known (anti-)pattern in OO. The flip of the anti-pattern into a feature is intentional — *what's wrong in code is right in data model*, at the right scope.
+3. **Paired with GraphMirror / Gopher backbone.** The "substrate-of-substrates" framing. ProseMirror is a text editor primitive; GraphMirror would be the graph editor primitive.
+
+## Why it's risky
+
+- Reads cult-adjacent out of context.
+- Overpromises if the actual data model hasn't demonstrated that level of expressiveness yet.
+- Flagged in [[../open-questions]] (item 6) as a *"trap."*
+
+## Where it sits
+
+- **Layer:** substrate (all layers sit on it).
+- **Audience:** builders, systems-thinkers, database people.
+- **Register:** in-group. Not recommended in public pitches without editorial framing.
+
+## What it pairs with
+
+- [[medium-for-thought]] — the less risky version of the same ambition.
+- [[open-source-knowledge-graphs]] — the political stance toward the God data structure (it's public infrastructure, not proprietary).
+- [[neocortex-for-the-global-brain]] — the same maximalism at the system level.
+
+## Editorial note
+
+This page keeps Jacob's phrasing verbatim per his decision (see [[../meta/design-history]]). It also flags the risks so future editors can decide when to invoke it and when to reach for a softer framing.
+
+## Related
+
+- [[../open-questions]] (item 6)
+- [[../canonical-terms]] (Data-model terms)
new file mode 100644
index 0000000..362eb44
@@ -0,0 +1,62 @@
+---
+title: Framing — "graph database for your brain"
+type: framing
+visibility: public
+first-used: 2024-03-22
+audience: users, investors
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2024-03-22
+related:
+ - wiki/framings/notebook-for-our-minds.md
+ - wiki/framings/neocortex-for-the-global-brain.md
+ - wiki/north-star-thesis.md
+---
+
+# "graph database for your brain"
+
+## The line
+
+Jacob, 2024-03-22 (`#explainingideaflow #best #pitch`, while drafting what he explicitly flagged as his best pitch):
+
+> "**graph database for your brain**"
+
+Six words. No hedging. It became house vocabulary and survived verbatim into 2026.
+
+## Why it works
+
+1. **Concrete.** "Graph database" means something specific — to developers, to investors, to anyone who's touched Neo4j or Roam.
+2. **Personal.** "Your brain" collapses the scale. The user is the point, not the product.
+3. **Ambitious but grounded.** It's not *"brain upload"* or *"consciousness 2.0."* It's a database. A *graph* database. For *your* brain.
+4. **Compressed.** The full [[../north-star-thesis|north-star thesis]] fits inside the six words if you already know IdeaFlow's angle.
+
+## Where it sits
+
+- **Layer:** personal cognition ([[../layers/personal-cognition]]).
+- **Audience:** users first, investors second.
+- **Register:** casual; works verbally.
+
+## What it pairs with
+
+- For the aesthetic side of the same metaphor: [[notebook-for-our-minds]].
+- For the scale-up: [[neocortex-for-the-global-brain]] (the same graph database, at civilization scale).
+- For the why-now: Semantic Web + LLMs (see [[open-source-knowledge-graphs]]).
+
+## What it rules out
+
+It *isn't* "better notes" — the phrase is "graph **database**," not "graph notebook." Structure is front and center.
+
+## Context from the original thread (March 2024)
+
+Jacob was in the middle of drafting what became his "best pitch" — rehearsing different framings out loud.
+
+> "Now, what I'm actually building is a massive-scale collective cognition system for humanity. But one of the pieces it takes is a personal knowledge management system. You can tell it anything and it organizes it into a structure that makes sense and you can find it again."
+> "What is it? It's called… I don't really understand. Well, it's like Obsidian, but AI-powered and better ergonomics."
+> "**graph database for your brain**"
+
+The phrase emerged as the compression of the whole pitch. It's not the first thing he tried; it's the one that landed.
+
+## Related
+
+- [[../north-star-thesis]]
+- [[../canonical-terms]] (see "Data-model terms")
+- [[../pitches/best-pitch]] (the full original thread)
new file mode 100644
index 0000000..64b829d
@@ -0,0 +1,56 @@
+---
+title: Framing — "medium for thought"
+type: framing
+visibility: public
+first-used: 2024-01-XX
+coiner: Joe Henke
+audience: builders, philosophers
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2024-02
+related:
+ - wiki/north-star-thesis.md
+ - wiki/framings/graph-database-for-your-brain.md
+---
+
+# "medium for thought"
+
+## The line
+
+Joe Henke, at IdeaFlow's morning standup, early 2024:
+
+> "First build a **medium for thought**, then there are things you can build in world with it."
+
+Jacob adopted it as house vocabulary immediately:
+
+> "It shows how Ideaflow is a whole frame to represent and track and augment all collective human intellectual effort. Also, would love to expand more on how I see our mid term vision a lot as Joe put it this morning. **First build a medium for thought, then there are things you can build in world with it.** `#explainingideaflow`"
+
+## Why it works
+
+1. It reframes IdeaFlow as **infrastructure** rather than **application.** Infrastructure patience is different from product patience.
+2. It acknowledges the two-stage nature: the medium comes first (unsexy), then the applications (sexy) bloom on it.
+3. It implicitly answers "why build a graph primitive, not a Notion-like app?" — because the primitive is the *point*.
+
+## Where it sits
+
+- **Layer:** spans all three. The medium is substrate; the applications are the layers.
+- **Audience:** builders and investors who think infrastructurally. Not a user-facing line.
+- **Register:** formal, considered.
+
+## What it pairs with
+
+- As the substrate whose *applications* include [[team-humanity]] and [[god-data-structure]].
+- As the *why* beneath [[graph-database-for-your-brain]] and [[notebook-for-our-minds]] (those are personal-layer instances of the medium).
+
+## What it rules out
+
+It *isn't* "build lots of features faster." It's: build the primitive right, and the features compose. Against MVP-culture, in a specific way.
+
+## Attribution
+
+This framing belongs to Joe Henke in house-vocabulary shorthand, though it's clearly downstream of Doug Engelbart and Vannevar Bush. Jacob kept Joe's phrasing rather than re-translating it.
+
+## Related
+
+- [[../north-star-thesis]]
+- [[../framings/bicycle-for-the-mind]] — same lineage, different metaphor
+- [Engelbart](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/doug-engelbart) on vision-convo
new file mode 100644
index 0000000..de71f5e
@@ -0,0 +1,51 @@
+---
+title: Framing — "neocortex for the global mind/brain"
+type: framing
+visibility: public
+first-used: 2024-03-22
+audience: all
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2024-03-22
+related:
+ - wiki/layers/collective-cognition.md
+ - wiki/framings/team-humanity.md
+ - wiki/framings/graph-database-for-your-brain.md
+---
+
+# "neocortex for the global mind/brain"
+
+## The line
+
+Jacob, March 2024 (`#explainingideaflow`):
+
+> "Tool to discover the path of wisdom and empower people to act on it? Build a **neocortex for the global mind/brain; for the Internet?** — this covers suggestion board — supporting you in acting on your goals — organizer of information that comes into your life — system to track and coordinate all human scientific and practical endeavor — human activity — align the world to the path of wisdom."
+
+## Why it works
+
+1. The neocortex is the **layer that plans, symbolizes, coordinates.** It doesn't replace the older brain; it augments it.
+2. "Global mind/brain" is an old idea (H.G. Wells's "World Brain," Teilhard's noosphere, the Engelbart lineage). Claiming the neocortex layer specifically gives IdeaFlow a *structural* role in the tradition, not just a gestural one.
+3. It pairs with [[graph-database-for-your-brain]] at the opposite end of the scale — the same metaphor (cortex-shaped graph) at the opposite scale (humanity).
+
+## Where it sits
+
+- **Layer:** collective cognition ([[../layers/collective-cognition]]).
+- **Audience:** all, with philosophical or missional framing.
+- **Register:** heavy. Use when the audience is ready for the civilization-scale claim.
+
+## What it pairs with
+
+- [[team-humanity]] — the same claim rephrased as organization-of-organizations.
+- [[god-data-structure]] — the data-model side of the same maximalism.
+- [[open-source-knowledge-graphs]] — the stance: this neocortex is a commons, not a proprietary platform.
+
+## Risks (flagged in [[../meta/design-history]])
+
+- Reads grandiose / cultish out of context.
+- Can blur product with worldview.
+- Mitigation: this page foregrounds the lineage (Wells, Teilhard, Engelbart) to show it's inherited, not invented.
+
+## Related
+
+- [[../layers/collective-cognition]]
+- [Vision for the World (vision-convo)](https://wikihub.md/@jacobcole/vision-convo/wiki/themes/vision-for-the-world)
+- [Doug Engelbart (vision-convo)](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/doug-engelbart)
new file mode 100644
index 0000000..69c2a8c
@@ -0,0 +1,55 @@
+---
+title: Framing — "a notebook for our minds"
+type: framing
+visibility: public
+first-used: 2025-10-XX
+audience: users
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2025-10
+related:
+ - wiki/framings/graph-database-for-your-brain.md
+ - wiki/layers/personal-cognition.md
+---
+
+# "a notebook for our minds"
+
+## The line
+
+Jacob, October 2025:
+
+> "One key to this whole project is that we built a really cool frictionless text editor kind of like Obsidian that's actually good for taking meeting notes (almost! if we give it a little bit of love). But it also serves as a legitimate place to hold structured data on people etc, and bidirectionally links into systems of record on them, and hide complexity. It's **a notebook for our minds**. `#explainingideaflow`"
+
+Follow-up in the same message:
+
+> "Because this is exactly what our brains do — they see text on a page and then they have tons of hidden associations around each name they see, each idea they see. This is actually representing what's going on in the world."
+
+And:
+
+> "This is really getting to be a notebook that augments your intelligence!"
+
+## Why it works
+
+1. **The aesthetic version** of [[graph-database-for-your-brain]]. Same object, softer register.
+2. **"Notebook" disarms.** It's not a "platform," not a "system," not a "product." It's the oldest technology of thought.
+3. **"For our minds" — plural.** Slight but important — the collective is latent in the personal framing.
+4. **Matches the actual UX.** IdeaFlow *is* a text editor with graph superpowers. The framing is honest.
+
+## Where it sits
+
+- **Layer:** personal cognition ([[../layers/personal-cognition]]). The aesthetic of that layer, more than its mechanism.
+- **Audience:** users, writers, researchers, people who own a Moleskine.
+- **Register:** warm.
+
+## What it pairs with
+
+- [[graph-database-for-your-brain]] — the technical version.
+- [[bicycle-for-the-mind]] — the lineage version.
+
+## What it rules out
+
+It's not a "second brain" app — Tiago Forte's framing is about *external storage* of thoughts. Notebook-for-our-minds is closer to Paul Ford's *"the pen is the part of the hand."* The artifact is a substrate for ongoing thinking, not a backup drive.
+
+## Related
+
+- [[../layers/personal-cognition]]
+- [Sparks of Motivation (vision-convo)](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/sparks-of-motivation)
new file mode 100644
index 0000000..38c999d
@@ -0,0 +1,57 @@
+---
+title: Framing — "the open source movement for knowledge graphs"
+type: framing
+visibility: public
+first-used: 2024-10-XX
+audience: all
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2024-10
+related:
+ - wiki/framings/god-data-structure.md
+ - wiki/framings/team-humanity.md
+ - wiki/layers/collective-cognition.md
+---
+
+# "the open source movement for knowledge graphs"
+
+## The line
+
+Jacob, October 2024 (`#explainingIdeaflow`):
+
+> "**Starting the open source movement for knowledge graphs**, e.g. Open Supply Chains."
+
+## Why it works
+
+1. **Takes a stance.** The long-arc collective-cognition substrate has to be open, federated, commons-first — or it's just Facebook for graphs.
+2. **Names the movement, not just the product.** Invites collaboration rather than competition.
+3. **Gives a concrete example.** Open Supply Chains — a domain with real adoption pain, real need for shared structure, real stakeholders.
+
+## Why it matters strategically
+
+The [[../what-it-is-not|distinction from Semantic Web]] is important: the 2000s Semantic Web failed on adoption (markup burden). The 2020s version has the LLM tailwind — but will fail again if it builds walled gardens instead of open substrates.
+
+Eden Chan's Munger-frame (2025) extends this: an open graph is also the **trust substrate** that Munger called the highest form of civilization. Openness isn't just an ethical preference; it's what makes the trust economics work.
+
+## Where it sits
+
+- **Layer:** substrate stance (applies to all layers).
+- **Audience:** all, with ideological framing.
+- **Register:** movement-language. Invokes open source traditions.
+
+## What it pairs with
+
+- [[god-data-structure]] — the maximal structural claim; this framing is the political stance on it.
+- [[team-humanity]] — the humanity-scale application; this is the license it runs under.
+- [[neocortex-for-the-global-brain]] — the anatomy; this is the governance.
+
+## Concrete scaffolding
+
+- **Open Supply Chains** — the named example in Jacob's tag, and a working case study for what open-KG governance might look like.
+- **Public curated lists** (2025) — small steps toward a public commons of structured knowledge.
+- **Alliance graphs across friends' networks** (2025) — user-level federation as a building block.
+
+## Related
+
+- [[../layers/collective-cognition]]
+- [[../use-cases]] → "Collective layer"
+- [[../canonical-terms]]
new file mode 100644
index 0000000..0263cec
@@ -0,0 +1,56 @@
+---
+title: Framing — sparks of motivation
+type: framing
+visibility: public
+first-used: 2022-05-XX
+audience: all
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2022
+related:
+ - wiki/framings/gestalt-capture-to-gestalt-processing.md
+ - wiki/layers/personal-cognition.md
+---
+
+# Sparks of Motivation
+
+## The line (compact)
+
+Jacob, 2022-2023:
+
+> "Ideaflow as a tool for **gathering and focusing sparks of motivation** — critical when not abundant."
+
+And (from vision-convo's [Sparks of Motivation concept](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/sparks-of-motivation)):
+
+> "I like putting my sparks into a knowledge graph. It's like, ooh, here's a spark here, here's a spark here, spark here. Okay, I can graph them. Cluster, cluster. This is power. It's a flame."
+
+## Why it's the mission unit
+
+Sparks — small, intrinsic-motivation flares — are the **atomic unit** of what IdeaFlow captures. Not "thoughts" (too broad). Not "tasks" (too post-processed). **Sparks.** They're:
+
+- Fragile — evaporate in minutes without capture.
+- Small — a single insight, not a whole idea.
+- Intrinsic — they come from inside; you don't manufacture them.
+- Clusterable — several sparks reveal a deeper attractor.
+
+## The philosophical weight
+
+From vision-convo's Sparks of Motivation page:
+
+> Meaning is two things at once: (1) Impact — coordinated benefit to the world. (2) Meaning-fullness — having enough mental space to actually feel what things mean.
+
+Sparks are the atomic site where meaning-fullness meets impact. A captured, clustered, graphed spark is both *personal* (it's yours) and *civic* (its cluster can couple into team-level and humanity-level sparks).
+
+## Why it's foundational to this wiki
+
+The earliest `#explainingIdeaflow` Slack tag (2022) points directly at sparks. The 2024 "best pitch" thread pivots on sparks ("I like putting my sparks into a knowledge graph"). The civilization-scale framing (Humanity 3.0) assumes sparks are the atomic substrate of the collective. **Sparks are the through-line.**
+
+## What it pairs with
+
+- [[gestalt-capture-to-gestalt-processing]] — sparks are the things captured; gestalts are the clusters that emerge.
+- [[../layers/personal-cognition]] — sparks are the personal layer's primary input.
+- [[../framings/graph-database-for-your-brain]] — sparks are the nodes.
+
+## Related (vision-convo)
+
+- [Sparks of Motivation](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/sparks-of-motivation)
+- [Jacob's Origin Story](https://wikihub.md/@jacobcole/vision-convo/wiki/themes/jacob-origin-story) — how the RSI-era realization about sparks as *precious, fragile, clusterable* became the product thesis.
new file mode 100644
index 0000000..62c754f
@@ -0,0 +1,56 @@
+---
+title: Framing — "Team Humanity"
+type: framing
+visibility: public
+first-used: 2024-03-XX
+audience: all
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2024-03
+related:
+ - wiki/framings/neocortex-for-the-global-brain.md
+ - wiki/layers/collective-cognition.md
+ - wiki/framings/open-source-knowledge-graphs.md
+---
+
+# "Team Humanity"
+
+## The line
+
+Jacob, March 2024 (user story format):
+
+> "We are just building an übertool/dashboard/collaboration platform to house, track, and support all the thinking that happens online in really large, multi-tiered organizations like Alphabet or Verizon … One such organization happens to be the entire planet earth's, ie **Team Humanity**. Which, whether we are conscious of it, or not, is a team/corporation. But right now, since we don't think of it as such, and we don't use IdeaFlow tools, it's not a very efficiently run organization. But if we have this tool, team humanity can move more efficiently towards its OKRs. Like getting everyone's needs met, and working together to discover/cluster everyone's needs."
+
+## Why it works
+
+1. **Generalizes the wedge.** Enterprise is already IdeaFlow's wedge. Team Humanity is the extreme version of the wedge — same product shape, bigger org.
+2. **Defamiliarizes by analogy.** Thinking of humanity as a single, badly-run company is productive. OKRs, coordination, meetings, knowledge transfer — all the same failure modes, all the same fixes.
+3. **Actionable.** "How do we make team humanity more efficient?" has a first move: make its collective thinking legible.
+
+## Why it's risky
+
+- Literal reading is technocratic / dehumanizing.
+- Humanity isn't *actually* a corporation; analogies have tails.
+- Mitigation: keep it adjacent to [[../layers/collective-cognition]] where the moral framing (Vision for the World, NVC, sparks of motivation) provides the ballast.
+
+## Where it sits
+
+- **Layer:** collective cognition, framed organizationally.
+- **Audience:** all. Especially good for operators / systems-thinkers.
+- **Register:** playful but serious.
+
+## What it pairs with
+
+- [[neocortex-for-the-global-brain]] — the anatomical metaphor for the same object.
+- [[open-source-knowledge-graphs]] — the governance stance.
+- [[god-data-structure]] — the data-model side.
+
+## The pairing that makes it tolerable
+
+Team Humanity by itself reads technocratic. Paired with [vision-convo's Vision for the World](https://wikihub.md/@jacobcole/vision-convo/wiki/themes/vision-for-the-world) — which grounds the scale in the schooling-fish vs cat-dog frame and the sparks-of-motivation unit — it becomes humanistic: Team Humanity is the right metaphor *because* humans are already trying to act as one body; IdeaFlow just makes the trying legible.
+
+## Related
+
+- [[../layers/collective-cognition]]
+- [[../framings/neocortex-for-the-global-brain]]
+- [Vision for the World (vision-convo)](https://wikihub.md/@jacobcole/vision-convo/wiki/themes/vision-for-the-world)
+- [Collective Intelligence (vision-convo)](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/collective-intelligence)
new file mode 100644
index 0000000..7fbe106
@@ -0,0 +1,67 @@
+---
+title: Collective Cognition — the humanity layer
+type: layer
+visibility: public
+audience: all
+related:
+ - wiki/framings/neocortex-for-the-global-brain.md
+ - wiki/framings/team-humanity.md
+ - wiki/framings/open-source-knowledge-graphs.md
+ - wiki/system-map.md
+---
+
+# Collective Cognition
+
+The humanity layer. Billions of users, one federated graph, oriented toward civilization-scale coordination. This is the long arc of IdeaFlow.
+
+## What it does, in one line
+
+> "A **massive-scale collective cognition system for humanity**."
+
+## The long bet
+
+From Jacob's mentor Jack Park (via vision-convo's [jack-park](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/jack-park)), and invoked repeatedly in the `#explainingideaflow` corpus:
+
+> "**Humanity 3.0.** World of Warcraft meets collective sense-making. You're getting together to slay a dragon and do a raid, and you're combining your specialized skills."
+
+The collective layer is what makes the World Quest framing operational. Without a shared substrate, every civilizational effort starts from scratch. With one, specialization composes.
+
+## Key framings that live here
+
+- [[../framings/neocortex-for-the-global-brain]] — the anatomical metaphor
+- [[../framings/team-humanity]] — the organizational metaphor
+- [[../framings/open-source-knowledge-graphs]] — the stance
+- [[../framings/god-data-structure]] — the data-model maximalism
+
+## Applications (built on this layer)
+
+Most of these are projects, not ship-dates. They're what the substrate makes *possible*, not what IdeaFlow ships tomorrow.
+
+- [manifestos.world](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/manifestos-world) — Vision Charter, repository of world-visions
+- [Quests World](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/quests-world) — the World Quest framing, concrete
+- [World Issue Tracker](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/world-issue-tracker) — GitHub issues, but for civilization's bugs
+- [World Progress Bar](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/world-progress-bar) — progress against mapped human goals
+- [Accretive Collective Action](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/accretive-collective-action) — Kickstarter for boycotts, pledges, voting
+
+## Use cases (concrete)
+
+See [[../use-cases]] → "Collective layer" and "Adjacencies":
+
+- Public curated lists beneficial to the world
+- Alliance graph across friends' networks
+- Open Supply Chains
+- Crisis mutual aid (Asheville water-contamination example, 2024)
+
+## The Munger frame (Eden Chan, 2025)
+
+> "A seamless non-bureaucratic web of deserved trust" as "the highest form that Civilization can reach."
+
+Eden Chan's contribution to this layer, from a Munger reading: the collective cognition system is also the **trust substrate**. Legibility of intent (sparks → gestalts → goals) is also legibility of trustworthiness. See the full Munger passage in `raw/slack-explainingideaflow-2022-2026.md`.
+
+## Related (vision-convo cross-links)
+
+- [Vision for the World](https://wikihub.md/@jacobcole/vision-convo/wiki/themes/vision-for-the-world) — the worldview this layer serves
+- [Collective Intelligence](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/collective-intelligence)
+- [One Nervous System](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/one-nervous-system)
+- [Doug Engelbart](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/doug-engelbart)
+- [Jack Park](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/jack-park)
new file mode 100644
index 0000000..f7983a4
@@ -0,0 +1,68 @@
+---
+title: Personal Cognition — the individual layer
+type: layer
+visibility: public
+audience: users
+related:
+ - wiki/framings/graph-database-for-your-brain.md
+ - wiki/framings/notebook-for-our-minds.md
+ - wiki/framings/bicycle-for-the-mind.md
+ - wiki/framings/sparks-of-motivation.md
+ - wiki/system-map.md
+---
+
+# Personal Cognition
+
+The individual layer. One user, one graph, one life. This is IdeaFlow at your desk, in your pocket, in your voice memo, in your meeting.
+
+## What it does, in one line
+
+> "It's a **[[framings/notebook-for-our-minds|notebook for our minds]]**."
+
+## What it's for
+
+- **Capture** without thinking about where it goes. Voice, keyboard, import, photo, message.
+- **Cluster** automatically, so the same spark found in five contexts shows up once with five handles.
+- **Recall** in O(1) — the thought is where you need it when you need it.
+- **Surface** proactively — the substrate reminds you of the person you haven't followed up with, the paper that connects to what you're writing, the goal you articulated six months ago.
+
+## The promise
+
+> "You can tell it anything and it organizes it into a structure that makes sense and you can find it again."
+
+## The anti-promise (what *not* to expect)
+
+It won't feel like a *magical assistant* that reads your mind. It feels like a notebook that quietly gets smarter. See [[../what-it-is-not]].
+
+## Key framings that live here
+
+- [[../framings/graph-database-for-your-brain]] — the data-model metaphor
+- [[../framings/notebook-for-our-minds]] — the aesthetic metaphor
+- [[../framings/bicycle-for-the-mind]] — the augmentation metaphor (Jobs/Engelbart)
+- [[../framings/sparks-of-motivation]] — the mission metaphor
+- [[../framings/gestalt-capture-to-gestalt-processing]] — the methodology
+
+## Use cases (concrete)
+
+See [[../use-cases]], "Personal layer" section:
+
+- Conversation notes → knowledge base
+- Contacts auto-populated from conversations
+- Meeting notes, well-organized for the first time
+- Quick capture, quick sort (mobile)
+- Personal KG × world KG for fundraising
+
+## Pitches that draw from this layer
+
+- [[../pitches/for-users]]
+- [[../pitches/elevator-summary]]
+
+## Related (vision-convo cross-links)
+
+- [Sparks of Motivation](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/sparks-of-motivation)
+- [Inner Ecosystem](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/inner-ecosystem)
+- [Voice-First Thought Capture](https://wikihub.md/@jacobcole/vision-convo/wiki/practices/voice-first-thought-capture)
+
+## Why this layer comes first
+
+Every user of the team and collective layers starts here — as an individual. The personal layer is the onramp. Skip it and you build a top-down system that serves no one's actual habits.
new file mode 100644
index 0000000..3b0c554
@@ -0,0 +1,57 @@
+---
+title: Team Cognition — the organization layer
+type: layer
+visibility: public
+audience: investors, builders
+related:
+ - wiki/framings/graph-database-for-your-brain.md
+ - wiki/pitches/for-investors.md
+ - wiki/system-map.md
+---
+
+# Team Cognition
+
+The team / organization layer. Many users, one shared graph, with privacy at node and edge granularity.
+
+## What it does, in one line
+
+> "The **ultimate CEO dashboard** — and **collective brain for a company**."
+
+## The enterprise wedge
+
+This is IdeaFlow's current revenue engine (2026). Teams have coordination pain acute enough to pay for the substrate. The wedge products:
+
+- **Slack bot that listens to conversations** and harvests unstructured team knowledge into a graph — then suggests connections between people who have related ideas.
+- **Meeting notes pipeline** — voice/text meeting capture producing structured knowledge with connection-provenance, not just summaries.
+- **Internal "Twitter" feed** that surfaces context relevant to whatever the user is currently working on.
+- **Innovation management** — mapping ideas and connections across an organization's actual thinking surface (not its org chart).
+
+## Why teams pay
+
+Teams have three problems IdeaFlow solves that notes apps don't:
+
+1. **Knowledge silos.** What's in one head isn't in another's.
+2. **Context loss.** Every meeting re-derives the same context from scratch.
+3. **Coordination drift.** People pursue subtly-different goals because the canonical goal isn't legible.
+
+The graph is the shared surface that resolves all three. Slack resolves none of them; docs resolve one with heavy overhead; IdeaFlow resolves all three because the substrate *is* the shared cognition.
+
+## What a team's graph looks like
+
+- Projects as nodes, with goals, open questions, decisions, artifacts all attached.
+- People as nodes, with their responsibilities, interests, recent thinking.
+- Meetings as nodes, with structured takeaways and connection provenance.
+- Slack messages as edges (non-privileged, time-stamped, hide-from-main-timeline-by-default).
+- Customers, products, markets as nodes — importable from systems of record, bidirectionally linked.
+
+## Related (on this wiki)
+
+- [[../framings/graph-database-for-your-brain]] — at team scale
+- [[../use-cases]] → "Team layer"
+- [[../pitches/for-investors]]
+- [[../pitches/for-builders]]
+
+## Related (vision-convo cross-links)
+
+- [Collective Intelligence](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/collective-intelligence) — the conceptual parent
+- [IdeaFlow (project page)](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/ideaflow)
new file mode 100644
index 0000000..48512c1
@@ -0,0 +1,64 @@
+---
+title: Design History — how this wiki got scaffolded
+type: meta
+visibility: public
+---
+
+# Design History
+
+On 2026-04-20, Jacob asked Claude Code to turn the `#explainingideaflow` tag corpus into a coherent LLM wiki. The earlier exchange (line 462 of session `1137ed19-6d0a-4294-9240-7c559603a947`) had already laid out the question:
+
+> "Separately I'm also thinking about somehow integrating all of the `#explainingideaflow` tags from notestream and slack into some LLM wiki which coherently updates the IdeaFlow vision. I'm wondering if it should be in this wiki or a different wiki."
+
+Claude's recommendation at that time (unactioned until now): a **separate wiki**, cross-linked with [vision-convo](https://wikihub.md/@jacobcole/vision-convo). On 2026-04-20, Jacob said "let's try to make a wiki about that and maybe add to it by referencing relevant stuff in the current wiki." This page records how the scaffold was chosen.
+
+## Claude Code's original proposal
+
+1. **Name:** `ideaflow-vision`
+2. **Structure:** `index.md`, `AGENTS.md`, `raw/` by year-window, `wiki/framings/` (one page per metaphor), `wiki/pitches/` (audience-specific), `wiki/themes/`, `wiki/sources/`
+3. **Privacy:** synthesize *Jacob's own* framings; co-worker quotes sparingly. Cross-link heavily to vision-convo.
+4. **Scope:** Slack only for v1. Defer notestream/Thoughtstream.
+
+## Codex second opinion (gpt-5.4 high, 2026-04-20)
+
+Asked Codex to push back. Summary of its critique:
+
+1. **Separate wiki — yes, agreed.** Different source type, different job, different reader intent. Don't bury this inside vision-convo.
+2. **"Too axis-heavy."** Don't make framing, audience, theme, and era *all* first-class. Pick a primary axis.
+3. **Recommended organization (hybrid):**
+ - *Primary:* functional layers — `personal/`, `team/`, `humanity/`
+ - *Secondary:* `framings/` — one page per durable metaphor
+ - *Single:* `chronology.md` — era as context, not navigation
+ - *Single:* `entry-points.md` — audience translations
+4. **Quote ratio:** 80–90% synthesis, 10–20% verbatim. Keep `raw/` lightly cleaned.
+5. **Missing page types:** `north-star-thesis`, `what-it-is-not`, `system-map`, `chronology`, `canonical-terms`, `open-questions`, `use-cases`.
+6. **Rename `pitches/`:** reads salesy and time-bound → `translations/` / `entry-points/` / `explainers/`.
+7. **Risks:** context collapse, internal-language leakage, metaphor sprawl, product/worldview blur. Mitigations: editorial note, dating, separate canonical-current from historical, be selective with quotes even with permission.
+
+## Jacob's decisions
+
+1. **Keep `pitches/`.** Overrule Codex's rename. "Pitches" is the right word; the wiki isn't ashamed of pitching.
+2. **Use verbatim lines.** Invert Codex's ratio — lean on Jacob's own voice. Synthesis is connective tissue, not the main event.
+3. **Evolution, not change.** Frame the chronology this way: *"The vision hasn't necessarily changed longitudinally, but it has been refined and has evolved and matured, and more forks have been discovered, with more details and realizations."* This is the backbone of [[../chronology|chronology.md]].
+4. **Adopt** Codex's missing page types: north-star-thesis, what-it-is-not, system-map, canonical-terms, open-questions, use-cases.
+5. **Adopt** the functional-layer primary organization (personal → team → humanity).
+6. **Save** this design history in the wiki itself (this page) *and* in a beads ticket.
+
+## Risk mitigations adopted
+
+- Editorial note in [[../../AGENTS|AGENTS.md]] acknowledging the synthesis is of historical framings.
+- Date every ingested excerpt in `raw/`.
+- Every framing page has a `first-used` date and cites the raw source.
+- Linking discipline: framings cite [[../north-star-thesis|north-star-thesis]] to avoid metaphor sprawl.
+- Separation of concerns: [[../what-it-is-not|what-it-is-not]] and [[../system-map|system-map]] draw the product/philosophy line.
+
+## Related
+
+- Beads ticket: `wikihub-4i3b` (full design history + decisions, on the wikihub issue tracker)
+- Session: `1137ed19-6d0a-4294-9240-7c559603a947` — original conversation that raised the question
+- Codex session: `019daa5f-4a5c-7771-a654-a07d44510344` — second-opinion conversation
+- Sister wiki: [vision-convo](https://wikihub.md/@jacobcole/vision-convo)
+
+## What this page is *for*
+
+When a future editor (Jacob or an agent) looks at this wiki and asks "why this shape and not another?" — the answer is here. The shape is a compromise between a bottom-up archive of Jacob's actual framings and a top-down taxonomy Codex proposed. Both perspectives left their fingerprints.
new file mode 100644
index 0000000..d6c46e9
@@ -0,0 +1,72 @@
+---
+title: North-Star Thesis — what IdeaFlow is really for
+type: concept
+visibility: public
+related:
+ - wiki/system-map.md
+ - wiki/what-it-is-not.md
+ - https://wikihub.md/@jacobcole/vision-convo/wiki/themes/vision-for-the-world
+---
+
+# North-Star Thesis
+
+In one sentence, in Jacob's own words:
+
+> "Now, what I'm actually building is a **massive-scale collective cognition system for humanity**. But one of the pieces it takes is a personal knowledge management system."
+> — 2024-03-22, `#explainingideaflow #best #pitch`
+
+That's the whole thing. Every other framing in this wiki is a projection of that statement onto a specific audience or a specific layer.
+
+## The three-scale decomposition
+
+IdeaFlow is building one substrate that works at three scales. Same data model, same interaction grammar, same graph.
+
+- **Personal** — a [[framings/graph-database-for-your-brain]] — a [[framings/notebook-for-our-minds]] — *"quick capture, quick sort"*.
+- **Team/company** — a [[layers/team-cognition|collective brain]] — *"the ultimate CEO dashboard"* — a Slack-listening bot that harvests unstructured conversation into structured knowledge.
+- **Humanity** — a [[framings/neocortex-for-the-global-brain]] — the substrate under [[framings/team-humanity]] coordinating at civilization scale.
+
+See [[system-map]] for how these stack.
+
+## Why "cognition" and not "notes"
+
+Jacob's repeated insistence, across years:
+
+> "Reducing intelligence to generation is like reducing software to print() statements."
+> — 2024-02-15
+
+The rejected framing: *notes app*. The insistence: **cognition** — capture, cluster, relate, surface, augment, coordinate. Notes are the raw material; cognition is what the substrate *does* with them.
+
+Cody Hergenroeder's shorthand for this at the product level:
+> "**O(1) capture and recall** is how I've been phrasing it to myself."
+
+## Why a graph, not a document
+
+Jacob, citing Taylor Mitchell's early-2024 framing:
+
+> "In most outliners, when you 'expand' a node, you're showing its children. This is different from graph database explorers, where when you 'expand' a node, you're showing *all related nodes,* not just children."
+
+A graph is the right shape because the same spark ([[framings/sparks-of-motivation]]) appears in many contexts at once — planning, health, work, relationships. A document forces a single ordering that hides everything else. See also [[framings/graph-database-for-your-brain]].
+
+## Why now
+
+The markup burden that killed the 2000s Semantic Web is gone:
+
+> `#ExplainingIdeaFlow #whyNow #SemanticWeb` — LLMs can now produce structured graph nodes from unstructured input.
+
+Jacob's collaborator context: Tim Berners-Lee was one of Jacob's research advisors at Oxford/MIT (see [vision-convo → entities/tim-berners-lee](https://wikihub.md/@jacobcole/vision-convo/wiki/entities/tim-berners-lee)). The lineage runs straight from the Semantic Web through the LLM era into IdeaFlow.
+
+## The long bet (civilization scale)
+
+From vision-convo's [Vision for the World](https://wikihub.md/@jacobcole/vision-convo/wiki/themes/vision-for-the-world) theme:
+
+> "We are moving one way and another part of us moves the other way. We're fragmented … We want to be the fish, not the cat-dog."
+
+IdeaFlow is the substrate on top of which civilization can become the schooling-fish body instead of the cat-dog. Concrete applications: [manifestos.world](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/manifestos-world), [World Issue Tracker](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/world-issue-tracker), [World Progress Bar](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/world-progress-bar), [Accretive Collective Action](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/accretive-collective-action).
+
+## Related
+
+- [[system-map]] — how the three scales stack
+- [[what-it-is-not]] — category-confusion prevention
+- [[chronology]] — how this thesis was refined 2022→2026
+- [[canonical-terms]] — the working vocabulary
+- [[pitches/best-pitch]] — Jacob's own best compression of this thesis
new file mode 100644
index 0000000..9ac402d
@@ -0,0 +1,57 @@
+---
+title: Open Questions — unresolved tensions
+type: concept
+visibility: public
+related:
+ - wiki/north-star-thesis.md
+---
+
+# Open Questions
+
+Unresolved tensions surfaced across the `#explainingideaflow` corpus. These are not bugs. They are where the vision is still negotiating with itself.
+
+## 1. Global stream vs. personal stream
+
+From 2025: Jacob wants *"everything I ever write or produce to end up in my thought stream"* — Slack, email, voice, docs. But the **global stream** is also a promised surface. How are negative filters expressed? How is *"non-explicit" / "raw"* flagged as a first-class node property vs. a list-membership property?
+
+Status: stated as an open architectural decision in 2025. No final call yet.
+
+## 2. Graph-first UX vs. outliner UX
+
+Taylor Mitchell's 2024 analysis: most tools-for-thought people use outliners (Workflowy, Roam) as their mental model, but IdeaFlow wants users to *feel* like they're working in a graph. The UI compromise (workflowy-as-scaffolding with graph semantics) is a tactical choice, not a final one. What does a graph-native UI look like once outliners aren't the onramp?
+
+## 3. Markup burden: still there, just moved
+
+The why-now claim is that LLMs close the markup gap. In practice, LLMs still produce wrong tags and invent nodes. The burden has *moved from the user to the review step.* Who reviews, when, and with what UX?
+
+## 4. Public vs. private at the personal layer
+
+If the long arc federates graphs, what's the default privacy? Node-level? Edge-level? Zone-level? The instinct has been "everything private by default, surface what you choose." But the 2025 alliance-graph framing (query the best intro path across friends' networks) requires aggressive opt-in sharing. Where's the right default?
+
+## 5. Enterprise wedge vs. consumer ambition
+
+Teams pay; individuals don't. But the enterprise wedge has its own gravity — it shapes the product toward Slack harvesters and CEO dashboards and away from *"a notebook for our minds."* How long before the wedge risks absorbing the project?
+
+## 6. The "God data structure" trap
+
+Jacob's maximalist framing (*"our God data structure should be able to contain everything in the world"*) is directionally right but culturally risky: it reads as hubristic. The wiki keeps the phrase because it's Jacob's own, but it's worth flagging that readers will judge it.
+
+## 7. Where does [Noos](https://globalbr.ai) sit?
+
+Jacob's Noos knowledge graph (separate product, separate wiki surface) overlaps significantly with IdeaFlow's personal layer. Are they the same thing at different stages, parallel products, or one being the other's substrate? The `#explainingideaflow` corpus doesn't fully answer this.
+
+## 8. Humanity 3.0 on what timeline?
+
+The long bet is civilization-scale coordination. The wedge is enterprise team-cognition. The gap is huge. No published roadmap ties them together with dates. How much should it?
+
+## 9. Speculative scientific claims
+
+Tagged in `#paperidea`-style messages: *"do this equipping [LLMs] with a hypergraph store."* These are load-bearing for the why-now story. But they're not substantiated in the corpus itself. Do they need their own "research page" in a future wiki?
+
+## 10. Voice vs. keyboard
+
+Thoughtstream started voice-first. The current product is keyboard-first with voice. The "dream-cap" speculation in vision-convo points even further (sleep-capture). What's the input hierarchy, and does it change by layer?
+
+---
+
+When one of these resolves, move it to an entry in [[chronology]] with a dated note.
new file mode 100644
index 0000000..3fb27e0
@@ -0,0 +1,67 @@
+---
+title: Pitch — "the best pitch" (Jacob's own)
+type: pitch
+audience: investors, curious outsiders
+visibility: public
+first-used: 2024-03-22
+sources:
+ - raw/slack-explainingideaflow-2022-2026.md#2024-03-22
+related:
+ - wiki/pitches/elevator-summary.md
+ - wiki/pitches/for-investors.md
+ - wiki/framings/graph-database-for-your-brain.md
+---
+
+# The Best Pitch
+
+## Why this page exists
+
+Jacob flagged this himself with `#explainingideaflow #best #pitch` in March 2024. So this is the canonical verbatim version — his own voice, his own rhythm, the one he rehearsed live while drafting.
+
+## Jacob's full pitch, verbatim (March 2024)
+
+> Now, what I'm actually building is a **massive-scale collective cognition system for humanity.** But one of the pieces it takes is a personal knowledge management system. You can tell it anything and it organizes it into a structure that makes sense and you can find it again. I'm running a seed-based startup in the Bay Area and we recently launched and I'd love to show you guys. It takes just a second.
+
+*(Follow-up, when asked what it is:)*
+
+> It's called… I don't really understand. What's the… Well, it's like Obsidian, but AI-powered and better ergonomics. It's not…
+>
+> Like, Obsidian is very hackery and complicated. Imagine Obsidian, but optimized for quickly capturing new thoughts and with a much simpler organizational paradigm, but also power. Who here has used Obsidian or Rome Research or something like that? Okay, so yeah. So it's some… It's like a…
+>
+> What do you call those things? You're saving me this? It's like the ultimate.
+
+*(Compression:)*
+
+> **graph database for your brain**
+
+*(Closing — the moral frame:)*
+
+> **Tool to discover the path of wisdom and empower people to act on it?** Build a neocortex for the global mind/brain; for the Internet? — this covers suggestion board — supporting you in acting on your goals — organizer of information that comes into your life — system to track and coordinate all human scientific and practical endeavor — human activity — align the world to the path of wisdom. `#explainingideaflow`
+
+## Why it's the best
+
+1. **Opens with the civilizational claim.** No apologizing for scale.
+2. **Immediately grounds it in a personal concrete.** "One of the pieces it takes is a personal knowledge management system."
+3. **Invites a demo.** "I'd love to show you. It takes just a second."
+4. **Confesses uncertainty.** "I don't really understand. What's the…" — disarms the investor/curious person who expects polished.
+5. **Reaches for familiar reference.** Obsidian / Roam. Corrects their shortcomings. Lands on *graph database for your brain*.
+6. **Ends on the moral frame.** "Align the world to the path of wisdom." Non-optional for Jacob.
+
+## When to use
+
+- Any time you have 90 seconds and an audience that can hold one abstract claim *and* one concrete example.
+- Works in person. Works on camera. Works over lunch.
+
+## When *not* to use
+
+- Cold DM's to strangers (no room for the demo invite to land).
+- Highly technical audiences (they want [[for-builders]] or [[../framings/god-data-structure]] instead).
+- Very short elevator rides (use [[elevator-summary]]).
+
+## Related
+
+- [[elevator-summary]] — the 30-second version
+- [[for-investors]] — the VC-tuned version
+- [[../framings/graph-database-for-your-brain]]
+- [[../framings/neocortex-for-the-global-brain]]
+- [[../north-star-thesis]]
new file mode 100644
index 0000000..04e6733
@@ -0,0 +1,32 @@
+---
+title: Pitch — elevator summary (30 seconds)
+type: pitch
+audience: all
+visibility: public
+related:
+ - wiki/pitches/best-pitch.md
+ - wiki/framings/graph-database-for-your-brain.md
+---
+
+# Elevator Summary
+
+Three compressions, by register. Pick the one that matches the room.
+
+## Consumer (10 seconds)
+
+> "IdeaFlow is a **graph database for your brain.** Capture any thought by voice or text, and it organizes itself. Like Obsidian, but smarter and faster."
+
+## Investor (20 seconds)
+
+> "We're building a **massive-scale collective cognition system for humanity**, starting with an enterprise wedge that turns Slack conversations and meeting notes into a shared graph a team can actually reason over. Think **neocortex for the company.** The long arc is the same graph, federated, at civilizational scale — Google did this for the Internet; we're doing it for information in people's minds." *(— Alex Kayyal, Lightspeed, said that last line. We liked it.)*
+
+## Builder / technical (30 seconds)
+
+> "Three-layer stack. At the personal layer, it's **a graph database for your brain** — O(1) capture and recall. At the team layer, it's a **collective brain for a company** — Slack bot + meeting notes pipeline producing a shared graph with provenance. At the humanity layer, it's the open-source **neocortex for the global brain** — Semantic-Web-style federation, but with LLMs doing the markup instead of humans. Same substrate at every scale. The wedge is enterprise; the long arc is [[../framings/team-humanity|Team Humanity]]."
+
+## Related
+
+- [[best-pitch]] — Jacob's own full version
+- [[for-investors]]
+- [[for-users]]
+- [[for-builders]]
new file mode 100644
index 0000000..3a6b16a
@@ -0,0 +1,77 @@
+---
+title: Pitch — for builders / collaborators
+type: pitch
+audience: builders
+visibility: public
+related:
+ - wiki/pitches/best-pitch.md
+ - wiki/framings/medium-for-thought.md
+ - wiki/framings/god-data-structure.md
+ - wiki/framings/open-source-knowledge-graphs.md
+---
+
+# Pitch — for Builders / Collaborators
+
+The version tuned for engineers, designers, researchers, and co-conspirators evaluating whether to work *on* IdeaFlow. Leads with substrate, not shipping.
+
+## The bet
+
+> **First build a medium for thought, then there are things you can build in world with it.**
+> — Joe Henke, IdeaFlow, early 2024
+
+IdeaFlow is infrastructure-first. The substrate is the point; the applications compose.
+
+See [[../framings/medium-for-thought]].
+
+## What the substrate is
+
+- A graph data model expressive enough to hold text, relations, spatial regions, category-theoretic structures, calendar events, people, conversations, files. The in-house framing: [[../framings/god-data-structure|the God data structure]] / Gopher backbone / **GraphMirror** (Jacob, 2025: *"Everyone uses ProseMirror. We could offer GraphMirror."*).
+- An editor that *feels* like workflowy but *is* a graph (Taylor Mitchell's 2024 framing: *"graph database explorers expand all related nodes, not just children"*).
+- LLMs doing the markup burden so users don't have to.
+- Federation-ready from day one — each user's graph is a subgraph of a larger commons.
+
+## Open-source movement
+
+Jacob, 2024-10:
+> "Starting the open source movement for knowledge graphs, e.g. **Open Supply Chains**."
+
+This isn't a walled-garden KM product. The long-arc goal is a commons of structured knowledge with federation and credible-neutrality properties. See [[../framings/open-source-knowledge-graphs]].
+
+## The interesting problems
+
+- **Graph editor UX.** No one has shipped a truly graph-native editor that doesn't bounce off mainstream users.
+- **LLM + structure feedback loop.** Markup without burden means LLM-generated structure with human-in-the-loop review. Review UX is wide open.
+- **Federation without extraction.** How do personal graphs federate into team / public graphs without siphoning value away from their authors?
+- **Hypergraph-store-for-LLMs.** Jacob, 2025: *"It helps language models … do this equipping them with a hypergraph store."* Interesting adjacent research thread.
+- **Provenance at every node and edge.** The meeting-notes demo (Oct 2025) claims *"the first well-organized meeting notes ever taken in human history"* because of provenance. Making that default, not artisanal, is a substrate problem.
+- **Chunking a God data structure.** How do you make a data model capable of everything *usable* for one thing?
+
+## Why now
+
+- LLMs close the Semantic-Web markup gap.
+- The tools-for-thought movement has run into its ceiling without structure.
+- Hypergraph / property-graph databases are fast enough at scale.
+- The AI-agent wave needs a persistent substrate that survives any single model.
+
+## Lineage
+
+- Doug Engelbart → Jack Park → Jacob.
+- Tim Berners-Lee (Jacob's Oxford/MIT advisor).
+- Vannevar Bush's memex as the patron saint.
+
+## What we value in collaborators
+
+(Inferred from the Slack corpus, not a formal HR statement:)
+
+- Care about the two-stage structure — medium before applications.
+- Comfort with both graph abstraction and UX intuition. Taste matters.
+- Willingness to say "this framing is wrong" when it is. (Taylor and Cody did this repeatedly and moved the product.)
+- Appreciation for speculation as a work product (see [[../open-questions]]).
+
+## Related
+
+- [[best-pitch]]
+- [[../framings/medium-for-thought]]
+- [[../framings/god-data-structure]]
+- [[../framings/open-source-knowledge-graphs]]
+- [[../open-questions]]
new file mode 100644
index 0000000..68c3183
@@ -0,0 +1,61 @@
+---
+title: Pitch — for investors
+type: pitch
+audience: investors
+visibility: public
+related:
+ - wiki/pitches/best-pitch.md
+ - wiki/pitches/elevator-summary.md
+ - wiki/layers/team-cognition.md
+---
+
+# Pitch — for Investors
+
+The version tuned for people evaluating IdeaFlow as a startup. Lead with the wedge; hold the civilizational frame in reserve.
+
+## The wedge (today)
+
+Enterprise team-cognition. The product surfaces:
+
+- **Slack bot** that harvests unstructured conversation into a structured graph across the org.
+- **Meeting notes** with connection provenance — the first *"well-organized meeting notes ever taken in human history"* (Jacob + Tejas, Oct 2025).
+- **Innovation management** — mapping actual thinking surface, not the org chart.
+- **Internal Twitter** surfacing relevant context for what someone's currently working on.
+
+Teams have three coordination problems notes apps don't solve (knowledge silos, context loss, coordination drift). The graph substrate solves all three because the substrate *is* the shared cognition.
+
+See [[../layers/team-cognition]] for the full wedge decomposition.
+
+## Why-now
+
+- **LLMs close the Semantic Web's markup gap.** The 2000s KG wave failed on human markup burden. LLMs eliminate it. `#ExplainingIdeaFlow #whyNow #SemanticWeb` (Jacob, 2025).
+- **AI coding agents are devouring structured-data markets.** Anything that doesn't produce persistent structured knowledge loses leverage to agents. IdeaFlow produces the structure.
+- **Noticeable tailwind.** Sample (April 2025): *"These models barely know me. At this point, I feel like a traveling salesman from the 1800s, lugging a little suitcase of context from one AI to the next."* (Saanya Ojha, VC, on LinkedIn — quoted by Jacob as a VC articulating the thesis.)
+
+## Lineage (the room you're standing in)
+
+- **Tim Berners-Lee** was one of Jacob's research advisors at Oxford/MIT. The Semantic Web descent is literal, not rhetorical.
+- **Doug Engelbart** (augmentation) → **Jack Park** (Jacob's mentor, cured his own cancer with a KM system, 1990s) → IdeaFlow.
+- **Naval Ravikant** is an angel investor.
+
+## The long bet (the extra 30 seconds, if the room wants it)
+
+The same graph, federated, at civilizational scale. A **neocortex for the global brain** ([[../framings/neocortex-for-the-global-brain]]). Applications: [manifestos.world](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/manifestos-world), [World Issue Tracker](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/world-issue-tracker), [World Progress Bar](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/world-progress-bar), [Accretive Collective Action](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/accretive-collective-action).
+
+## The ask
+
+Depends on the round. Not templatable here. But: if the room is investing in the wedge, they're also buying option value on the long bet.
+
+## Social-proof lines
+
+- **Alex Kayyal, Lightspeed:** *"What I think you're doing is really cool. Sort of what Google did for the Internet but for information not on the web but in people's minds."*
+- **Laurel Touby:** *"AI help me fundraise. Like having an assistant with me all of the time."* (From the 2024 demo conversation.)
+- Drafts of the deck for the Draper Summit (2025).
+
+## Related
+
+- [[best-pitch]]
+- [[elevator-summary]]
+- [[../layers/team-cognition]]
+- [[../framings/graph-database-for-your-brain]]
+- [[../chronology]]
new file mode 100644
index 0000000..dc611f7
@@ -0,0 +1,69 @@
+---
+title: Pitch — for users
+type: pitch
+audience: users
+visibility: public
+related:
+ - wiki/pitches/best-pitch.md
+ - wiki/layers/personal-cognition.md
+---
+
+# Pitch — for Users
+
+The version tuned for someone who might actually *use* the product. Leads with pain, not ambition.
+
+## The pain
+
+- You write things down so you don't forget. You forget anyway.
+- You have the same "aha" three times because you can never find the first one.
+- You tell five people five different versions of the same idea, then lose track of which version is the current one.
+- You're a daily AI user, but every conversation starts from zero.
+- You want a brain *outside* your brain — one that actually helps, not just stores.
+
+Jacob put it directly (2025):
+> "I often say, man, I'm writing all this stuff down and I hope someday AI can process it all and make sense of it and tag it and surface all my tags and stuff because on this thread I'm going to say `#usecase`. Tons of my friends have said this. We are actually building that software!"
+
+## The promise
+
+> You can tell it anything and it organizes it into a structure that makes sense, and you can find it again.
+
+Concretely:
+
+- **Quick capture, quick sort** — voice, keyboard, import. Minimal thinking about where it goes.
+- **The same thing found five places shows up once** with five handles.
+- **Sparks cluster automatically** — a few related thoughts reveal the thing you're actually after.
+- **Things surface** when they're relevant — the paper you read, the person you should text, the note you took months ago.
+
+## What it feels like
+
+> **A notebook for our minds** — that augments your intelligence. Kind of like Obsidian, but frictionless, voice-friendly, AI-smart, and with real structured data on the people and things you care about.
+
+See [[../framings/notebook-for-our-minds]].
+
+## What it replaces (loosely)
+
+- Your scattered Notion / Obsidian / Apple Notes.
+- The Slack DMs to yourself that you can't search.
+- The iMessage-to-yourself threads.
+- The screenshots you never open.
+- The half-remembered conversations from last month.
+
+## What it doesn't replace
+
+- A chat UI for talking to a model (it plugs into that).
+- Your calendar / task tool (those ride on top).
+- Your relationships with people (it helps you remember them better).
+
+## The aspirational version
+
+- **Alliance graphs across your networks** — your LinkedIn, iMessage, email, all in one queryable place. Opt-in federate with friends to find the best intro path to anyone.
+- **Conversation capture → structured KB** — talk naturally; it builds the knowledge base behind you.
+- **Personal KG × world KG** — suggests the top 3 people to reach out to, drawn from your knowledge and the world's.
+
+## Related
+
+- [[best-pitch]]
+- [[elevator-summary]]
+- [[../layers/personal-cognition]]
+- [[../framings/notebook-for-our-minds]]
+- [[../framings/graph-database-for-your-brain]]
new file mode 100644
index 0000000..a371a8c
@@ -0,0 +1,113 @@
+---
+date: 2026-05-08
+related:
+- wiki/north-star-thesis.md
+- wiki/system-map.md
+- wiki/layers/collective-cognition.md
+- https://worldissuetracker.com/progress-bars
+- https://worldissuetracker.com/tracker/scientific-grand-challenges
+- https://worldissuetracker.com/tracker/world-issues
+- https://worldissuetracker.com/issue/6bc61081-b564-4219-8065-51bc48d51626
+- https://worldissuetracker.com/issue/96db73e5-b1da-4e54-b1f7-e5f6cc57b572
+title: Resource Matching for Grand Challenges
+type: vision-note
+visibility: public
+---
+
+# Resource Matching for Grand Challenges
+
+IdeaFlow is building a system that can match the resources the world is already generating to the grand challenges the world actually needs solved.
+
+Those resources are not only money or institutions. They include notes in people's notebooks, half-formed ideas, observations, scientific anomalies, private goals, public issues, social graphs, project histories, meeting notes, hackathon ideas, and the tacit knowledge sitting inside people's personal and team workflows. Most of this material never reaches the problems where it could matter. It remains trapped in notebooks, chats, PDFs, lab logs, personal task lists, and project-specific tools.
+
+The vision is to make those latent resources composable.
+
+## Core Model
+
+The system has two complementary directions.
+
+First, top-down grand challenges: structured representations of the large problems humanity is trying to solve. These can include scientific grand challenges, country and civic problems, institutional goals, existential risks, health problems, education problems, and the more explicit Hierarchical Utopia Issue Tracker frame: a hierarchy of goals, needs, problems, blockers, strategies, and open loops.
+
+Second, bottom-up observations: the small pieces of reality people notice. A lab result, a surprising pattern, a field observation, a product idea, a policy failure, a note from a conversation, a hackathon idea, a personal goal, a user complaint, a local civic issue, a quote from a paper, or a private intuition.
+
+The work is to connect these layers:
+
+- observations to hypotheses
+- hypotheses to issues
+- issues to grand challenges
+- grand challenges to people, projects, funding, institutions, and next actions
+
+This is scientific propagation in product form. New observations should not just be stored. They should find the challenges they may help solve.
+
+## Why This Belongs In The IdeaFlow Vision
+
+This is the collective-cognition version of the same IdeaFlow thesis:
+
+- At the personal layer, capture should be frictionless enough that thoughts and observations are not lost.
+- At the team layer, observations become shared context, tasks, roadmaps, and decisions.
+- At the humanity layer, those observations can feed public issue trackers, scientific challenge maps, Idea Hunt, WikiHub pages, and progress dashboards.
+
+World Issue Tracker is one civic/scientific surface for this. WikiHub is the durable knowledge surface. Idea Hunt and Idea Bank are the idea-discovery surfaces. ListHub-like lists can be the provenance-heavy observation surface. SuperConnector and Noos can connect the right people and private goals. The point is not that every surface becomes one app immediately. The point is that they share a substrate and can route useful signals to each other.
+
+## Hierarchical Utopia Issue Tracker
+
+The Hierarchical Utopia frame should be treated as the explicit "goal tree" layer:
+
+- What does a better world require?
+- Which needs or goals sit above which subgoals?
+- Which problems block which goals?
+- Which scientific grand challenges unlock many downstream goals?
+- Which observations, ideas, and people might help unblock them?
+
+Scientific Grand Challenges should plug into this hierarchy rather than remain a separate list. A grand challenge like "understand consciousness", "cure aging", "make clean energy abundant", or "solve safe coordination at scale" should be represented as a high-level challenge with linked subproblems, observations, hypotheses, projects, funding needs, and related people.
+
+The bottom-up side is equally important. A list of scientific observations should not be treated as low-status raw material. It is the sensing layer of the system. Many important discoveries begin as anomalies or notes that did not yet know which grand challenge they belonged to.
+
+## Product Implications
+
+World Issue Tracker should support featured scientific grand challenge trackers, including the existing Scientific Grand Challenges tracker:
+
+- https://worldissuetracker.com/tracker/scientific-grand-challenges
+
+It should also connect those challenges to World Progress Bars, which already exists as a WIT surface:
+
+- https://worldissuetracker.com/progress-bars
+
+Progress Bars is the measurement layer. Grand challenge trackers describe the problems and blockers; observation lists provide bottom-up evidence; Idea Hunt/Idea Bank propose candidate solutions; World Progress Bars asks what a better world is trying to become and whether reality is moving in that direction. A mature system should let a grand challenge point to progress bars, sub-bars, indicators, baselines, target states, and historical trajectories.
+
+It should also support or integrate with a bottom-up observation list surface in the spirit of ListHub. Those observations should have provenance, citations, confidence, novelty, source context, and links to the challenges or hypotheses they may affect.
+
+The system should eventually let agents ask:
+
+- Which observations might matter for this grand challenge?
+- Which grand challenges might this observation affect?
+- Which people have captured related notes, goals, or ideas?
+- Which projects, issues, or funding paths could move the challenge forward?
+- Which ideas in Idea Bank or Idea Hunt are actually subsolutions to a larger goal?
+
+## Current WIT Links
+
+This note should stay connected to the WIT tickets created from the same thread:
+
+- Feature scientific grand challenge trackers and bottom-up observation lists: https://worldissuetracker.com/issue/6bc61081-b564-4219-8065-51bc48d51626 (`world-issue-tracker-0h5x`)
+- First-class related tracker links and tracker groups: https://worldissuetracker.com/issue/96db73e5-b1da-4e54-b1f7-e5f6cc57b572 (`world-issue-tracker-o9uj`)
+- Flesh out World Progress Bars as the measurement layer for grand challenges: `world-issue-tracker-mvjg`
+- Idea Hunt page and ideas surface: `world-issue-tracker-1m1`
+- Design tracker taxonomy and grouping model: `world-issue-tracker-aae`
+- Audit VisionCharter and WikiHub vision pages for WIT integration: `world-issue-tracker-2sb5`
+- Import hackathon ideas into Idea Bank without polluting Idea Hunt: `world-issue-tracker-6go0`
+- SuperConnector profile integration for WIT ideas and private goals: `world-issue-tracker-oqyv`
+
+## Open Design Question
+
+The product should not prematurely decide whether this is one app or many. The better framing is one substrate with several high-fit surfaces:
+
+- World Issue Tracker for public problems, blockers, and dependencies
+- World Progress Bars for goal state, indicators, and measurable trajectories
+- WikiHub for durable knowledge pages
+- Idea Hunt and Idea Bank for ideas and candidate solutions
+- ListHub-like lists for observations and sourced claims
+- SuperConnector for people, goals, and matching
+- Noos/Cortex/Notestream for capture and routing from everyday work
+
+The grand-challenge layer is where these surfaces become more than tools. It is where captured human context gets matched to the goals that can use it.
\ No newline at end of file
new file mode 100644
index 0000000..604141d
@@ -0,0 +1,92 @@
+---
+title: System Map — personal → team → humanity
+type: concept
+visibility: public
+related:
+ - wiki/layers/personal-cognition.md
+ - wiki/layers/team-cognition.md
+ - wiki/layers/collective-cognition.md
+ - wiki/north-star-thesis.md
+---
+
+# System Map
+
+IdeaFlow operates at three scales, stacked. Same substrate, different observers.
+
+```
+┌──────────────────────────────────────────────────────────────┐
+│ COLLECTIVE COGNITION │
+│ (humanity layer — Team Humanity, Humanity 3.0, │
+│ the neocortex for the global mind, World Quest, │
+│ civilization-scale coordination on shared goals) │
+│ │
+│ ▲ applications: manifestos.world, World Issue │
+│ │ Tracker, World Progress Bar, Accretive Collective │
+│ │ Action, open data commons │
+└──────┼───────────────────────────────────────────────────────┘
+ │
+┌──────┴───────────────────────────────────────────────────────┐
+│ TEAM COGNITION │
+│ (organization layer — the ultimate CEO dashboard, │
+│ collective brain for a company, Slack-bot harvesters │
+│ that turn unstructured conversation into structured │
+│ knowledge, internal-Twitter surfacing, innovation mgmt) │
+│ │
+│ ▲ applications: enterprise product, team alliances, │
+│ │ meeting note → structured KB pipelines │
+└──────┼───────────────────────────────────────────────────────┘
+ │
+┌──────┴───────────────────────────────────────────────────────┐
+│ PERSONAL COGNITION │
+│ (individual layer — graph database for your brain, │
+│ notebook for our minds, bicycle for the mind, │
+│ quick capture / quick sort, O(1) capture and recall) │
+│ │
+│ ▲ applications: thought capture, personal KG, │
+│ │ relationship memory, task/goal surfacing, │
+│ │ "AI that knows me" │
+└──────────────────────────────────────────────────────────────┘
+```
+
+## The same object, three observers
+
+A single user's graph is a subgraph of their team's graph, which is a subgraph of humanity's graph. Privacy is a property of edges and nodes, not a hard division between systems. This is a feature, not a bug — it's what lets sparks flow upward (from individual will, to organizational priorities, to civilizational goals) and context flow downward (from shared knowledge to individual decisions).
+
+## The upward flow: sparks → clusters → gestalts → goals
+
+> "I like putting my sparks into a knowledge graph … ooh, here's a spark here, here's a spark here, spark here. Okay, I can graph them. Cluster, cluster. This is power."
+> — Jacob, from [vision-convo → projects/ideaflow](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/ideaflow)
+
+- A **spark of motivation** ([[framings/sparks-of-motivation]]) lives at the personal layer.
+- Clustered sparks become an **open gestalt** — legible intent.
+- Gestalts across a team become **priorities**.
+- Priorities across humanity become **goals** (see [vision-convo → World Progress Bar](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/world-progress-bar)).
+
+## The downward flow: goals → priorities → context → decisions
+
+A civilizational goal (say, "map water-contamination crises"), once legible, can inject context into team priorities (a relief org's roadmap), which inject context into individual decisions (an activist's daily todo list). The substrate is what makes injection possible without coercion — it's just better-surfaced information.
+
+## Why a single substrate, not three products
+
+> "We are just building an übertool/dashboard/collaboration platform to house, track, and support all the thinking that happens online in really large, multi-tiered organizations … One such organization happens to be the entire planet earth's, ie Team Humanity."
+
+Building three products at three scales means three different data models, three different graphs, three different adoption curves. They don't compose. One substrate that scales up (personal → team → humanity) *does* compose — each layer's users become the humans of the next layer up.
+
+## The wedge strategy
+
+Today (2026): enterprise product at the **team** layer is the revenue wedge. Personal and collective layers are the long arc.
+
+Why team first? Because:
+- Teams pay.
+- Teams have pain (coordination, meeting notes, knowledge silos) acute enough to overcome the adoption friction.
+- A team's graph is the smallest unit that shows off the substrate's *cognition* (not just capture) properties.
+
+See [[pitches/for-investors]] for the wedge framing in pitch form.
+
+## Related
+
+- [[north-star-thesis]]
+- [[layers/personal-cognition]]
+- [[layers/team-cognition]]
+- [[layers/collective-cognition]]
+- [[framings/team-humanity]]
new file mode 100644
index 0000000..9369cfc
@@ -0,0 +1,83 @@
+---
+title: Use Cases — concrete examples
+type: concept
+visibility: public
+related:
+ - wiki/north-star-thesis.md
+ - wiki/system-map.md
+---
+
+# Use Cases
+
+Each of these is a concrete usage pattern that appeared in the `#explainingideaflow` corpus. Not theoretical; someone actually did the thing or the thing was demoed.
+
+## Personal layer
+
+### Conversation notes → knowledge base
+> "I was just helping a guy at a Founder meetup import all of his conversation notes from Sublime Text into old IdeaFlow. And I realize that there's really no tool where you can take conversation notes naturally on one side, and it builds a knowledge base for you on the other side that's awesome."
+> `#mewUseCase #explainingIdeaflow`
+
+### Contacts auto-populated from conversations
+Jacob demo, 2024-03-28:
+> "Contacts + populating by taking notes on conversations." (Draft 1 · Clean version)
+
+### Meeting notes, well-organized for the first time
+Jacob + Tejas, 2025-10-21:
+> "The first well-organized meeting notes that were ever taken in human history, because there was never a structure that could properly well-organize them before. Including connections added and citing exactly where relations were created from."
+
+### Quick capture, quick sort (mobile UX)
+Jacob, 2024:
+> "Quick capture, quick sort … mock jack's UX idea for folders on mobile (can do with tags)."
+
+### Personal KG × world KG for fundraising (Laurel Touby, 2024)
+> "If you're fundraising for your company, it could intelligently suggest the top 3 people already in your network to reach out to — based on your own knowledge base × the world knowledge graph."
+
+## Team layer
+
+### Slack-bot idea harvester
+> "Our Slack bot listens to conversations and builds a database of ideas from across the company, and suggests connections to others who have related ideas. It also can harvest the unstructured Slack information as a knowledge base."
+
+### CEO dashboard / collective brain for a company
+> "We could call our app the ultimate CEO dashboard — and collective brain for a company."
+
+### Innovation management
+Jacob, 2025 demo:
+> "For an investor who specializes in innovation management … Exploring the Innovation Management Solution: Mapping Ideas and Connections." `#InnovationManagement #demovideo #usecase` + auto-populate from meeting notes + Slack bot + personal notes app. Internal "mini-Twitter" surfaces relevant context.
+
+### Debate outlines as civic infrastructure
+Jacob, 2024-12:
+> "Time sensitive use of Mew to make a debate outline! Let's track opposing points like in here." `#explainingIdeaflow #debateoutlines`
+
+## Collective layer
+
+### Public curated lists
+> "Creating a place where we curate public lists of information that are beneficial to the world."
+
+### Alliance graph across friends' networks
+> "Export all of your networks like LinkedIn data, text contacts and email, and search it all from one place. Also get your friends to do the same and form an alliance whereby you can easily query the best intro path to anyone."
+
+### Open Supply Chains
+> "Starting the open source movement for knowledge graphs, e.g. Open Supply Chains."
+
+### Water-contamination resources (community mutual aid)
+October 2024 — Eden and others curating crisis-resource lists for hurricane-flooded Asheville, NC, using Mew as the data layer. Referenced in the same `#explainingIdeaflow` Slack window.
+
+## Adjacencies
+
+### Backend of every website
+Jacob, 2025:
+> "Some vision for mew as a centralized organized database that hosts the backend of every website."
+
+### Hypergraph store for LLMs
+Jacob, 2025-10 `#paperidea`:
+> "It helps language models … do this equipping them with a hypergraph store."
+
+### Memex / why-now
+Jacob, 2025-06 `#memex #ai`:
+> "This obscure 80-year-old machine might be the key to unlocking the full potential of AI today." `#cool #explainingideaflow`
+
+---
+
+## Rule of inclusion
+
+A use case belongs here if (a) it was actually demoed or implemented somewhere in the corpus (Loom video, screenshot, prototype), or (b) Jacob or a co-worker wrote it with a concrete setup, not just as abstract ambition. Pure ambition lives in [[open-questions]] or in framings.
new file mode 100644
index 0000000..3562d3d
@@ -0,0 +1,60 @@
+---
+title: What IdeaFlow Is Not
+type: concept
+visibility: public
+related:
+ - wiki/north-star-thesis.md
+ - wiki/canonical-terms.md
+---
+
+# What IdeaFlow Is Not
+
+A category-confusion prevention page. IdeaFlow rotates at enough angles that readers frequently assume it's *just* one of the things below. It isn't. Each of these is either a piece, a neighbor, or a non-goal.
+
+## Not just a notes app
+
+> "Like, Obsidian is very hackery and complicated. Imagine Obsidian, but optimized for quickly capturing new thoughts and with a much simpler organizational paradigm, but also power."
+
+IdeaFlow overlaps with Obsidian, Roam, Notion, Mem. But [[north-star-thesis|the thesis]] is cognition, not storage. Notes apps stop at capture. IdeaFlow keeps going: cluster, relate, surface, coordinate.
+
+## Not just voice-first capture
+
+Whisper, Willow, Otter, and friends solve *capture*. They don't do *structure*. IdeaFlow's bet is capture + clustering + graph + LLM, integrated.
+
+## Not just a knowledge graph / Semantic Web tool
+
+Enterprise KG / RDF / Neo4j solve structure — and fail at adoption because the **markup burden** on humans is crushing. IdeaFlow's why-now: LLMs do the markup. Structure without friction. See [[framings/open-source-knowledge-graphs]].
+
+## Not *only* the enterprise product
+
+The current enterprise wedge ships revenue. But the long arc is civilization-scale. Confusing the wedge with the bet leads to reading IdeaFlow as a startup with vague philosophy — or a total worldview disguised as a startup. It's both, stacked. See [[system-map]].
+
+## Not a social network
+
+> "Create an idea flow for every community."
+
+IdeaFlow has social surfaces (Slack bots, shared zones, alliance graphs), but it is not a social feed optimized for engagement. The opposite: see `empowerment algorithms` (cf vision-convo's [concepts/engagement-vs-empowerment-algorithms](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/engagement-vs-empowerment-algorithms)).
+
+## Not a chatbot / AI assistant company
+
+The LLM is a component. A very important one. But IdeaFlow is not a thin wrapper over a frontier model. The substrate *outlives* any specific LLM — that's the whole point of the graph layer.
+
+## Not a task manager
+
+Tasks, reminders, calendars can ride on the substrate. But if the frame is "better todo list," you've misread the product.
+
+## Not closed / not walled-garden
+
+> "Starting the **open source movement for knowledge graphs**, e.g. Open Supply Chains."
+
+The long arc is open. Individual nodes can be private; the substrate is designed so anyone's graph can be federated into others'. See [[framings/open-source-knowledge-graphs]].
+
+## Not a Semantic Web revival
+
+Adjacent, not the same. Semantic Web (RDF, OWL) assumed humans would hand-author structured markup. IdeaFlow assumes LLMs + UI will. The vocabulary overlaps; the adoption strategy is completely different.
+
+## Related
+
+- [[north-star-thesis]]
+- [[canonical-terms]]
+- [[framings/god-data-structure]] — maximalist framing (*"contain everything in the world"*) that could be misread as hubris