§6–7. Concept, Implementation, Boundaries
§6. Concept vs. Implementation
Mind Extended exists at two distinct levels:
| Level | Domain | What it is | Where it lives |
|---|---|---|---|
| Framework (mind-extended.org) | Concept / Spec | The definition of what an extended mind is. Components, pillars, scale model, principles. Guides possible implementations. | This repo + mind-extended.org website |
| Implementation (e.g. super-mind.app) | Product | A concrete implementation of an extended mind. Makes specific choices about stack, UI, data model, and which scales to operationalize. | Repo: super-mind-app (and potentially others) |
The analogy: the framework is an architectural specification. An implementation is a building constructed according to that specification — with its own design, materials, and context, but sharing the same structural principles.
What the spec defines
- • What an extended mind is and what it is not
- • The three pillars (Memory, Access, Action) and how they interrelate
- • The components that constitute an extended mind
- • The scale model: how the pillars apply at agent, organization, ecosystem, and topology scales
- • Principles and constraints that any implementation should respect
What implementations decide
- • Tech stack (Next.js, Supabase, SQLite, etc.)
- • UI/UX (conversational, visual, hybrid)
- • Data model (tables, schemas, file formats)
- • Deployment (local-first, cloud, hybrid)
- • Which scales to operationalize first
- • Specific access channels and protocols
§7. What Mind Extended Is Not
- Not a product. super-mind.app is a product. Mind Extended is the conceptual framework it implements.
- Not an app. It’s a specification — a set of definitions and principles.
- Not a project management system. Projects are one of many components. Writing, learning, relationships, identity, and agent coordination matter equally. An implementation may include project management features, but the framework itself is about cognitive extension, not task tracking.
- Not static. The spec evolves as understanding deepens. Version 2.0 is a starting point, not a destination.
- Not a replacement for thinking. The system extends what its operator can think, not replaces what they should think. Agents are partners, not substitutes. (“Extended cognitive hygiene” — Clark, 2025.)
It IS:
- • A conceptual framework for cognitive extension
- • A definition of what an extended mind consists of and how it operates
- • The answer to: “If the Extended Mind Thesis is true, what would a well-designed extended mind actually look like?”
Full specification
The complete Mind Extended specification (v2.0) is maintained as a markdown file in the source repository.