The Context Map

Every innernet project is a Context Map — a structured world model the AI maintains on your behalf. It has three primary layers.

Dimensions

Long-form markdown documents. Free-form, named per project. Common names: vision, product, roadmap, technical, decisions, brand, voice. The names are emergent — they reflect what this project needs to remember, not a fixed schema.

A dimension grows over time. The AI re-reads it on load and re-writes it on save, consolidating new captures into the existing prose rather than appending endlessly.

Nodes

Typed structured entities. Today: person, artifact, concept, decision, project, stakeholder. Each node has an id, a type, and a JSON content blob shaped to its type.

Nodes are for things that need a stable identity across dimensions — a person referenced in vision and again in stakeholders is one node, not two strings.

Commits

Append-only history. Every save, capture, or branch operation adds a commit with a hash, parent hash, summary, and trigger (genesis, manual, sync, mcp, etc.). This is what makes innernet versioned — you can read what happened, when, and why.

Branches

A fork of the entire Context Map at a commit. Use branches to explore a divergent direction (a different positioning, an alternative architecture) without losing the trunk. park archives, mergerejoins.

Why this shape

Other tools (Notion, Mem, Obsidian, Claude Projects) treat memory as flat notes you maintain manually. innernet separates the maintenance loop (the Sync Agent consolidates) from the storage (dimensions + nodes + commits). The AI does the upkeep, you do the thinking.