[[
wikihub
]]
Search
⌘K
Explore
People
For Agents
Sign in
Explore
People
For Agents
Sign in
@jacobcole / IdeaFlow Vision / wiki/system-map.md
Suggest edit
Cancel
Submit suggestion
Title
Name
Note
--- 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]]