[HARD][TREASURY] Build liquidity, reserve, and solvency controls for platform funds #69

Overview

Build a treasury-control service that tracks available cash, restricted pool escrow, repayment collections, investor payables, operating reserves, refunds, and pending provider settlements.

Problem

A finance platform can show positive wallet or ledger balances while still lacking enough immediately available funds to meet refunds, payouts, and operational obligations. ChainMove needs explicit solvency checks before money-moving operations are approved.

Scope

• Define treasury buckets: available cash, restricted escrow, settlement-in-transit, investor payable, refund payable, platform reserve, fees, and suspense.
• Compute liquidity and solvency positions from authoritative financial records.
• Add configurable minimum reserve and concentration limits.
• Block or hold payouts/refunds that would breach policy.
• Support settlement delays and provider pending balances.
• Add daily treasury snapshots and variance explanations.
• Add admin-only adjustment proposals that require reason and audit history.
• Expose safe summary APIs for operations without leaking account credentials.
• Provide warning and critical thresholds consumable by monitoring and dashboards.

Acceptance criteria

• Restricted funds cannot be counted as freely available cash.
• Concurrent payout approvals cannot spend the same liquidity twice.
• Reserve breaches produce deterministic holds and audit events.
• Treasury snapshots can be reproduced from underlying records.
• Manual adjustments never mutate user balances directly.
• All monetary calculations use integer minor units.

Tests required

Cover pending settlements, restricted escrow, concurrent payout requests, reserve breaches, refunds, reversals, negative scenarios, snapshot reproducibility, and adjustment authorization.

Documentation

Include treasury definitions, formulas, policy examples, and incident procedures for liquidity shortfalls.

Difficulty

Hard