Transparent paid cooperation: the agreement before the work, an optional
independent instance for one agreement's funds, and every outcome defined before
implementation. Voluntary work remains a choice; nothing here launches custody, a token
or a marketplace.
Design candidate · proposed, optional. Illustrates the settlement
stage's release criteria with synthetic content. Not an offer of payment, custody or escrow —
see the vision index for scope.
Journey view · agreement before work
The agreement card, visible to everyone involved
Budget, asset, contributors, fees, funding responsibility, release conditions,
rights to deliverables, deadlines, cancellation and dispute path — agreed before work begins,
rendered where every participant can point at it. Do not infer a paid engagement from a
posted offer or need.
Budget · asset
Synthetic example only — no real asset is modeled here
Funder commits before work; the instance holds only this agreement's funds
Release conditions
The acceptance threshold of stage 04 — a delivery reference alone releases nothing
Rights to deliverables
Stated in the agreement, not implied by payment
Cancellation · dispute
Named path with deadlines; unavailability of a party is a designed state
Criteria addressed
Budget, asset, contributors, fees, funding responsibility, release conditions, rights,
deadlines, cancellation and dispute path agreed before work · voluntary work stays voluntary.
Journey view · the outcome machine
Every outcome is defined before implementation
The proposed contract defines these states up front; partial work, partial
acceptance, fee deductions and timeout outcomes get explicit rules, not implementation
defaults discovered after funding.
funded
The independent instance holds exactly one agreement's funds, within the authority and evidence policy the parties accepted.
delivered
A delivery manifest exists (stage 03). Delivery does not move money.
accepted
The stage 04 threshold is met on one delivery revision. Settlement consumes its own authorization — acceptance is evidence, not permission to pay.
disputed
The named dispute path is active; the independent reviewer selection rule and cost allocation come from the agreement.
released
Funds move only on an authorized release decision bound to the accepted revision. Bounded amounts, no double payment.
refunded
Cancellation, timeout or nonresponse paths return funds by rule — including partial rules stated in advance.
Criteria addressed
Funded, delivered, accepted, disputed, released, refunded and cancelled outcomes defined before
implementation · a valid delivery reference alone must never release funds · the instance
operates only within the accepted authority and evidence policy.
Journey view · evidence before real value
The gate before any real value moves
These are prerequisites for a release decision, not a launch schedule. Independent
review adds evidence; it does not eliminate every defect.
Threat model
Published and concrete: forged or replayed decisions, stale scope, compromised or revoked roles, front running, collusion assumptions, unresponsive decision-makers
Fund invariants
Conservation of funds, bounded release/refund amounts, correct recipient and asset handling, reentrancy, failed transfers, unsupported assets fail explicitly
Independent review
Of the deployed version, with resolved findings; bytecode/source correspondence; clear chain and contract identification
Operations
Limits on delegated agent signing; incident, pause and recovery procedures; transparent administrative and upgrade powers — including their absence
Criteria addressed
Before real value: publish a concrete threat model, independently reviewed implementation,
resolved findings and a separately approved deployment plan.