Suggest edit — What IdeaFlow Is Not

Title

Name

Note

---
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