Decision graph tooling for AI-assisted development.
Track every goal, decision, and outcome. Survive context loss. Query your reasoning.
Work smarter with careful rigor.
LLMs generate complex code fast. Reviewing it, understanding it, and maintaining it? That's on you. Deciduous gives you a structured record of every decision—what was considered, what was chosen, and why. No more losing institutional knowledge when context windows reset.
Claude (and LLMs generally) lose context. Sessions end, memory compacts, decisions evaporate. Six months later, no one remembers why you chose approach A over approach B.
Deciduous solves this by tracking every decision in a queryable graph that persists forever.
High-level objectives
Choice points with options
Approaches considered
What was implemented
What happened
Technical insights
Every PR in this repo includes its decision graph. Here are some examples:
#11 Type Unification: TUI + Web with Enforcement Tooling 14 tracked decisions. JSON Schema as canonical source, validation scripts, git hooks, CI enforcement. Full decision tree in PR body. #3 Multi-User Graph Sync jj-inspired diff/patch model for sharing decisions across developers. UUID-based change_ids survive across databases. #9 TEA Architecture Refactor Functional core refactor of TUI using The Elm Architecture. Architectural decisions tracked throughout.Watch a full session building with deciduous: initialization, decision logging, graph visualization, and context recovery.
Deciduous was extracted from losselot, an audio forensics tool that grew into an experiment in AI-assisted development.
The core insight: LLM sessions lose context, but the decision graph survives. Every goal, every rejected approach, every "why did we do it this way?" is preserved and queryable.
This isn't documentation written after the fact. It's a real-time record of how software gets built—captured as decisions happen, not reconstructed from memory later.
Deciduous is built exclusively using deciduous. Every feature, every bug fix, every architectural decision is tracked in its own graph.
Browse the live graph to see 340+ decisions from the development process.