MANAGE TREASURY
Grow Track — Step 3
FORGE LABS — EXPERIMENTAL PROTOCOL
Treasury is real, powerful, and operational inside the Forge. But connecting it to the outside world — ad platforms, bank APIs, live dashboards — requires your engineering.
API keys. Platform accounts. Debugging skills. Extensions required. Here be dragons.
WHAT IS FORGE LABS? →Every boxing counts. I track revenue from Stripe, Paddle, and Mercury. I allocate budgets across ad channels. Steris runs forecasting models so we know what we can spend before we spend it. And if anything looks wrong, I freeze everything in one command. The books always balance.
DocksonWHAT THE TREASURY DOES
The Treasury is VoidForge's financial nervous system. It ingests revenue from your payment processors, allocates budgets to growth channels, and runs daily reconciliation to make sure every dollar is accounted for.
Steris handles forecasting — projecting runway, estimating ROI on proposed campaigns, and flagging when spend rates will exceed revenue thresholds. You always know where you stand before committing funds.
/treasury --reportGenerate a full financial report: revenue by source, spend by channel, net position, and Steris's 30-day forecast. Outputs to the build journal for audit trail.
CONNECTING REVENUE
The Treasury supports three revenue sources out of the box. Connect them one at a time or all at once:
/treasury --connect stripeConnects your Stripe account via restricted API key. The Treasury ingests subscription revenue, one-time payments, and refund data. Paddle and Mercury follow the same pattern — just swap the provider name.
Once connected, revenue data flows into the budget allocation engine. Dockson distributes funds across growth channels based on historical ROI, with Steris validating each allocation against her forecast models.
PER-PROJECT ISOLATION
Treasury paths are project-scoped. Each project keeps its own financial logs in project/cultivation/treasury/ — spend-log.jsonl, revenue-log.jsonl, budgets.json, and campaigns/. No more global collision at ~/.voidforge/treasury/.
What stays global: The credential vault (one Stripe/Mercury account across projects) and TOTP 2FA (user-scoped, not project-scoped).
Per-project daemon: Run voidforge heartbeat start --project-dir /path to configure PID, socket, token, state, and log files for each project independently.
Migration: Clean-break approach — global archive is preserved, per-project logs start fresh. No data is deleted. Use voidforge migrate treasury to move existing data.
SAFETY ARCHITECTURE
The Treasury enforces the same four spend tiers established by Cultivation. Every transaction is tagged with the tier that authorized it, creating a complete audit trail from authorization to reconciliation.
Daily reconciliation runs automatically. Dockson compares actual spend against authorized budgets, flags discrepancies, and alerts you if any channel exceeds its allocation by more than 5%.
If something goes wrong — unexpected charges, runaway ad spend, compromised credentials — one command locks everything down:
/treasury --freezeEmergency freeze. Pauses all ad campaigns, revokes spend authorization, and generates an incident report. Requires TOTP 2FA to unfreeze. The nuclear option — but sometimes you need it.
WHAT'S NEXT
The books are open. Now watch the whole operation in the Danger Room (Step 4). Or go back to Growth to run campaigns against the budget you just set.