Module M2

M2 • Tokenized Treasury Ops

Run enterprise day‑2 operations for tokenized treasuries: recon, exceptions, SLAs, and evidence exports.

← Previous Take Quiz Mark Module Complete Next →

Track

—

Progress

1) Outcomes & timebox 2) Core concepts 3) Trust boundaries & controls 4) Evidence & proof artifacts 5) Mini case study 6) Worksheet (download)

Outcomes & timebox

Enterprise grade = clear outputs

By the end you can

Explain the enterprise operating model for tokenized treasury ops
Identify control points, owners, and escalation paths
Define evidence outputs that satisfy enterprise review
Produce a reusable artifact template for your Proof Pack

How to use this module

Read the tables, then complete the scenario + worksheet. Download the artifact to your delivery repo.

Enterprise test If a bank asked “show me,” you can hand them controls + evidence + runbook steps within 10 minutes.

Core concepts

Vocabulary + enterprise expectations

Operating model

What “good” looks like

Area	What you run	Common failure	Required control	Evidence output
Recon	Expected vs actual positions	Custodian mismatch	Daily recon + owner	Recon report (daily)
Exceptions	Non-standard cases	Queue overflow / stuck cases	Severity + SLA routing	Exception log + resolution notes
SLAs	Response and resolution targets	Missed response times	On-call + escalation	On-call timeline + postmortem
Evidence exports	Audit packages	Missing/invalid logs	Scheduled exports + checks	Export hashes + retention proof
Operations cadence	Daily/weekly routines	Drift, forgotten tasks	Checklist + automation	Checklist completion record

Turn each row into: owners → controls → monitoring → evidence.

Roles

Who owns what

Operator on-call

Owns monitoring, exceptions, recon, incident response, and daily evidence exports.

Custody liaison

Coordinates with custodian/broker; validates mismatches and settlement issues.

Compliance reviewer

Validates evidence packet completeness and retention policy alignment.

Clarity closes deals Ambiguous ownership = buyer assumes risk = approval stalls.

Trust boundaries & controls

Where enterprise risk actually lives

Boundaries

Boundaries you must control

Boundary A: Dashboard → Decisions

Operators need one source of truth with ownership and escalation.

Evidence: Runbook + owner list + escalation tree

Boundary B: System → Custodian

Mismatch handling and confirmation loops.

Evidence: Recon diff + custodian confirmation + resolution audit trail

Boundary C: Ops → Reporting

Evidence must be buyer-safe and consistent.

Evidence: Evidence export schedule + retention policy + integrity checks

Minimum control set

Controls you must be able to prove

Daily recon with signed-off owner
Exception queue with severity + SLA timers
On-call escalation policy + paging
Evidence export schedule + integrity checks (hashes)
Change control for ops config (limits/alerts)
Postmortems for SLA breaches

Buyer question “If this breaks at 2am, who sees it, what do they do, and where’s the evidence?”

Evidence & proof artifacts

What makes enterprise buyers trust you

Proof artifacts

Add these to your Proof Pack

Daily Ops Checklist (tick list + owner)
Exception Taxonomy (severity + SLA + routing)
Recon Report Template (expected/actual/diff/resolution)
On-call Escalation Tree (contacts + rules)
Evidence Export Schedule (what, when, where retained)

Evidence rule

Evidence must be time-bound, attributable, and reviewable — without leaking private keys or customer PII.

Template

Downloadable artifact

Complete the worksheet below and download a Markdown file to your repo.

Mini case study

Enterprise thinking in 10 minutes

Scenario

Exception queue surge (end of month)

Exception volume triples and SLA timers begin expiring. The buyer asks: “How do you prevent backlog, prioritize, and prove resolution?”

Your response must include

Severity routing + SLA timers
Temporary controls (rate limits / throttles)
Escalation + staffing plan
Evidence export impact
Postmortem trigger conditions

Write your ops response

Write 6–12 lines you could hand to an enterprise buyer.

Download as .md

Optional, but it turns training into a deliverable.

Worksheet

This becomes your capstone foundation

Fill & download

Fill the fields and download the artifact for your Proof Pack.

Daily ops checklist (10 bullets) Exception severity + SLA table Evidence export schedule

Download Artifact →

What “enterprise grade” means

Not statements — outputs

Every module produces an artifact: checklist, runbook section, control matrix, or proof pack component.

Measurable gates

Quizzes + capstone + exam. Completion is earned by passing gates.

Repeatable delivery

Templates, owners, SLAs, and evidence. That’s what closes enterprise deals.

Take M2 Quiz → Next Module →