How rememd is organised
Four levels, and one rule about which way things move between them. Everything else in rememd is a consequence of this.
Context is attached to work, not to a folder
The thing rememd stores is not "what is in this directory". A feature can span four repositories, and a repository can carry work from three features. So the unit is the work, and a terminal says which work it is on by connecting to it.
That is why rememd connect takes a product and a feature rather than a path, and why it runs from anywhere. The folder you are in supplies a default and nothing more.
The ladder
Four levels, widest at the bottom. Each one outlives the one below it, which is the whole point — a feature ends, and what it taught should not end with it.
| Level | What it holds | Lifespan |
|---|---|---|
| Workspace | Everything one person or team works on, and the conventions that hold across all of it. | Permanent |
| Product | One thing you are building. Its vision, and the knowledge distilled from every feature that finished. | Years |
| Focus area | A component of that product — not a theme. “Storage and sync”, not “performance”. | Months |
| Feature | A PRD, its tasks, its notes, its diagrams, and the log of every session spent on it. | Days to weeks |
Things move up, and only when they are finished
Sessions attach to a feature. When the feature is done, what it taught is promoted — to the focus area if it is about that component, to the product if it holds across all of them, to the workspace if it is true of how you work rather than of what you built.
The default is the focus area, deliberately. A product document that receives everything stops being knowledge and becomes a dumping ground, and the next agent reading it cannot tell the load-bearing lines from the incidental ones.
A session is what an agent reads first
Every terminal bound to a feature has a session. It accumulates what happened, and the next agent — tomorrow, or on another machine — starts by reading it rather than by asking you to explain again.
Sessions receive logs; features receive intent. A log says what happened; a note, a task or a PRD edit says what should happen. Putting the second kind in a session log is how a decision gets lost, because the next write on that session replaces the body.
Seeing it
The menu bar shows the whole ladder as a tree. From a terminal:
rememd connect # pick in the menu bar
rememd where # what the current folder resolves to
rememd ls features # what is on the go