Beta Coming soon. This feature is still being built, so names and details may change before it ships.

Decision Ledger

The Decision Ledger is a short list of what you and the agent have agreed on, such as use Zod for request validation or keep prices in cents. Locked decisions are checked before every edit and plan, so a later run, or a brand-new chat, doesn't quietly undo them.

Turn it on

  1. Open Settings › Tools › Game changers.
  2. Turn on Decision Ledger.
SettingDefaultEffect
ingot.decisions.enabledoffrecord decisions and check them before edits and plans
ingot.decisions.autoCaptureonlock a decision when you confirm a choice in the chat
ingot.decisions.promoteAfter3confirmations before a decision is offered as a habit

Lock a decision

From the chat

When you confirm a choice the agent offered, the agent records it for you:

Agent: Should request validation use Zod or the hand-written checks in lib/validate.ts?
You:   Zod. And keep the error format we already return.

The agent writes the decision to .ingot/decisions.md and a note appears under its reply:

Locked in Decisions

Click the note to open the entry. If it got the wording wrong, edit it there or choose Unlock.

By hand

  1. Run Decisions: Lock a Decision… from the command palette.
  2. Type the decision in one line, for example Prices are stored in cents as integers.
  3. Add why (optional). The reason helps the agent judge whether a change really goes against it.
  4. Press Enter. The decision is saved as locked.

Run Decisions: Show Decisions to see the whole list with a Lock / Unlock switch on each entry.

What happens before an edit

Before the agent applies an edit or starts on a plan, it compares the change with every locked decision. If the change would go against one, it stops and asks first:

This change goes against a locked decision:
  "Use Zod for request validation" (locked Oct 30)
Planned edit: replace the Zod schema in api/orders.ts with manual checks.
ChoiceResult
Keep the decisionthe agent drops that edit and looks for another way
Unlock and continuethe decision is unlocked and the edit goes ahead
Allow oncethe edit goes ahead; the decision stays locked

Unlocked decisions stay in the file as history, but the agent no longer checks them.

The file: .ingot/decisions.md

The ledger is a plain Markdown file. Commit it so everyone's agents follow the same decisions.

# Decisions

## Use Zod for request validation
- Status: locked
- Since: 2026-10-30
- Why: one schema gives us both the types and the runtime checks
- Confirmed: 2

## Prices are stored in cents as integers
- Status: locked
- Since: 2026-10-28
- Why: floats caused rounding bugs in invoices

## Use Redux for app state
- Status: unlocked
- Since: 2026-09-12
LineMeaning
## …the decision, in one line
Statuslocked (checked before edits) or unlocked (kept as history)
Sincewhen it was locked
Whyoptional reason, shown when the agent asks
Confirmedhow many times you confirmed it again

You can edit the file by hand; changes apply from the next request.

Decisions become habits

When you confirm the same decision again and again (3 times by default), Ingot offers to make it a habit so it guides the agent's work in that area, not only its edits. Choose Make it a habit and the habit is written to .ingot/habits/:

Saved to Habits

Silver notes

NoteWhen
Locked in Decisionsa decision was added to .ingot/decisions.md
Saved to Habitsa repeated decision became a habit