Skip to content
DigitalBrain Wiki edited this page Jul 16, 2026 · 6 revisions

DigitalBrain

DigitalBrain is a shared workspace of Neurons. Everything addressable in the product is a Neuron — Login, Chat, Gmail, Salesforce, Features, Connections, Approvals, and the Flutter destinations that show them. Humans and agents work the same brain; Flutter only projects live state.

One sentence

DigitalBrain is a personal OS where every product thing is a Neuron in one Owner/Actor workspace, agents enter through MCP as another client of that workspace, and external change only happens through prepared Effect Neurons that a human can approve.

Hard axioms (do not dilute)

  1. Everything is a Neuron — implementation traits (function, OAuth connector, LLM worker, surface projection) are how a Neuron is built, not a second taxonomy.
  2. One common workspace — no UI brain vs agent brain.
  3. Flutter = live projector — destinations are surfaces of Neurons, not a separate app domain model.
  4. MCP = same brain, different client — not a tool marketplace and not “paste external MCP URL.”
  5. Self-evolution is human-approved — new Neurons / Features enter a journaled approval rail, not free shell.
  6. Retained path (as Neurons): Client → Edge/Auth → Operation/Feature Neurons → Capability faces → Effect Neuron → Connector Neuron → Activity Neuron.

Wiki map

Page What it answers
Everything is a Neuron Why this is the product, not a slogan
The Shared Workspace Owner/Actor, one state, human + agent co-presence
Flutter as Live Surface Flutter only projects; actions bind to live Neurons
Agents via MCP How agents join the same workspace
Capabilities & Connections Connect Google/Salesforce → health → unlock verbs
Effects & Trust Prepared mutations + human approval as product
Building on DigitalBrain How new Neurons appear
What We Delete Explicit non-products
Demo Path / Proof Three product demos in plain language
Glossary Shared product language
Repo Reality What’s real today vs vision
FAQ Short answers to sharp questions
Roadmap Shape Themes, not sprint tickets

Who this is for

Founders, designers, eng, and agent users who need shared language before more machinery. This wiki shapes the product. It is not an architecture dump and not a rewrite plan.

Start here

  1. Read Everything is a Neuron.
  2. Walk Demo Path / Proof.
  3. Check Repo Reality so demos stay honest.
  4. Use Glossary when language drifts.

In one line: One workspace of Neurons; Flutter and MCP are two eyes on the same brain.

Clone this wiki locally