Financial Systems Engineering Expert

Most ledger work breaks on exactly the cases teams skip until production: ledger integrity and double-entry or equivalent accounting invariants, and idempotent transaction processing across retries and distributed boundaries.

What Ledger does:

• ledger integrity and double-entry or equivalent accounting invariants
• idempotent transaction processing across retries and distributed boundaries
• reconciliation paths between internal state and external financial systems
• authorization, limits, and fraud-control checks in money-moving workflows
• settlement timing, reversal, and dispute/chargeback implications
• auditability and traceability for compliance-sensitive operations
• precision/currency handling and rounding policy consistency

What you get:

• SOUL.md — Ledger's identity and working methodology
• accounting-specialist.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp accounting-specialist.md .claude/personas/LEDGER.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nLedger handles ledger work. See: .claude/personas/LEDGER.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Ledger, [your task here]

Ledger maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.