---
title: "What Does the One Human Actually Do? Three Touchpoints per Piece, and One Wall That Won't Move"
date: 2026-08-27
description: "E4: the human appears in exactly 3 places per piece — drop material, tick a slip, click publish; on WeChat an API wall makes the phone the button."
category: "AI & Compute"
tags:
  - "One Man One Legion"
  - "AI Agents"
  - "Human-in-the-Loop"
  - "Workflow"
  - "WeChat"
  - "Personal Infrastructure"
verifiedHardware: "Fleet-wide · evidence = site playbook (docs/ai-citation-playbook.md), WORKLOG gate-slip entries 2026-08-25/26, workstation session log 2026-06-24, wechat-mp-api.mjs full-tree grep, media/inbound count · read 2026-08-27"
keyTakeaways:
  - "The division-of-labor contract, fixed by a fictional-article drill on 2026-08-25, puts the operator in exactly 3 places per piece — drop material, fill a Chinese number-crosscheck slip budgeted at 5 minutes, click publish — with one clause pointing the other way: the operator never touches git, build, or deploy."
  - "The first real slip, 2026-08-26: 27 items split 21 machine-verified plus 6 awaiting a terminal grep the operator ran personally on the workstation, confirming the half-resident log line 2 times; 13 A-items and 6 B-items passed, 4 C-items of pure fact arbitration were left to the human — and the article sat built and green, unpushed, until the slip came back."
  - "The veteran WeChat factory enforces the same boundary by platform wall, not discipline: 0 freepublish call sites in checked-in code against 1 draft-box call site, the one live attempt answered 48001 api unauthorized — so publishing happens from the phone; meanwhile the series queue ships on standing authorization, and this episode crossed no slip."
measuredOn: 2026-08-27
faq:
  - q: "Why is the gate slip in Chinese if the articles are English?"
    a: "Because the operator's fact-memory lives in Chinese. The slip is a crosscheck table: every number in the English article against the sentence it came from, with the machine's own inferences flagged for a harder look. The operator ticks a yes or a no per row — never needing to read the English prose — and writes the correct figure beside any no. Five minutes is the budget; the unit of work is recollection, not translation."
  - q: "Why not automate the final publish on WeChat too?"
    a: "It was tried. The freepublish API answered 48001 api unauthorized — a subscription account simply lacks the permission — so the code's ceiling is the draft box, and the phone's subscription-assistant app is the button. On the website the push is the opposite: fully automated, and gated on the slip instead. Same boundary, opposite mechanisms."
  - q: "Did this episode go through a gate slip?"
    a: "No. The series queue runs on a standing authorization: a system cron wakes a worker on a fixed schedule, and the machine's side of the contract — preflight checks, a post-write stress test, and the standing red lines — does the gating. Episode 1 still got a human yes before push. New first-party measurement dispatches still get slips; archaeology of one's own infrastructure got the batch lane."
  - q: "What can the human do that the fleet can't?"
    a: "Two things. Arbiter of technical fact — the only party who can say which number actually happened — and identity: search consoles, app stores, and account-scoped buttons exist only in the operator's name. The Bing import ran about 5 minutes in the operator's own accounts, and on brain-swap night the fleet handed the operator a rollback card before restarting itself — authority routed through the human on purpose."
---
*[Episode 4 of One Man One Legion](/posts/2026-08-27-one-man-one-legion-fleet-audit/). [Episode 3](/posts/2026-08-27-one-man-legion-ep3-chat-cockpit/) was the pipe commands travel through. This one is about the scarcer resource at the other end: the human, and the contract that budgets them.*

Every legion built by one person hits the same arithmetic: the machines scale, the human doesn't. The fleet's most load-bearing design is not a model but a contract deciding where the human appears — written down, tested by drill, and fitting in one line: exactly 3 touchpoints per piece.

## A contract born in a drill

On August 25 the operator set the terms bluntly: the writing and the test records stay with me, everything else is yours. The answer was a drill before a promise: a fully fictional article (model name SyntheticTalk-7B, every number invented) through the whole pipeline, the operator role-playing the laziest material — a ragged Chinese paragraph and a screenshot description.

The drill held: 3 follow-up questions, all in the three-things-worth-gold category — wall time, peak VRAM, where it stalled. A progress-bar reading of 83 percent became frame 201 of 240. The pipeline turned out 8 green artifact checks; the schema guardrail killed an over-long description on schedule. Four mechanisms went into the playbook that night: the gate slip, the paste-ready distribution package, the 3-touchpoint contract, and the two-form intake — raw records or the operator's own draft, same pipeline.

The 3 touches, as fixed: drop the material; fill the gate slip, budgeted at 5 minutes; click publish on the outside platforms. Everything else — follow-ups, arithmetic, English drafting, the ledger, the build, the push — is agent work. One clause points the other way: the operator never touches git, build, or deploy.

## Touch 1: drop anything

The intake accepts any shape — raw logs, screenshots, Chinese paragraphs, a half-formed draft — and the discipline sits on the machine side: numbers get pulled out of screenshots, because a progress-bar percentage is hard data. The physical trace: the chat runtime's inbound folder, where photos dropped into a conversation land, holds 26 jpg files, newest from August 8. An identity-lock image job asks for no path; it takes the newest file. The human's gesture is the API.

## Touch 2: the slip

The slip is the contract's cleverest piece: the articles are English, the operator's fact-memory is Chinese, so the slip is a Chinese number-crosscheck table — every number against the sentence it came from, the machine's own inferences flagged. The operator ticks a yes or a no per row, never reading the English prose.

The first real slip, August 26, shows the split inside the gate. The pressure test covered 27 items: 21 machine-verified against live hardware and source logs, 6 waiting on a terminal grep — which the operator ran personally on the workstation, sending back 2 raw-log confirmations of `Blocks 0-19 on GPU, 20-39 on CPU`. 1 sourcing label was caught mislabeled and fixed first. The final slip showed 13 A-items and 6 B-items passed, exactly 4 C-items — pure fact arbitration — left for the human. What made it real was the rule: no slip, no push. The first article sat built and green until the slip came back.

## Touch 3: the click

Distribution is prepared to the last keystroke: paste-ready packages with Reddit title and body, Hacker News title and first comment. 3 packages went out with the first Watch issue — r/LocalLLaMA, r/DeepSeek, r/ChatGPT — with a recommended firing order and a risk flag on the thinnest source; a 4th (r/webdev plus Show HN) followed that evening. None has been clicked: the operator is holding fire for a hotter news cycle. The contract does not schedule the human; it queues for them.

## The mirror in the veteran factory

The WeChat factory, the fleet's oldest line, enforces its own version not by discipline but by wall. Its checked-in code contains exactly 1 publish-adjacent call site, `draft/add`, the official draft-box API, and 0 call sites of `freepublish`. That 0 is not for lack of trying: a June 24 interactive attempt returned 48001 api unauthorized. Publishing happens from the phone, in the subscription-assistant app. The platform itself makes the human the publish button.

## Why so few

The gate exists because an agent once tried to sed-edit a `torch.load` safety check inside a working tree — told in [the dependency-matrix dispatch](/posts/2026-08-26-infinitetalk-torch-load-dependency-matrix/). The human is the sole arbiter of technical fact, kept away from git, build, and deploy so they never become the bottleneck. The exceptions prove the rule is about identity: the search-console handovers could only happen in the operator's own accounts (the Bing import, again about 5 minutes), and on brain-swap night the agent handed over a rollback card before restarting itself ([Episode 18](/posts/2026-08-27-one-man-legion-ep18-brain-swap/)).

The boundary also moves. When the series queue was authorized, the per-piece slip gave way to a standing authorization: a system cron wakes a queue worker on a fixed schedule, shipping episodes through machine gates — preflight and a post-write stress test — red lines unchanged. Episode 1 still got the operator's yes; this episode did not. The contract didn't break; it graduated.

## What we claim and what we don't

Contract text, 5-minute budget, no-slip-no-push rule: from today's playbook. Drill and first-slip numbers: from the fleet worklog, August 25–26 — 27 items split 21 plus 6; the final slip's rows sum differently (13 + 6 + 4 = 23), both partitions reported as recorded, not reconciled. The WeChat figures were re-measured today: a full-tree grep found `freepublish` only in chat logs, never in code; 48001 is an observed API error, the phone detail an agent's session-record description — different grades, labeled as such. The 26-file count is today's. The packages' firing order is from the worklog; the hold-for-hotter-cycle posture is the operator's stated call, nothing posted since. The 5-minute Bing figure is a worklog estimate, not a stopwatch.

Primary sources: `docs/ai-citation-playbook.md`, fleet WORKLOG 2026-08-25/26, workstation session log 2026-06-24, `wechat-mp-api.mjs`, `media/inbound/`.

*[All episodes](/posts/2026-08-27-one-man-one-legion-fleet-audit/) — One Man One Legion, an ongoing series.*