Smart Contract Treasury

Learning objectives

• Explain the main treasury decision that Smart Contract Treasury is designed to support.
• Use Treasury scenario, Enable AI monitoring to test how different assumptions change the scenario.
• Interpret Output: Approval Queue in plain language and connect them to an action or conclusion.
• State one limitation, risk, or governance consideration before using the result in a real decision.

Run modes

• Supported modes: Browser
• Demo type: Interactive browser demo
• Primary launch surface: index.html

Before you start

Starts immediately in browser with no installs, no API keys, and classroom-safe defaults.

This helps set classroom expectations before students click into the live experience.

Core context

Look for treasury rule, smart-contract condition, approval flow, and transaction outcome.

Observe how automated controls reduce manual risk and where human override is needed.

Concepts covered

What students should note

Note that smart contracts are powerful controls only when rules, audits, and exceptions are clear.

List of steps

• Choose the run mode that fits the class: Browser.
• Review the default assumptions before changing anything.
• Change one or two inputs, then use `Submit Transaction`.
• Read Output: Approval Queue first, then compare any supporting metrics, charts, or AI text.
• Capture one insight, one limitation, and one action recommendation.

Input variables explained

• `Treasury scenario` changes one part of the scenario; increase or decrease it deliberately and watch how the output shifts.
• `Enable AI monitoring` changes one part of the scenario; increase or decrease it deliberately and watch how the output shifts.
• `Recipient wallet or vendor` changes one part of the scenario; increase or decrease it deliberately and watch how the output shifts.
• `Amount` changes one part of the scenario; increase or decrease it deliberately and watch how the output shifts.
• `Token` changes one part of the scenario; increase or decrease it deliberately and watch how the output shifts.

Decision buttons explained

• `Submit Transaction` runs the policy checks and shows whether the treasury instruction is approved, warned on, or rejected.
• `Reset` returns the payment scenario to a clean baseline.
• `Export Snapshot` saves the transaction state and control outcome for audit or classroom review.

Outputs explained

• `Output: Approval Queue` should be read as evidence for the decision, not just a display element. Ask what high, low, or changing values imply.

What to notice

• The interesting learning moment is not only whether the transaction passes, but which control caused the decision
• Use AI monitoring as an explanatory layer, not as a replacement for explicit treasury policy rules
• Discuss where human override is appropriate and where automation should stay strict

Discussion and reflection

• What business or technical decision would you make differently after using Smart Contract Treasury?
• If you changed one assumption and ran `Submit Transaction`, which output moved the most and why?
• What would you still want to validate with real data, policy, or expert review before acting on the result?