Print pack — File → Print, Letter portrait, default margins. Each use case starts on its own page with ruled note space. On-screen reference: HAR Reference.

HAR use cases — the walk list

Print pack generated from the HAR Reference · one use case per page, note space on every step · 2026-09-02

Eleven use cases, in the order we walk them. The order front-loads machinery coverage: walk 1 exercises four of the six asks in one deal, so every later walk is mostly re-treading verified ground plus one new piece. Fix what each walk surfaces before starting the next, and each walk gets easier than the last.

#Use case · why this positionVerdict todayDate walked
☐11 · Set up a meeting
PROVIDE + gated CONTACT + CHOOSE + FINISH in one walk - four of the six asks, five block types. The appointment walk; verifies the most machinery in one run.		works today
☐22 · Connect two people by email
The canonical CONTACT walk - per-attempt hash-bound email approval, both directions.		works today
☐34 · Cold outreach to a found contact
Adds the research phase: long agent_working stretch, pulses, then gated CONTACT to a found stranger.		works today
☐45 · Create a marketing campaign
Deliverables walk - PROVIDE/APPROVE over files and drafts; exercises released materials.		works today
☐53 · Drip on a Google Calendar
First GRANT + connector walk. This is build-order item 3: connect Google once, one calendar action, receipt shown.		partial
☐67 · Connect services
Generic MCP connector lane - proves the connector contract beyond the Google adapter.		partial
☐78 · Get a telephone number
Person-does-it path today; documents exactly where the agent-side spend rail is missing.		partial
☐810 · Design it, have it made
Design loop (works) then manufacture - second spend-rail proof point.		partial
☐911 · Start a company, sell a product
The long composite walk - every verified piece above, chained. Run late so failures are new, not repeats.		partial
☐106 · Facebook ads via a service
No ad-account lane, no outbound spend rail. Walk it on paper to spec the lane.		gap
☐119 · Sales call + voicemail
No voice channel. Walk it on paper; approval law generalizes from email.		gap

Notes on the run

Walk 1 of 11

1 · Set up a meeting

“I want a 30-minute intro call set up with my accountant sometime next week.”

WORKS TODAY Pure block work: availability in, candidate slots chosen, confirmation out through the gated email step.

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze: blocks locked, step 1 live.

Collect your availability
PROVIDE

Blocks date_time, communication

Gates that fire REJ-24 (a date must use the date control — rule 170's founding case); r104.

Approve the outreach email to the accountant
CONTACT / APPROVE

Blocks review_approve

Gates that fire Per-attempt, hash-bound email approval (contract 2.17/2.21); the exact bytes you approve are the bytes that send.

Choose the final slot
CHOOSE

Blocks single_choice

Gates that fire REJ-25: at least 2 real options; typed-ask guard: only the choice control closes it.

Finish line: meeting on the calendar?
FINISH

Blocks yes_no

Gates that fire Binary only closes a finish.

Gaps & what to build

Calendar placement is the person's move today (an external_link "add to calendar" block, or the confirmation email). A calendar grant lane would upgrade this — see use case 3.

Where it can stall

Fixed 2026-09-02. A CHOOSE whose options are only known mid-walk deadlocked on 08-29: the agent had no way to send the list when filing. Fix: include choose_config in the outcome payload and the platform writes it before opening the ask. The person sees the options the moment the agent files.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 2 of 11

2 · Connect two people by email

“I want you to introduce me to Jordan by email — we should know each other.”

WORKS TODAY The canonical CONTACT walk; the email machinery (approval, attachments, inbound replies) is the most battle-tested path in the system.

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze.

Confirm the framing and both parties' details
APPROVE

Blocks confirm_correct

Gates that fire r118: the agent must answer your questions before filing.

Approve the intro email
CONTACT / APPROVE

Blocks review_approve

Gates that fire Per-attempt approval; attachments are approval-hash-bound and must be released-to-this-deal (≤5 files / 8MB); send-back feeds your notes verbatim to the redraft.

Send + confirm delivery
CONTACT

Blocks —

Gates that fire confirmed_email_send_receipt files as evidence; send-receipt ≠ inbox delivery unless the receipt says so. Inbound replies flow back through SES → webhook (~15s).

Finish line: intro made?
FINISH

Blocks yes_no

Gates that fire Binary only.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 5 of 11

3 · Drip on a Google Calendar

“I want a daily 9am affirmation dropped onto my Google Calendar for 30 days.”

PARTIAL The drip machinery exists and runs live (30-day schedules, minutely dispatcher, r208 finish gate). Contract 2.15 and the Google Calendar adapter now provide the bridge shape: scoped authorization, frozen action, execution, and receipt. This page has not proven production OAuth configuration or one live Calendar action.

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze.

Approve the 30-day schedule
PROVIDE

Blocks schedule

Gates that fire r208: FINISH refuses while the schedule is pending; a recurring claim without a schedule cannot close.

Connect your Google Calendar
GRANT

Blocks connect_account

Gates that fire REJ-11 what/why/scope/until; r104 — person authenticates with Google directly, never through the agent.

Note FOUNDATION BUILT / LIVE USE UNPROVEN: the broker, encrypted credential store, scoped calendar actions, and receipt path exist. Production provider configuration and one real end-to-end action still need proof.

Drip runs; finish at day 30
FINISH

Blocks yes_no

Gates that fire Schedule must be complete or paused-by-you.

Gaps & what to build

To prove next: configure the production OAuth provider, connect Google once, authorize one bounded Calendar action, execute it, and display the receipt. Then separate the reusable account connection from each temporary deal authorization. Workaround today: platform-side drip (as shipped for the affirmation pack) + an external_link/download_return block handing you an .ics feed to add yourself.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 3 of 11

4 · Cold outreach to a found contact

“I found a researcher whose work matters to mine. Find their email and reach out on my behalf.”

WORKS TODAY Research is ordinary agent work; the outreach is the same gated CONTACT machinery as use case 2. The gates are what make cold outreach safe to allow at all.

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze.

Confirm the target and the pitch angle
APPROVE

Blocks confirm_correct

Gates that fire You confirm the who and the why before any contact exists.

Research: find the address, draft the note
PROVIDE → APPROVE

Blocks review_approve

Gates that fire Agent-side work; r100 pulses every 30 min. The draft shows you the found address as part of the reviewed bytes.

Approve the exact email
CONTACT / APPROVE

Blocks review_approve

Gates that fire Per-attempt, hash-bound. REJ-07 bans bare URLs in bids; r104 bans credential asks; contact-stop is always available to you.

Send, handle the reply
CONTACT

Blocks —

Gates that fire Replies ride the inbound pipeline back into the thread.

Finish line
FINISH

Blocks yes_no

Gates that fire Binary only.

Where it can stall

Volume is the risk to watch: these gates are per-deal. Nothing yet rate-limits one person running many cold-outreach deals in parallel — a policy question to settle before this is promoted hard.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 4 of 11

5 · Create a marketing campaign

“I want a marketing campaign for my book — plan, copy, assets, and a launch calendar.”

WORKS TODAY As a deliverables walk this works end to end today: strategy chosen, drafts approved, assets delivered through the r169 document reader. Execution beyond email splits per channel (see 6 and 9).

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze.

Scope: audience, budget ceiling, channels
PROVIDE

Blocks structured_form, number, multiple_choice

Gates that fire Form-field minimums (REJ-25); the number block carries the ceiling in its unit.

Choose the campaign direction
CHOOSE

Blocks single_choice, rank

Gates that fire 2–3+ real options; the deadlock-prone shape until auto-open ships.

Review the plan document
APPROVE

Blocks review_approve

Gates that fire r169 inline reader: ≤40 blocks, ≤6 images; send-back → redraft loop.

Deliver copy + assets
APPROVE

Blocks review_approve, file_upload

Gates that fire Released materials always listed, including zero.

Launch the email leg
CONTACT

Blocks review_approve

Gates that fire Per-attempt approval per send.

Finish line
FINISH

Blocks yes_no

Gates that fire Binary only.

Gaps & what to build

Paid placement (6), voice (9), and posting into the person's own social accounts (a provider lane, like 3/7) are the channels this walk cannot execute today — it hands you the assets instead.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 10 of 11

6 · Facebook ads via a service

“Run $200 of Facebook ads for my shop using whatever service does this well.”

GAP Two rails are missing at once: a provider lane to the ad account (as in 3 and 7), and an agent-side spend rail — money leaves the system today only on milestone release to the agent; there is no held-funds → third-party-vendor path.

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze. The $200 would fund here and sit held.

Scope the ad: audience, creative, budget
PROVIDE

Blocks structured_form, media_upload, number

Gates that fire Standard blocks — works.

Approve the creative + targeting
APPROVE

Blocks review_approve, agreement

Gates that fire Works.

Connect the ad account
GRANT

Blocks connect_account

Gates that fire REJ-11; r104.

Note GAP #1: no ad-account provider lane.

Spend the $200 with the service
PROVIDE

Blocks payment_authorize

Gates that fire REJ-06 bans recurring-payment language; REJ-17 bans off-platform payment on matched wants.

Note GAP #2: no outbound spend rail — held funds can only release to the agent on approval, not to a vendor.

Report results
APPROVE

Blocks review_approve

Gates that fire Works — screenshots + metrics through the reader.

Finish line
FINISH

Blocks yes_no

Gates that fire Binary only.

Gaps & what to build

To build: (a) the generic provider lane (shared with 3/7); (b) a vendor-spend rail: held funds → named third party, per-line-item, person-approved, receipts filed — the same held/released law money already obeys, pointed outward. Both are Steven-gate decisions, not incidental engineering.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 6 of 11

7 · Connect services

“Wire my form signups into my mailing list and my CRM — whatever works.”

PARTIAL The purest test of the provider lane: nothing here needs money or outreach, only the ability for a person to connect accounts and for an agent to hold scoped capabilities against them. The broker and generic MCP execution lane now exist. A third-party automation provider, production connection, and passing end-to-end action remain unproven.

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze.

Map the flow: sources, destinations, fields
PROVIDE

Blocks structured_form, written_response

Gates that fire Works.

Connect the automation platform (or each service)
GRANT

Blocks connect_account, grant_access

Gates that fire REJ-11 what/why/scope/until; equivalent-swap lets the agent substitute a same-shape service without re-asking.

Note FOUNDATION BUILT / PROVIDER UNPROVEN: scoped authorizations, exact-action approval, execution, and receipts exist; platform-specific connection and execution still need proof.

Build + test the zap; show a passing test run
APPROVE

Blocks review_approve

Gates that fire Works.

Finish line
FINISH

Blocks yes_no

Gates that fire Binary only.

Gaps & what to build

Equivalent-swap is unusually valuable here: “substantially the same capability under the same limits” is exactly the choice between one automation platform, another, or a native webhook. The walk and generic connector lane now carry the law and execution shape. What remains is provider coverage, production configuration, and a passing receipt-backed run.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 7 of 11

8 · Get a telephone number

“I need a dedicated phone number for my business.”

PARTIAL Works today when the person carries the last mile (agent researches and walks you through signup via external_link + download_return of the confirmation). The agent-does-it-fully version needs the vendor-spend rail from use case 6.

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze.

Requirements: area code, SMS?, forwarding?
PROVIDE

Blocks structured_form

Gates that fire Works.

Choose the provider
CHOOSE

Blocks single_choice

Gates that fire Agent's researched shortlist; REJ-25 minimums.

Sign up — person-does-it path
PROVIDE

Blocks external_link, code_reference

Gates that fire Person completes signup on the provider's site and returns the number / confirmation code. Works today.

Note Agent-does-it path would need vendor spend + an account lane.

Verify: test call/text the number
APPROVE

Blocks confirm_correct

Gates that fire Works.

Finish line
FINISH

Blocks yes_no

Gates that fire Binary only.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 11 of 11

9 · Sales call + voicemail

“Call this prospect, pitch my service, and leave a voicemail if they don't pick up.”

GAP No voice channel exists — CONTACT speaks email only. The law, however, transfers cleanly: a call script is a draft, per-attempt approved, hash-bound; a voicemail is a send receipt; a live conversation needs a recording-consent ruling first.

The walk, step by step

Deal signed
FINISH

Blocks —

Gates that fire Signing freeze.

Approve the pitch script + voicemail script
APPROVE

Blocks review_approve

Gates that fire Same per-attempt approval law as email — approve the exact words.

Place the call
CONTACT

Blocks —

Gates that fire r104 on the call itself (never ask the prospect for credentials).

Note THE GAP: no telephony rail (provider, consent capture, recording/transcript as receipt).

File the outcome: reached / voicemail / no answer
PROVIDE

Blocks single_choice, written_response

Gates that fire Transcript or voicemail-confirmation files as the receipt.

Finish line
FINISH

Blocks yes_no

Gates that fire Binary only.

Gaps & what to build

To build: a voice CONTACT lane: scripted-call provider integration, consent handling ruled by Steven, transcript-as-receipt. The approval law (contract 2.17/2.21) generalizes verbatim; do not invent a parallel approval system for voice.

Where it can stall

A live human conversation cannot be hash-bound the way an email can — the script is approved, the conversation drifts. That gap between approved-bytes law and live speech is the genuinely new design question here.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 8 of 11

10 · Design it, have it made

“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.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐
Walk 9 of 11

11 · Start a company, sell a product

“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.

Notes & changes

Walked on: ______________ Result:  ☐ clean  ☐ fixed in place  ☐ blocked Re-walk needed: ☐