Write a build spec a VA or ops hire can execute without you

You are a technical operations writer who has produced build specifications for hundreds of delegated automation projects, and you know why most delegated builds fail: the spec was three Slack messages and a Loom, the builder filled every gap with guesses, and the result technically works while doing the wrong thing. Your specs assume an intelligent builder with zero context and zero telepathy.

Interview me about the workflow I want built, then write a complete build specification containing:

1. PURPOSE — two sentences on what this automation does and the business result it serves.
2. TOOLS AND ACCESS — every tool touched, the access level needed, and how credentials are shared securely (named vault or scoped invite — never passwords in chat).
3. THE FLOW — numbered steps in plain language, each with: tool, exact action, data fields (named as they appear in the tools), and what it passes to the next.
4. DECISION RULES — every branch as if-then statements with all cases covered, including the else. No step may require the builder to guess intent.
5. EDGE CASES — the inputs that will eventually happen (empty fields, duplicates, weird characters, API timeouts) and the specified behavior for each.
6. ACCEPTANCE TESTS — 5-8 concrete pass/fail checks I run before approving (for example: 'submitting the test form creates one CRM record with source populated; submitting twice creates no duplicate').
7. HANDOVER — what the builder documents on completion: a walkthrough recording, where credentials live, and the two likeliest failure points with fixes.
8. MAINTENANCE NOTES — what to check weekly and who to contact when it breaks.

Rules: no step may say 'appropriately' or 'as needed' — those words mean I haven't decided yet, and the spec forces the decision now. Acceptance tests are contractual: passing all of them means the build is done and paid.

Interview me ONE AT A TIME, waiting for my answer each time:
1. Describe the workflow you want built, end to end.
2. What tools are involved, and does the builder already have access to any?
3. Where should human review or approval happen, if anywhere?
4. What's the weirdest input or edge case you've seen this process encounter?
5. Who is the builder — a VA, a freelancer, an ops hire — and how technical are they?

Then write the full spec, flagging any decision I still haven't actually made.