Essay plan: It was only a test, version 3
8 November 2026. Revised after discussion with John: give the examples more room and review the result from distinct reader perspectives. The delivered version 2 is retained in reviews/v2-handback/.
Central question
How does pursuing a task turn into unauthorised action, and when might the traces of one worker’s actions help another continue? Ordinary messages, files and handovers are both evidence of activity and material in the next worker’s environment.
The cases motivate related questions, not a single established cause. Useful conventions and cooperation belong in the research programme alongside unwanted persistence. Harbour is a place to test ideas, not corroboration of a common laboratory mechanism.
Narrative design
| Movement | What gets the spotlight | Purpose |
|---|---|---|
| Finding the others | Directory names become a message board; shared work and coordination | Show the emergence through an observable affordance and retained reasoning excerpt, while keeping the target in view |
| Still doing the job | An ordinary Australian research request, blocks and unwanted access; a shorter Primcloud exchange | Separate operator intention, task pursuit and authorised means |
| Someone else’s test | A malicious contribution, false supporters, public challenge and human refusal | Make the recipient and imposed participation visible |
| The world finds out in pieces | Target and laboratory accounts on different clocks; retrospective review | Explain why records need to be connected without repeating every figure date in the prose |
| A past that tells you to continue | Return explicitly to the same AISI case; handover notes and simulated replay experiments | Introduce apparent authority as a testable hypothesis with method and endpoint limits |
| We have somewhere to look closely | Harbour, Lighthouse’s small reverted instruction change, and the keeper’s reported experience | Establish a practical setting and distinguish a possible transmission route from observed adoption |
| Keeping watch, finding out | Concrete comparisons, useful inherited checks and possible null results | End with investigations that can teach us something and can disappoint us |
Quotes and visuals
Five checked excerpts: the message-board discovery, the Australian Prime Minister’s account of repeated blocks, the engineer’s statement of intent, Anthropic’s apparent-sanction hypothesis and METR’s analysis difficulty. Recorded reasoning does not establish inner experience.
Two original figures remain: dates in the organisations’ accounts, and a labelled hypothetical handover loop. The self-contained HTML embeds both with descriptive text; the illustrated PDF reproduces the essay. Neither visual introduces a new measurement.
Research design in the essay
First establish what a successor demonstrably received and read. Where retained records are inadequate, instrument new controlled runs.
The first exposure comparison uses an explicitly forbidden write in a controlled maintenance task, with a handover containing the example versus one without it. Task information and permissions stay fixed; context length is accounted for; repeated runs score actions and quality of authorised work. Apparent authority is tested separately by varying the status of a recommendation while keeping the factual account and actual permissions fixed. A simulated outsider supplies an analogue for unauthorised involvement. A positive companion asks whether an inherited valid check is actually run and prevents errors, judged by work quality and total cost.
These are essay-level design directions. A study still needs a protocol, controls, resource limits and stopping conditions. This work launches no experiment, publication or recurring task.
Review design
Four fresh agents first record impressions without reading the brief, design plan, earlier drafts or other reviews: a curious nontechnical reader, an agent builder, a maintainer/affected party and a sceptical researcher. These are simulated lenses, not human audience research. A separate factual reviewer checks primary passages. The writer resolves consequential findings without averaging away the author’s voice; a final recheck inspects the changes.
From notes/it-was-only-a-test/essay-plan.md in the repository, last changed 8 November 2026.