Work∣Available on Web, macOS and Windows

Give it a goal.Get back work you can check.

Hand ZeroTwo an outcome, the material it may use, and the steps that need your sign-off. It plans the run, works with the models and tools your account allows, and stops before anything consequential.

Plan the assignment

The run starts as a plan you can read: the outcome broken into bounded steps, each with its inputs and the check that closes it.

  • Steps and dependencies laid out before any work starts
  • Every step names what it needs and what it produces
  • Review points marked where you asked for them
Plan4 steps · 2 need you
Writing planRenew Acme before 30 Sep

Four steps. Two need your sign-off before anything leaves the building.

1Pull Q3 usageneeds DriveQ3-usage-summary.xlsx
2Check against contractneeds Notionseat + integration deltas
3Draft the renewal noteneeds steps 1–2renewal-note.docx
4Sendwaits for youapproval gate
Assumptions
Seat count is billable seats, not invited seats.
The March rate holds unless the contract says otherwise.
Integrations counted per workspace, not per user.

Use the right model and tools

It works with what your account already has — the models you pay for, the files you attached, the connectors you approved. Nothing beyond that.

  • Model choice per step, not one model for the whole run
  • Reads only the sources you authorised
  • Connectors and research modes stay inside your permissions
Run1m 12s

Renew Acme before the 30th — and send nothing without me.

Working for 1m 12s
Gemini 3 ProReadingReaddrive://Q3-usage.xlsx214 rows
Gemini 3 ProReadingReadcontract://acme-2025cap 220 seats
GPT-5.5CheckingCheckedcrm://acme/ownerrenews 30 Sep
Opus 4.6CreatingCreatedrenewal-note.docx+214 −0
Opus 4.6DraftingDrafted#acme-renewals1 message
3 models · 4 connectors · all within account permissions

Pause at approval gates

Before anything leaves the building — a send, a purchase, a change someone else will see — the run stops and shows you what it is about to do.

  • Consequential steps wait for a person, every time
  • The facts and figures behind a step are shown with it
  • Declining sends the run back a step rather than ending it
approval
Draft is ready for Vicky at Acme. It quotes 214 seats and the annual rate. Sending needs your OK.
what changed since the last one?
Seat count, up from 181. The rate and the terms are the same as March.
SendEdit firstHold

Package the result

What comes back is the work plus its receipts: the artifact you asked for, the assumptions it rests on, and the sources behind each claim.

  • The finished brief, analysis, or file — not a summary of one
  • Assumptions and limitations kept next to the claims they affect
  • Sources you can open and check yourself
Deliverables4 files
acme-renewal-note.docxWord Document · 48 KBHeld in draftsOpen
Q3-usage-summary.xlsxSpreadsheet · 3 sheets
assumptions.mdMarkdown File · 4 noted
sources.mdMarkdown File · 6 · all openable
Open in Google Drive
Download
Open in ZeroTwo
Plan4 steps · 2 need you
Writing planRenew Acme before 30 Sep

Four steps. Two need your sign-off before anything leaves the building.

1Pull Q3 usageneeds DriveQ3-usage-summary.xlsx
2Check against contractneeds Notionseat + integration deltas
3Draft the renewal noteneeds steps 1–2renewal-note.docx
4Sendwaits for youapproval gate
Assumptions
Seat count is billable seats, not invited seats.
The March rate holds unless the contract says otherwise.
Integrations counted per workspace, not per user.
Run1m 12s

Renew Acme before the 30th — and send nothing without me.

Working for 1m 12s
Gemini 3 ProReadingReaddrive://Q3-usage.xlsx214 rows
Gemini 3 ProReadingReadcontract://acme-2025cap 220 seats
GPT-5.5CheckingCheckedcrm://acme/ownerrenews 30 Sep
Opus 4.6CreatingCreatedrenewal-note.docx+214 −0
Opus 4.6DraftingDrafted#acme-renewals1 message
3 models · 4 connectors · all within account permissions
approval
Draft is ready for Vicky at Acme. It quotes 214 seats and the annual rate. Sending needs your OK.
what changed since the last one?
Seat count, up from 181. The rate and the terms are the same as March.
SendEdit firstHold
Deliverables4 files
acme-renewal-note.docxWord Document · 48 KBHeld in draftsOpen
Q3-usage-summary.xlsxSpreadsheet · 3 sheets
assumptions.mdMarkdown File · 4 noted
sources.mdMarkdown File · 6 · all openable
Open in Google Drive
Download
Open in ZeroTwo

What you hand it

A run is only as bounded as its brief. Three things set the edges.

A defined outcome

The file, decision, analysis, or action the run has to produce.

Authorized context

The files and sources the work is allowed to use — and no others.

Approval boundaries

The steps that need review before an external action or a client handoff.

What comes back

Every run returns the same three things, so a result is always checkable.

Work plan
The sequence of tasks, dependencies, and review points
Finished artifact
The brief, analysis, campaign, or code change you asked for
Evidence trail
Sources, assumptions, and checks beside the claims they support
Model choice per step
Which model ran which part of the work, and why
Approval record
What paused, who cleared it, and when
Reusable routine
Any run you approve can be scheduled to repeat

Common questions

It runs the steps you scoped and can do so on a schedule, but this is a workspace for planning, tool-assisted execution, model choice, and human approval — not an autonomous-work guarantee. Anything consequential waits for a person.

Give it something real

Start with one bounded assignment and a clear approval line. Widen it once you have read a run end to end.