Trust Capital on the Balance Sheet

Finance wouldn't let you run a business on "people feel pretty good about cash." We run AI programs that way. Adoption scores. Smile sheets. A dashboard that says 87% of tickets now touch the assistant. None of that tells you whether the people who have to live with the outputs still believe you when you say the system is under control.

Trust is capital. It's built slowly, spent quickly and called at the worst possible time, usually by a journalist, a regulator or a staff member who has been quiet for months. If you can't date the last withdrawal, you're not governing. You're hoping.

Deposits are specific

A deposit isn't a town hall. A deposit is a moment when a person took a risk on your word and wasn't punished for it. In AI-enabled work, the deposits that matter look like this:

• A reviewer rejects a polished draft, names the error and is thanked in the same channel, not managed afterward.
• A leader explains a decision in four sentences they will sign, as Explainability Is a Leadership Skill requires and then lives with the sentence when it's inconvenient.
• An exception is granted to a person, not to a score and the reason is written where the next person can find it.

Deposits have dates and names. If your "trust-building" activities can't be entered on a ledger, they're branding.

Withdrawals are quieter than incidents

The dramatic failures get workshops. The withdrawals that actually empty the account are small:

• A model-shaped decision is reversed in private and left standing in the public log.
• A person who flagged a near-miss is told they're "not being commercial."
• A system is described to the board as supervised, while the supervisors are drowning in volume they can't actually read. That gap is the subject of The Human Overhead of Agentic Systems.

Each of these teaches the same lesson: the story and the practice have diverged. After three lessons, people stop bringing you the weird cases. You will still have adoption metrics. You will have lost the only feed that would have corrected the system. That's a call on the capital, whether or not you record it.

SCARF is the micro-structure of the same ledger. Status spent without acknowledgment is a withdrawal. Certainty sold ahead of accountability is a withdrawal. I mapped that terrain in The Status Threat Nobody Named, the accounting view is simply: write it down.

A one-page ledger

You don't need software. You need a page with four columns: date, event, deposit or withdrawal, who noticed. Keep it for one system, for one quarter. Rules:

1. Only events, not moods. "Team seems happier" isn't a row. "Maya refused the auto-summary and was asked to present the refusal" is a row.
2. Withdrawals can't be offset by communications. A blog post doesn't cancel a silenced reviewer.
3. The owner of the ledger is a named leader, not "the AI working group."
4. Once a month, read the last six rows out loud in the room that thinks it's in charge.

You will hate the first month. The page will look sparse, then suddenly not. Sparse is a finding: you're not close enough to the work to see trust move. Sudden density is also a finding: you're in a drawdown and have been reporting stability.

Calls

A call is when someone outside the cozy circle asks you to prove the account is real. Board. Regulator. Injured staff member. Journalist. You can't produce a feeling. You can produce a ledger with dates, names and stop conditions.

If you have been managing sentiment, the call will feel unfair. It's not. You asked people to rely on a system. Reliance is a credit relationship. Credit relationships get audited.

This is why I'm uninterested in "trustworthy AI" as a product adjective. Trustworthy is a claim you make about your practice. The system doesn't hold the account. You do. The human remains the moral agent of the credit.

What this isn't

It's not a fairness audit of a dataset, and it's not a stakeholder map. Those are neighboring instruments. They answer different questions. The ledger answers: have we been good for the word we gave our own people about this system? If that answer is no, no amount of model documentation will hold when the call comes.

Metrics That Actually Bite is the measurement companion: dissent latency, exception ownership, first-voice ratio. The ledger is where those numbers become a story a leader can tell without lying.

This week

Open a blank page. Title it with the name of one live system. Enter three deposits and three withdrawals from the last sixty days. If you can't find three of either, you're too far from the work or the account is already empty and nobody has said so.

The Ethical AI Leadership Decision Toolkit treats trust as something you can operationalize before the call arrives. The biweekly notes in EI Leadership Insights are how the practice stays in motion.