Connect payment to an agreed next step.

The amounts you see are proposed terms.

Entering a USDC value in FOLIO does not read a wallet balance, request an approval or transfer tokens. It only calculates the values in an unsigned draft.

The current site has no wallet connection or live escrow contract. Downloading an agreement does not reserve funds and does not create an on-chain record.

The intended flow.

This sequence describes the product direction. It is not a specification of deployed software. The final design must also cover cancellations, changes, timeouts and disagreements.

• Agreement: both parties accept the scope, milestones and applicable rules.
• Funding: the client would reserve the agreed amount through a supported contract.
• Delivery: the contributor submits a milestone for review.
• Approval: the agreed approval process determines whether the milestone is accepted.
• Release: the contract would transfer the amount assigned to that milestone under its rules.

What the escrow layer would need to do.

In the proposed model, escrow is the payment-holding part of the agreement. Its job would be to make the available funds and permitted releases explicit. It would not independently decide whether creative or technical work is satisfactory.

That distinction is central to FOLIO: payment rules can refer to an approval, but people still need clear criteria and a way to handle disputed decisions.

Follow one example.

Today the same example can be drafted and downloaded, but none of those releases occurs. No payment status in the builder should be interpreted as a transaction confirmation.

Decisions still to be made.