marketer fizz

A fresh take on AI.
A sharper take on marketing.

Updated AI, marketing and what comes next.
Conceptual artwork: a hand lifts a continuous paper trail for inspection at an amber clamp on cobalt rollers.
← Marketer FizzPerspective · 15 Nov 2026

Who is still watching when the AI keeps working?

Handing over a job is easy to describe. The harder story is who can change it, stop it and decide that the result is ready.

Original conceptual artwork created with AI assistance for Marketer Fizz.

Something in Simon Willison’s box room kept beeping. He asked the AI coding assistant Claude Code for software that could locate it using several listening devices. Finding the sound would also mean finding a way to correct the software while the job continued.

01

First, make the work visible

Automatic placement did not work well, he writes. He asked to drag device positions himself, then replay sounds and identify the one he wanted. The continuing job needed a way for its human operator to see and correct it.

The retained placement revision adds draggable positions, sequential replay and a confirmation control. A later saved-session revision keeps earlier sessions readable during repositioning. These are specific changes in what the person can inspect and alter.

Willison reports finding an old carbon monoxide detector that needed new batteries. That ending belongs to his account; we did not perform an independent physical test. His cloud starter and later local work are separate stages, and the full linked conversation remains uninspected. The retained revisions let us examine the narrower change in how he could intervene.

02

Two jobs leave different records

Separately, Plato founder Robert Farlow told Business Insider he stopped OpenAI’s Dot agent from coordinating the office move after movers complained about repeated emails. He says he did not use Dot for the replacement movers; he continued using AI to draft, reviewing before sending. The edited interview records his account, rather than an inspected execution log. The publication says OpenAI did not respond to its request for comment.

The contrast concerns visibility. In the personal task, retained code shows new controls for intervention. In the move account, an outside complaint made the effects of continuing work visible to the operator. Neither tells us how often such events occur.

Read the two lanes as separate tasks. The first pairs an author’s account with retained code; the second attributes an edited interview. Written evidence states show where each record ends. Card spacing does not represent elapsed time.

What each record lets the reader see

Retained code and reported actions have different evidence states. Each lane shows what can be checked within its own task.

Personal task: author account and retained code

A person gains controls for intervention

  1. Author account: locate a hidden sound

    Willison describes asking for software to locate an intermittent beep using several devices. Prompt times are uninspected.

  2. Retained code: place devices roughly

    Revision d5b5148, 9 November 20:42:12 UTC, adds draggable device positions.

  3. Retained code: replay and confirm

    The same revision adds sequential replay and a control for the person to confirm the sought sound.

  4. Retained code: preserve earlier sessions

    Revision 5b1ac7e, 9 November 22:09:43 UTC, separates saved-session views from live repositioning.

  5. Author-reported result

    Willison reports finding the detector. The full shared conversation and independent physical result remain uninspected.

Willison’s 9 November account, paired in prose with two retained revisions ↗ · Checked 2026-11-15

Operator account in an edited interview

A complaint changes the process

  1. Reported delegation

    Plato founder Robert Farlow describes assigning office-move coordination to Dot.

  2. Reported recipient response

    He says movers complained about repeated emails.

  3. Reported intervention

    He describes stopping Dot and choosing different movers. He continues using AI to draft, with review before sending.

  4. Execution record uninspected

    This edited interview does not supply an inspected execution log, repaired output or acceptance decision.

Business Insider edited operator interview, published 9 November ↗ · Checked 2026-11-15

Source relationships and written evidence states remain visible without colour or motion. Commit times and interview publication dates do not establish execution clocks. Neither task supplies the other’s missing endpoint.
03

The maintainer accepts this change

A third task supplies a more concrete endpoint. Datasette, a tool for publishing data, retains a revision that changes labels, button descriptions and associated tests. Its maintainer, Simon Willison, merged PR 3052 on 8 November at 21:20:01 UTC. We inspected the code and record, rather than executing the tests.

That merge gives this particular change an attributable endpoint. Willison is both the project’s maintainer and the author of the separate review-description account, where he explains how he selects a short introduction for an agent’s longer description. The person receiving the work should be able to see what deserves their attention.

An attributable endpoint for a separate task

  1. Retained revision

    Revision 5c7c304 changes labels, button descriptions and associated tests. Code was inspected; tests were not executed.

  2. Maintainer merge

    PR 3052 records Simon Willison’s merge on 8 November at 21:20:01 UTC.

  3. Bounded acceptance

    The merge accepts this change. It does not establish that unattended work will succeed elsewhere.

The original brief and human-authored correction request are uninspected. This is an endpoint for one change, not a reliability measure. Datasette PR 3052 and its revision history · 2026-11-15
04

A stop is one event. Acceptance is another.

Stopping a run concerns whether work continues. Permission authorises a particular action. Acceptance records a recipient’s decision about a result. Those events can occur at different times and involve different people.

The three records here expose different parts of that responsibility: an operator gains controls, a complaint prompts intervention, and a maintainer accepts a particular change. None supplies another task’s missing history.

For someone commissioning continuing work, the useful question is concrete: can the person responsible inspect the instruction, changed work, intervention and result in the same record? A claim that an agent is working is only one entry. The recipient’s decision still needs somewhere to live.

Our earlier visual report on work after image generation follows the same handoff in a campaign brief: a technically finished file still needs creative acceptance.

The detail

What each record establishes

Separate tasks, with different source relationships.

What each record establishes. Separate tasks, with different source relationships.
RecordEstablishedStill uninspected
Personal sound searchAuthor account and retained placement, replay, confirmation and session-view revisions.Full conversation, independent physical result and recipient sign-off.
Office moveOperator’s published description of delegation, complaint and intervention.Underlying execution log, repaired work and acceptance.
Datasette changeRetained revision and maintainer merge for this task.Original brief and human-authored correction request.
Original editorial comparison of evidence states; no reliability score, common experiment or savings measurement.Source: Original sources linked in each row · 2026-11-15

Sources & reporting

Checked 15 Nov 2026. This perspective combines reporting from the sources below with our editorial interpretation.

Written with AI assistance. Fizzy is our fictional reporter persona. Our editorial approach.