11 · Start a company, sell a product

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

“Help me start an LLC and get my first product listed and selling.”

PARTIAL The stress test: every ask type, most block formats, several deals chained. Each piece is a walk the system already carries or a gap already named — nothing here needs new law, it needs the two rails and honest sequencing. Likely several deals, not one (the walk holds one ball; a company is many).

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze.

Confirm formation facts
APPROVE

Blocks confirm_correct, structured_form

Gates that fire Name, state, registered agent — you confirm what gets filed.

File the LLC — person executes
PROVIDE

Blocks external_link, download_return, signature, code_reference

Gates that fire State filing sites are person-auth territory; agent prepares everything, you click file. Works today.

EIN, bank, payment processor
PROVIDE / GRANT

Blocks external_link, connect_account, code_reference

Gates that fire Same person-executes pattern.

Note Each connect_account is the provider-lane gap again.

Product listing: copy, photos, price
CHOOSE / APPROVE

Blocks review_approve, media_upload, number, single_choice

Gates that fire Works.

Storefront live
APPROVE

Blocks review_approve, external_link

Gates that fire Person connects their store account; agent verifies the listing.

First-sale marketing
CONTACT

Blocks review_approve

Gates that fire The email leg of use case 5.

Finish line: first sale?
FINISH

Blocks yes_no

Gates that fire SMART finish lines matter most here — 'selling' must be pinned to a number at bid time or REJ-16/19 territory.

Gaps & what to build

This case is why the reference exists: it is not one missing feature, it is the same two rails (provider lane, vendor spend) plus disciplined scoping. When 3, 6, and 7 are built, 11 falls out.

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