Agentic Treasury Micropayment Rail
Operational brief for DAO-controlled micropayment batches, showing how approved policy becomes batched stablecoin settlement with judge-visible runtime proof and telemetry continuity.
Document context
Operating brief only; it now frames Devnet material as historical rehearsal evidence and points operators to the current Testnet proof path without claiming production stablecoin settlement closure.
Audience: Judges, funders, operators, builders
Open raw fileAgentic Treasury Micropayment Rail
Purpose
The Agentic Treasury Micropayment Rail turns one approved treasury instruction into many small settlement events without breaking the PrivateDAO control story.
This rail is designed for:
- reviewer rewards
- operator task settlement
- per-action API payouts
- gaming or tournament reward batches
- future agent commerce where each approved action settles small value on-chain
Why it exists
PrivateDAO already handles:
- proposal lifecycle
- private vote flow
- governed execution
- proof and reviewer telemetry
The missing layer was a high-frequency settlement rail that can fan out from one approved policy into many small payouts while staying easy to audit.
This rail closes that gap.
Operating model
- signature
- explorer link
- batch index
- action label
- recipient
/services/govern/judge/analytics
- A treasury or service request is prepared with the
agentic-micropayment-railprofile. - The request keeps the route, quote posture, destination asset, and reviewer path inside the same payload.
- After approval, an execution agent can trigger a batch of low-value payouts.
- Every transfer is recorded with:
- The same batch can be reviewed from:
Asset model
The rail is stablecoin-ready by design.
- When a stable settlement mint is configured, the rail can execute through SPL token transfers.
- When no stable settlement mint is configured in the current environment, the runner falls back to native SOL on Devnet so the execution rail remains testable and reviewer-visible.
This keeps the feature operational today without pretending a stablecoin mint is already configured.
Proof surface
The live execution batch writes machine-readable evidence to:
docs/agentic-treasury-micropayment-rail.generated.jsondocs/agentic-treasury-micropayment-rail.generated.md
Those artifacts are intended to show:
- total transfer count
- successful transfer count
- settlement asset mode
- total amount settled
- execution wallet
- per-transfer signatures and explorer links
Judge-first reading
The judge path is simple:
- Open
/judge/ - Inspect the agentic micropayment rail panel
- Open transaction links on Solana Devnet
- Verify that one governed treasury feature is producing many real settlement events
Production intent
This rail is not a standalone payments demo.
It is a PrivateDAO execution feature:
- governance-controlled
- treasury-aware
- proof-linked
- reviewer-visible
- suitable for future agentic commerce and usage-based settlement
Related next docs
Shortest reviewer path across live proof, V3 hardening, trust links, and launch boundary surfaces.
Generated reviewer-visible route into telemetry, hosted reads, runtime evidence, indexed governance, and the infrastructure value layer behind PrivateDAO.
Capital-facing packet tying product, services, trust, and release-path truth together for accelerator and grant reviewers.