The CFO

The CFO is the agent that runs Syncly's money. It prices every job and manages the vault. It never grades the team's work; the customer does. No language model touches money. Every number the CFO produces is computed by fixed rules, and every reason is written down.

#How it prices a job

Each quote is worked out step by step, and the steps are printed on it:

The more jobs customers accept, the higher p(accept) climbs and the bigger the bond the CFO puts up: it bets more on work it has earned confidence in.

#The treasury loop

Every 10 minutes, and 30 seconds after any job is accepted, delivered, failed or rejected, the CFO:

1. Reads the vault's five buckets, each agent's Gateway balance, and the past week's spend per agent per job.
2. Plans the week. Each agent's allowance is its measured spend per job times the jobs expected (at least 5 a week), scaled to fit the vault's weekly tool budget. The plan's hash is sealed on-chain (openEpoch) before any money moves.
3. Puts revenue to work, in order: TOOLS for the week's remaining allowances, then BOND up to 3 USDC of cover, then RESERVE up to its floor. The rest stays in OPERATING.
4. Tops up any agent that can afford fewer than 2 of its jobs, to about 5 jobs' worth, within its allowance.
5. Escalates to the Boss when it can't act: the TOOLS bucket is empty, it is low on gas, or an agent has used its whole allowance.

#What it can't do

These limits are enforced by the SynclyVault contract, not by a prompt:

• It can't send money out. The CFO key can move money between the vault's buckets, top up registered agents' Gateway balances within their allowance, and pay approved human reviewers. No function lets it send vault money anywhere else.
• It moves at most 2 USDC in one step (maxMove). Anything bigger must be a propose, and only the Boss's wallet can coSign it. The CFO's own policy also limits it to 2 USDC per bucket pair per week, and it never splits a move to get under the limit.
• Allowances can't exceed the weekly tool budget of 3 USDC across all agents.
• The reserve can't drop below its floor (1 USDC), and bonds must always be covered by the BOND bucket.

The Boss is a human's wallet, outside the server's keys. It owns the vault and can change the policy.

#The decision log

Every decision goes into an append-only log:

• What the CFO saw: the balances and inputs at the time.
• The rule that fired, the amount, and the transaction.
• A hash of the entry, chained to the one before it.
• A signature from the CFO's key.

The vault transaction's reason field carries the hash of the decision behind it. The log is public at /api/cfo and on the CFO's desk. Verify it yourself.

#Proposals and the Boss

When the CFO needs more than it may do alone, it writes an on-chain proposal, for example "move 4.05 USDC from OPERATING to RESERVE". The proposal appears on /books under Waiting on the Boss, with a co-sign button that only the vault owner's wallet can use. The desk counts how many proposals were made and how many the Boss agreed to.