Decision Ledger

The append-only list of business decisions: what is recorded, how it is captured and how to use it.

Decision Ledger

The Decision Ledger is the running record of the business decisions your team makes in a module. Every time someone approves a suggestion, rejects it, edits it, overrides a rule or closes a result, one entry is added. The entry says what was decided, who decided it, under which role, when, and, if they wrote one, why.

It is append-only. Entries are never edited or deleted; a correction is a new entry that points to the old one, so the history of a decision is never rewritten. That is what makes the ledger trustworthy in an audit and useful when you want to understand how a decision was really made.

The ledger is the raw material for the rest of Enterprise Mind. Recall searches it, Outcome Learning compares it with results, and the autonomy ladder uses its acceptance numbers to decide when a class has earned more trust.

At a glance
Where to find it	Decision Ledger, in every module where Enterprise Mind is switched on
Who can read it	Staff who hold a role in the module; internal and sensitive details follow data-class rules
Who can change it	Nobody. Entries can only be added or superseded
How long entries stay	Until the retention period set for their data class ends (see Memory)
Export	Filtered views can be exported as a spreadsheet file by module administrators

Using the screen

Filter by entry type (approvals, overrides, outcomes, calls), by person or role, by action class and by date.
Open an entry to see the reason, the evidence that was on screen at the time and the record it belongs to.
Follow the link from a decision to its outcome, or from an outcome back to the decision that led to it.
Search by phrase to find every decision where someone mentioned, for example, "mountain route".

Why keep a ledger at all

Onboarding. New colleagues learn how decisions are made by reading real ones.
Audits. "Who approved this, and why?" has a one-click answer.
Learning. Overrides and rejections show where suggestions and rules need work.

app.totalapp.app/enterprise-mind/ledger

Decision Ledgerappend-only

AllOverridesOutcomesCalls

MRM. ReedAPPROVED09:12

Hospitality · T-118 · add one cleaner

“Check-in is at 15:00, the last two Fridays ran late.”

KBK. BrooksOVERRIDE08:47

FleetOps · WO-2041 · interval 40k to 30k km

“Mountain route wears tires faster.”

SsystemOUTCOME08:30

RevOps · Atlas Hotel renewal

“Won after discount call. Predicted 62%, actual won.”

VAVoice agentCALL08:02

Booking for 2 nights, late arrival noted

“Guest asked for a quiet room.”

Entry type	Recorded when	What is kept
Approved	An approver accepts a suggestion.	Who, role, the reason text, the evidence shown
Override	Someone changes a value a rule or suggestion proposed.	Old value, new value, reason
Outcome	A task closes, a deal is won or lost, a check passes or fails.	Result, time to close, link to the original decision
Call	A voice call ends.	Summary, language, extracted preferences, follow-ups

Every entry keeps two times: when it happened and when it was recorded. That is what lets Recall answer what was known on a given day.

How decisions are captured

Command Centers and screens report decisions through shared settings; nothing is added screen by screen.
When a person rejects or edits a suggestion, a reason field appears. The reason is optional but is the most valuable thing to write.
Only business decisions are recorded. Browsing, searching and screen time are not.

Role-level learning

Administrators can choose to record the role instead of the person, so the engine learns how a role decides without keeping individual names.

Related pages: Memory · Recall · Outcome Learning