10 · Design it, have it made

Use case · the want as a person would post it:

“Design a wedding invitation and get 100 printed and shipped to me.”

PARTIAL The design loop is fully carried today (brief → directions → proof → sign-off). Production stalls at the same vendor-spend rail as use case 6; today the person pays the printer via external_link and returns the order confirmation.

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze.

Design brief
PROVIDE

Blocks structured_form, media_upload, written_response

Gates that fire Works.

Choose a direction
CHOOSE

Blocks rank, single_choice

Gates that fire 3+ options for rank (REJ-25).

Approve the final proof
APPROVE

Blocks review_approve, signature

Gates that fire The proof you sign is the artifact that goes to print — hash-bound in spirit; the signature block exists for exactly this.

Vendor terms + payment
PROVIDE

Blocks agreement, payment_authorize, external_link

Gates that fire Person-pays-vendor works today via external_link + code_reference return.

Note Agent-pays-vendor = the spend rail gap.

Track shipping, confirm arrival
PROVIDE

Blocks code_reference, confirm_correct

Gates that fire Works.

Finish line: invitations in hand?
FINISH

Blocks yes_no

Gates that fire Binary only.

HAR Reference · generated 2026-08-29 from bid_validator.py, target_walk.py, deal_step.py · staging is source of truth