# VertexLineup intake workflow: default specimen

This is a browser-local demonstration. It was not sent to the studio. It is not a quote, contract, accepted task or connected workflow. Use invented information when testing the page.

## Visible default brief

- 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: Dhairya confirms the brief, scope and price personally. There is no automatic acceptance.

## Inspectable route

1. Capture the task, timing and data boundary.
2. Choose the category from the selected task.
3. Prepare a brief and the next question.
4. Require owner review before any actual action.

## Exception lane

- Missing output or source: ask for the missing evidence.
- Personal or confidential data: confirm permission and the approved boundary.
- Credentials: exclude them from this intake and arrange a separate approved transfer.
- Urgent timing: check available hours and review dependencies.
- Unknown category or specialist decision: require personal review and verify competence.
- Duplicate event in a connected implementation: use a unique event key and recorded state.
- Provider failure: show the failure and retain a manual queue.

## Human review checklist

- [ ] Confirm the source facts and decision-maker.
- [ ] Confirm permission and the approved data boundary.
- [ ] Confirm availability, required assets and scope.
- [ ] Agree price, review dates and acceptance in writing.
- [ ] Test exceptions before connecting any real account.
- [ ] Provide instructions to pause the workflow and handle failures manually.

The public sample ends at the review gate. It does not send email, create a customer record, call external AI, execute an action or prove a measured time saving.