Home

Deep Dive

Why it's built this way.
The README tells you what dreamcontext does — the layer where you, your team,
and your agents all see the same big picture. This document tells you why it is built
the way it is: the philosophy, the neuroscience, and every design tradeoff, argued honestly.

---

The story

• Why It Exists — the two-directional wall this tool answers
• The Problem in Depth — eleven problems, and what each became

The memory engine

• Architecture — the brain-region file layout
• The Hook Mechanism — seven hooks, zero tool calls
• The Sleep Cycle — consolidation, debt, the specialist fan-out
• Neuroscience-Inspired Memory — the research the design borrows from
• Memory Recall — BM25 over the curated corpus, and the hybrid layer

The surfaces

• The Dashboard — including the security model
• Project Task Overrides — your task format, enforced and briefed
• Council Debates — multi-persona decisions
• Lab (Insights) — curated metrics in the brain
• Automations — scheduled headless runs that learn
• The Desktop App — one window, every project
• Obsidian Integration

The team layer

• Brain Cloud Sync — one brain, whole team
• Federation — live read across projects
• Linked Repos — governing bare code repos

The craft

• CLI Design — CLI for structure, native edits for content
• Install & Update — one command, no stale docs
• Design Tradeoffs — what was chosen, over what, and why
• Release History — how it got here, and what comes next