A REPOSITORY, WITH ITS REASONS
Follow the decision.
Start with a problem. See the choice it led to, then follow the work that implements it. Select a record to look inside.
PUBLIC SAMPLE / READ ONLY
No account. No repository upload.
01 / SELECT A RECORD
- ← solves
- implemented_by →
02 / decision / e5dec61c
Keep decisions with the repository
- alternatives
- Leave the rationale in chat history
- Maintain a separate hosted knowledge base
- chosen
- Store a small, linked evolution graph in .evolution/
- rationale
- The reasoning should travel with the code, remain readable without a hosted service, and be available at the start of the next session.
- status
- in-progress
- problem
- Context disappears between sessions
- Expected outcome
- The next session can follow the original problem and chosen approach before making a change.
- Follow a relationship
=== ECS CONTEXT === CLI version: 0.1.2 ## Problems - 969872e6 [medium] Context disappears between sessions (969872e61b35446c79603ee42b65237e745464440be0d9ead0db7cfc709ab36b) ## Decisions - e5dec61c [in-progress] Keep decisions with the repository → Store a small, linked evolution graph in .evolution/ (e5dec61cb348009c91e2439f4747891de54add40456f4a8dee641fbd5e7315fe) ## Recent decision graphs (limit 5) ### Keep decisions with the repository (e5dec61c) decision: Keep decisions with the repository (e5dec61c) │ solves ▼ problem: Context disappears between sessions (969872e6) │ implemented_by ▼ change: change object (47f62d37) === END ECS CONTEXT ===
Real records. A sample story.
These five objects were generated with the published CLI, version 0.1.2. The problem and decision use ecs close-session; the sample worktree change uses the same domain APIs as the CLI’s interactive Git linking flow. Timestamps are normalized for reproducibility.
The panel shows actual ecs context output. The browser selects existing records and follows their edges locally. It does not run the CLI or an AI model.
Make a record of your own.
The CLI stores your graph in your repository’s .evolution/ directory. Record one decision, link it to its problem, and load it before your next coding session.