Ledger. Every commitment the office makes — tracked, owned, aged.
Every promise the office makes — caught in the meeting, owned by a person, aged until closed.
The shift
Before Ledger, and after.
Same office, same people — different operating posture.
Before
- — Half the room left a meeting owing something. Nobody wrote it down.
- — You learn a commitment slipped when the board asks.
- — Owners change; commitments don't follow them.
After
- — Every commitment surfaced from meetings and email.
- — An owner, a due date, a status — visible to the office.
- — Slippage flagged before it becomes a surprise.
How it runs
The Ledger workflow.
A short loop the office actually runs every day.
Step 01
Capture
Extracts commitments from meetings, mail, and decision packs.
Step 02
Assign
Routes to an owner with a due date and escalation rule.
Step 03
Age
Surfaces what's slipping; nudges before it breaks.
Inputs · outputs · artifact
What goes in, what comes out.
Inputs
- Meetings & email promises
- Manual entries
- Decision packs
Outputs
- Open commitments
- Owner accountability
- Slippage alerts
Sample · Commitment
Promise: send variance walk to board
Owner: CFO · due tonight · status: in progress.
Trust posture
The same approval gate as every other module.
Helm never sends, schedules, or commits anything externally without an explicit office decision. Every action is logged in Verdict with diff and approver identity.
Approval-gated execution
Tamper-evident audit
Customer-owned memory
Works with
Modules that pair with this one.
Close the loops