The code changed.
Keep the why.
Your commits tell you what happened. Evograph keeps the problems, decisions, and reasoning that got you there.
npm install -g @evograph/cliA local CLI. Plain files. Yours to keep.
Node.js 22.12+ recommended · Early release
01Why did we choose
this architecture?
02Keep the context
with the code.
03A decision you can
trace to its outcome.
next person.
Or the next agent.
You inherited the code.
Where’s the reasoning?
A rejected approach. A tradeoff made under pressure. The constraint behind an unusual implementation. These details rarely survive in the diff.
Evograph gives them a place: small, typed records linked to the problem they solve and the changes they inform. Commit them with your project and pick up the thread later.
Leave a trail.
Follow it next time.
- 01
Name the problem.
Write down what needs to change, while the context is fresh.
ecs create problem - 02
Record the decision.
Keep the chosen approach, the alternatives, and your rationale.
ecs create decision - 03
Connect the work.
Link the decision to its problem and the changes that implement it.
ecs link - 04
Pick up the thread.
Read the graph yourself, or load its context into a coding session.
ecs context
Give your agent
some history.
A fresh chat shouldn’t have to rediscover every decision. Evograph can scaffold instructions that ask coding agents to read your graph at the start of a session and record decisions at the end.
Instruction-based integration today. Follow-through depends on the agent; it isn’t enforced by hooks.
Set up your coding agent ↗$ ecs context === ECS CONTEXT === ## Problems Context disappears between sessions ## Decisions Keep decisions with the repository → Preserve the rationale, not just the diff ## Recent decision graphs decision: Keep decisions with the repository │ solves ▼ problem: Context disappears between sessions === END ECS CONTEXT ===
Make the next change
with the last one in mind.
Install the CLI, open a repository,
and write down the reason.