A guided builder for bounded coordination contracts — research toward a local,
synthetic, testnet-only stage. It starts from explicit requirements, never from an arbitrary
request to generate and deploy financial code.
Design candidate · research status. Illustrates the contract-lab
stage's release criteria with synthetic content. No real funds, no deployment, no key collection —
see the vision index for scope.
Journey view · guided requirements
Requirements first — the builder asks before it writes
The wizard walks roles, scope commitments, artifact references, acceptance
thresholds, deadlines and any optional settlement rule. Every answer lands in a readable
agreement summary before a single line of Solidity is generated.
Roles
Coordinator @aria · QA @sana · funder: open — each with grant/revoke visibility
Delivery manifest with CID and raw digest, per stage 03
Acceptance threshold
Scope check + QA check on the same delivery revision
Deadline
Escalation after 10 days of reviewer silence
Settlement rule
None in this example — settlement is a separate, optional stage
Criteria addressed
Start from explicit requirements · explain roles, scope, artifact references, thresholds,
deadlines and optional settlement before output · administrative power stays visible.
Journey view · what the builder produces
Output is a package, not just code
Generated with the code
Readable Solidity · the normalized agreement · stated assumptions · a threat model ·
version-pinned dependencies · compiler settings · reproducible tests.
Criteria addressed
Pinned reproducible output · role, signature, replay, nonce, expiry and cross-contract
tests accompany every generated contract.
Signing authority is modeled, not assumed
A future signing request binds action, project, scope and delivery version, permitted
recipient, amount where relevant, plus expiry and a single-use nonce — under a defined
domain. Contract wallets re-verify at execution; nothing caches trust.
Criteria addressed
Signing authority separate from Commons login · EIP-712 structured signing · explicit
semantics for revocation and delegated agent signing limits.
Journey view · hard refusals
What the lab will not do
The refusal states are drawn here so they are reviewable before any generator
exists. Each refusal names the boundary it enforces.
Collect the user's private keyrefused · keys
No private-key collection, no automatic signing, no implicit deployment.
A testnet demonstration is not a real-value launch.
Deploy to mainnetrefused · deployment
First slice is a local delivery-and-acceptance example with synthetic
artifacts and no real funds; any testnet exercise needs separate authorization.
Generate financial code unpromptedout of scope
The builder addresses bounded coordination agreements — escrow, tokens
and marketplaces are not in scope and are not generated "as a bonus".
Criteria addressed
Release criteria: clear review of the requested operation · no private-key collection, automatic
signing or implicit deployment · explicit access-control roles with visible grant/revoke powers.