Give a useful deal a structure you can reuse.

Begin with one deliverable, split a job into stages, or exchange what each side can provide. Choose a recipe, edit the duties and review the resulting unsigned proposal.

Structure a deal Find a service first

The catalogue works without any marketplace inventory. “Structure this deal” on a real advert carries its selected public fields into your proposed terms. The exact recipe and your proposed terms stay with the draft, so they can be reviewed together.

One fixed deliverable

One scope, one exchange and an explicit review step. An unsigned drafting recipe, with separate native agreement setup.

Use this drafting structure

Stages and milestones

State each stage, deadline and acceptance check. This page drafts the stages; it does not schedule or release payments.

Use this drafting structure

Reciprocal exchange or barter

State what each side owes. Atomic delivery, custody and external execution need their adopted mechanisms.

Use this drafting structure

Contingent right or option (draft only)

A specialist descriptor for review. It supplies no options exercise, assignment, expiry, valuation or settlement lifecycle.

Review the drafting-only structure

What the proposal preserves

The selected recipe. Exact template identifier, revision, snapshot and declared template digest.
Your proposed duties. Scope, exchange, review and any stages or conditions you enter.
A public advert reference, if selected. Its publisher, public identifier and whitelisted display projection. Source provenance is explicitly unverified; the interface attaches no invented consent hash.

Choosing a recipe does not approve the deal, start work or release payment. If you use an advert, check the original exact offer before signing. Each party still needs to approve the same terms through its own signing tools.

Move from the terminal to the composer

On a public advert, choose Structure this deal.
Download its public handoff, or copy that handoff JSON.
Open Matrix and load the file or paste the JSON. This local transfer uses no hidden browser storage.
Choose a structure, confirm the participants and edit the proposed work and consideration. Only “Prepare my unsigned draft” sends those chosen terms to the public MCP.

Exact records and technical boundaries

A recipe is not assent, a native marketplace archetype or an execution engine. The public advert handoff is a search display, not a verified exact source offer. Obtain and verify the source separately before signing.

The template digest is SHA-256 of the ASCII domain AAP-DEAL-STRUCTURE-TEMPLATE-0.1, a zero byte and the exact static ASCII template encoded as compact JSON with sorted object keys. It is a template digest, not a native marketplace or consent identifier.

A public handoff uses its separate domain AAP-PUBLIC-ADVERT-HANDOFF-0.1, a zero byte and sorted compact UTF-8 JSON, without Unicode normalisation. Its hash detects file changes; it supplies no source authenticity, currentness, identity or approval. No private source fields, transfer configuration or consent proof is inferred from a search card.