What the handoff includes
The agreed route rules, approved account connections, review ownership, input fields, exception handling, test record and instructions to pause the workflow. I confirm what support is included.
A workflow with a review gate.
I built this browser-local intake demonstration to make the decisions visible. Choose a sample task and inspect the route, the next question and the point where I must review it.
Automation study / Intake triage
Capture. Route.
Review before execution.
A repeated administrative task is a useful place to start. This example turns a short intake into a category, a brief and an owner review queue. The rules are deterministic. It is not a connected AI assistant.
Capture the brief
Record the intended output, timing and data boundary. Do not ask for credentials in a public intake.
Input / sample onlyRoute the task
Assign one of the nine service categories from the selected task. Record the next scope question.
Rule / inspectablePause for review
Flag sensitive data, urgent timing, funding requirements or media permissions. I confirm the decision.
Gate / always humanApprove the next step
A real workflow needs approved access, a defined scope and an exception route before sending or changing anything.
Execution / absent here
Working sample / Runs locally
Inspect the route
before connecting accounts.
Use invented sample information. No external API, mailbox or business account is connected. This page does not send a quote, create a client record or execute the task.
Up to 600 characters. Keep real names, private data and credentials out of this demonstration.
Default sample shown. Enable JavaScript to try different routes.
Route / READY / PERSONAL REVIEW
AI Setup & Automation
I confirm the brief, scope and price personally. No automatic acceptance.
Next question: Which repetitive step should change, what data does it use, and who approves exceptions?
Read this service scopeDEMONSTRATION / NOT SENT Category: AI Setup & Automation Proposed output: An intake workflow brief Timing: Within two weeks, scope unconfirmed Data: Public or invented sample information Next question: Which repetitive step should change, what data does it use, and who approves exceptions? Owner gate: I confirm the brief, scope and price personally. No automatic acceptance. Human review is required before a quote, external processing or execution.
Inspect the operating map
The stop points
are part of the design.
A useful automation brief explains what happens when inputs are missing, permissions change or the task exceeds the agreed rules. I define those branches before connecting a real account.
- 01 / Capture
Sample task and constraints
Only the selected category, timing and invented note enter this demonstration.
- 02 / Classify
One inspectable route
The selected task chooses a service category. The rule is deterministic and visible.
- 03 / Draft
A brief and next question
The page prepares text for inspection. It does not accept the job or quote a price.
- 04 / Review
Owner decision required
I confirm facts, permission, timing, competence and scope before any real action.
Exception lane / Stop and ask
Sensitive data, urgent timing, missing evidence, funding requirements and media permissions move to review. A visible ready state still requires personal approval.
Missing output or source records
Pause the route. Ask for the decision the deliverable must support and the missing source. Do not let a fluent draft conceal an incomplete brief.
Personal, confidential or credential data
Stop external processing. Confirm the permission and approved data boundary. Credentials are excluded from the intake and need a separate approved transfer method.
Urgent timing or unavailable review capacity
I check the calendar, assets and approval dates before promising delivery. Offer a later start or a smaller written scope when the timing does not fit.
Repeated event or duplicate request
A connected implementation needs a unique event key and a recorded state before sending or creating a second record. This local demo performs no send or record creation.
Unknown category or a specialist decision
Send the task to personal review. I verify fit and limits before quoting. Accounting, legal and funding decisions require the relevant qualified reviewer.
Provider failure or permission changes
Keep the draft and show the failure. Use a documented manual queue. Do not retry an external action indefinitely or represent an unconfirmed send as successful.
Take the inspected brief with you.
The local export reads the brief currently visible above. Run the route after changing the sample, then export. It includes the remaining review checklist and the demonstration label.
The default specimen is available without JavaScript.
What this sample proves
The interface routes an invented brief and exposes the owner gate. It does not prove autonomous AI judgement, a working mailbox integration or a measured time saving.
A real implementation
Define the failure path
before the happy path.
| Decision | What I define | Release check |
|---|---|---|
| Data boundary | Which records are needed, where they may be processed and who authorized access. | Remove unnecessary data and exclude credentials from prompts. |
| Connected accounts | Client-owned accounts, permission level and a reversible access method. | Verify the actual connection and test with a permissioned sample. |
| Human approval | Which draft or action needs approval and who gives it. | The workflow cannot silently bypass the owner gate. |
| Duplicate handling | How to recognize a repeated event and prevent a duplicate send or record. | Repeat the event deliberately and inspect the result. |
| Exception route | Missing data, provider failure, unexpected task and permission changes. | Show a useful failure and keep a manual way to complete the work. |
| Operating handoff | Owner instructions, logs, support boundary and how to turn it off. | The client can pause and resume it without depending on a demo page. |
Useful work to automate
Organize supplied notes, prepare a draft, calculate a defined metric, route a routine request or assemble a review queue. Start with one repeated task and a measurable manual baseline.
Decisions I retain
I approve scope, facts, pricing, permissions and release. Funding eligibility, confidential data and unfamiliar integrations require review before accepting the work.
AI Setup & Automation is scoped pilot work. This functioning sample demonstrates routing and safeguards. It does not prove a live integration, autonomous AI output or a measured time saving.
Scope basis: VL-PUBLIC-SERVICES.md, VL-CONTEXT.md and the studio’s AI workflow and quality gates in VL-BUSINESS-PLAN.md. The local routing rules were built for this public demonstration. No private records, connected accounts or client results are used.