The SeaShell Decision Ledger tracks decisions in 2 states: open, meaning a decision you still need to make, and settled, meaning one you made along with why. Its headline job is surfacing the open decisions you forgot were pending, oldest first, so a question that was quietly blocking progress actually gets decided. Settling one writes an ADR file into your repository and injects it into future sessions so the agent does not re-argue it. The engine ships today behind the paid tier, and SeaShell Pro is not yet on sale.
The decisions that hurt are the open ones
The costly decisions are not the 1 you made last week, they are the ones you needed to make and forgot were open.
The Decision Ledger keeps open decisions visible and aging-aware, ordered oldest first, so a question raised on a call does not stall the work indefinitely. The ordering matters: a digest sorted by recency shows you what you already remember, while one sorted by age shows you what you forgot.
Settled decisions keep their reasons
A decision without its rationale gets re-argued within 2 months; a recorded one does not.
When you settle a decision, SeaShell captures the outcome and the reasoning and writes it to decisions/NNNN-slug.md in your repository as an ordinary git-tracked ADR. The file is yours and readable without SeaShell. Settling is idempotent, so a decision you confirmed never silently flips on a later pass.
Settled decisions reach the agent, open ones do not
Only settled decisions are injected into session context, and that 1 rule is a deliberate safety property.
SeaShell renders settled decisions into the system prompt so the agent works from what you already concluded. Open decisions stay out. That way an unresolved or wrongly captured question stays visible in your digest without silently steering every future session in the repository.
Availability
Decision Ledger is 1 of the 8 record engines in SeaShell, and it sits behind the paid tier.
The engine is built and running in the product, gated to SeaShell Pro. Pro has no checkout yet, so it is not something you can buy today. Its live input is Intake, which reads call transcripts. Capturing decisions from coding sessions is built as a separate engine but is deliberately manual for now. Shipped, the automated work log, is the one record engine available free right now.
Frequently asked questions
- Is SeaShell decision tracking available now?
- The engine is built and running in SeaShell, but it sits behind the paid tier and SeaShell Pro is not yet on sale, so you cannot purchase access today.
- How is this different from a decision log?
- A log only records decisions you already made. The Decision Ledger also tracks open decisions you still need to make, ages them, and surfaces the oldest first.
- Where do the decisions come from?
- From the decisions SeaShell Intake extracts from your call transcripts. Capturing decisions made during a coding session is built as a separate engine but is manual rather than automatic today.
- What happens when I settle a decision?
- SeaShell writes an ADR to decisions/NNNN-slug.md in your repository with the outcome and rationale, flips the ledger entry to settled, and starts injecting it into session context.
- Do open decisions affect what the agent does?
- No. Only settled decisions are injected into context. An open or wrongly captured decision stays visible in your digest without steering the agent.
Try SeaShell in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install SeaShellRelated guides
Atlas with Llama 4 Scout (Ollama) in 2026
Explore Llama 4 Scout (Ollama) for Atlas in 2026. This free, self-hosted model offers a 10M-token context window and native multimodal capabilities for advanced AI coding.
Atlas vs Fine.dev: Terminal AI Coding Agents in 2026
Atlas and Fine.dev offer distinct AI coding agent workflows for 2026. Atlas provides a terminal-native TUI with permission-gated tool calls, while Fine.dev focuses on asynchronous cloud-based agent execution and PR
Atlas with Qwen3.6 27B in 2026
Explore Atlas with Qwen3.6 27B, the dense 27B reasoning model from Alibaba. Leverage its 256K token context for large code rewrites and consistent agent behavior in 2026.
Atlas with Qwen3.6 Plus in 2026
Drive Atlas with Qwen3.6 Plus, offering a 1,000,000 token context window for deep code understanding. Priced at $0.50 per Mtok input, it's ideal for complex reasoning tasks in 2026.
Atlas with Amazon Nova Pro in 2026
Explore Amazon Nova Pro with Atlas in 2026. This model offers a 300K token context window and cost-effective pricing, integrating direct with your AWS account for developer workflows.
Atlas with Qwen3-Coder 480B (Ollama) in 2026
Drive Atlas with Qwen3-Coder 480B (Ollama) in 2026 for a powerful, self-hosted AI coding agent. Leverage its 256K token context window and 290GB weights for zero data egress.
Atlas with GPT-5.3 Codex in 2026
Explore GPT-5.3 Codex with Atlas, the terminal-native AI coding agent. Optimized for agentic software engineering, it offers a 400K token context and surgical edits for $1.75/Mtok input.
Atlas with Qwen2.5 72B (local via Ollama) in 2026
Explore Atlas with Qwen2.5 72B (local via Ollama) for fully air-gapped, free AI coding. Leverage its 32,768 token context window for secure, self-hosted development in 2026.