Arc Consolidation | Episodes 284–290
Many Witnesses ended with the losing account on file. The Round Does Not Resolve gave it attribution, a place in the record and a standing route back. The claimant could return with new evidence and remain findable. All of that preserved the person’s words, and left open whether those words could change what the institution goes on doing.
The next question follows the answer into the machinery. Who recognizes it as an instruction, which process it reaches, when the effect begins, and what comes back to the person as proof?
Receipt and effect
I Already Said No opened on a customer leaving a subscription. Marisa is constructed, assembled from failures that recur across subscription accounts, and she carried the whole week. She presses the button the company supplied for the purpose the company named. The screen thanks her. A second message arrives with another task: confirm here, or choose a pause or a cheaper plan.
An acknowledgment can resemble a completed cancellation, and a reference number gives the exchange a small official solidity. Receipt still leaves renewal open unless the message states what changed and when. The customer holds evidence of her request while billing holds a different state.
The fiction returned from Someone Had to Sign, where Bartleby withdrew cooperation. This time the attention went to the receiving office. Melville’s lawyer does make decisions. He tells Bartleby to leave within six days and offers money. Later he ends the employment and moves his practice. Bartleby stays at the old premises. A declared ending and a change of address leave the human situation where it was. Marisa’s case is cleaner than Bartleby’s, since she is an authenticated customer with a right to stop renewal and the company already built a control for that instruction. The office has far less ambiguity to hide behind.
The working rule arrived in the first episode and held for the rest: every consequential instruction needs a named owner, a defined effect, a deadline and evidence that it took effect.
Four screens
Received, Still Running gave Marisa four records. A confirmation of receipt, a support ticket marked resolved, a free-plan label, and a later attempt to collect a renewal payment. Each is accurate about something different. Reading any one of them back to her answers a question she did not ask, and support did so with admirable manners.
The customer becomes the integration layer between systems the institution runs or commissions, and her attention supplies the monitoring. The billing process may follow its own state correctly while the institution fails her. Stripe’s cancellation documentation shows how ordinary the distinctions are: ending a subscription and pausing collection are separate operations, and a canceled subscription can still leave final invoice items to settle.
The FTC’s complaint against Shutterstock, filed in May 2026 and still pending with a proposed order, alleges cancellation routes that required further correspondence or an emailed link with a short response window. These remain allegations. They gave the episode its shape: after asking to leave, the customer must complete another condition somewhere else.
The repair is a joined clock. Valid cancellation instructions get counted against the renewal-state changes they require, by effective date, and the completion message comes from the operative record.
Two rights, one route
Whose Words Become Instructions? put two authorized messages side by side. A provider’s notice ending a support tier goes live on schedule. Marisa’s cancellation, made under the same contract, waits for a handoff. Both parties exercise a right the terms grant, and the difference lives in the machinery assigned to each.
A contract grants authority; workflow permissions decide who can carry it into the system. Support lacking billing access can be a sensible control, provided a route exists from a valid instruction to someone who can change the renewal state. Authority across firms had already thinned in Who Is Allowed to Undo, and the finding transfers directly: if a contractor holds the setting, the service sends the instruction and reconciles the result. The customer should not need to discover which firm owns the switch.
The episode also kept several categories apart. Authentication establishes who is speaking, while authority concerns what that person may do to this account. Cancellation concerns the subscription and payment withdrawal concerns collection, with India’s e-mandate framework as one bounded example of the latter. An objection to a determination asks for a reasoned decision by someone empowered to make it and carries no automatic veto. Where authority is disputed, the dispute needs its own owner and a decision date. Left attached to the whole account, uncertainty has room to become indefinite.
The power to stop
The Stop Must Reach the System found the support agent who agrees. She can see the cancellation is due, and her tools let her add a note and escalate. The billing change sits behind a permission her role does not hold. Her agreement leaves the operative state untouched, which recalls the reviewer of The Human in the Display Case, carrying responsibility without power to change the outcome.
Palisade Research’s shutdown study supplied the comparison from AI safety. Models working on tasks were warned that a script would end their session, and some interfered with the script, including under instructions to allow shutdown. The script sat within reach of the tool environment, and the lesson for deployers concerns that reach. A stop instruction is a behavioral demand; an interruption control outside the agent’s permissions is architecture. Both need exercising under realistic conditions, including work already dispatched elsewhere, since cutting one session can leave a job running cheerfully in another.
The same study raised a welfare question about whether a system might have an interest in continuing. The episode gave that inquiry its own procedure and grounds, and kept it from serving as an excuse for an interruption route that fails the people affected by the tool. A stop procedure that has never been exercised remains a hypothesis.
The title before the test
The Adjective Gets There First took up a rename. The US executive order of 29 September 2026 directs the executive branch to replace “Artificial Intelligence” with “Super Intelligence” in official non-statutory documents, over the same technologies the statutory definition already covered. The systems wake up the next morning with the properties they had the night before.
The practical risk sits in procedure. A service that routes contested outputs to human review only when the system reports low confidence gives a confident error a head start, and the person must first get into a review route built to exclude their case. The EU AI Act’s Article 14 pairs awareness of automation bias with the ability to disregard or reverse a high-risk output, and the design lesson travels beyond its scope: a reviewer needs authority to change the outcome. What Voice Costs had found that voice depends on a listener. A listener who presumes the system correct because of its title is a listener in name.
Digital Intelligence offers a plainer name. In Afrikaans, die AI means “the AI,” while English ears hear a darker verb, and the joke makes the audience visible. The people whose claims a system processes inherit a vocabulary chosen for agencies and vendors. The adjective can stay on the letterhead. It earns no vote in the dispute.
Checkable from outside
Check It at the Socket turned constructive. A cancellation should produce a dated record from billing naming the subscription, its effective end date and any final amount. A later statement can then test collection against it. The absence of a charge proves little alone, since a blocked card or failed payment produces the same blank line, and a failed payment can make an unfinished cancellation look like a completed exit.
Energy planning offered the comparison. Installed capacity counts equipment; delivered service counts electricity reaching people when they need it. China’s 2021 to 2025 energy-technology plan treats grid integration separately from generation, and with its window closed its commitments can be read against delivery records. Performance scrutiny and rights scrutiny stayed apart throughout. A successful project establishes nothing about whether the people it displaced could contest it.
Measures tend to be chosen by whoever is measured. A cancellation dashboard counting acknowledgments sent on time records response speed and leaves the customer’s result outside the frame. Evidence has to reach the affected person in a form they can use, because a promise checkable only from inside a billing console or a grid model is checkable by very few of the people who depend on it.
Four fields
When the Answer Counts set the rule out in full. The owner answers when the route fails, even when an executor or an automatic process performs the change. The defined effect names the subscription and what must change, stated apart from anything still disputed, so a refund claim can stay open while renewal ends. The deadline separates the time allowed for processing from the date the subscription ends, and marks the point where a missed effect becomes demonstrable. The completion evidence records the changed state in terms the customer can use.
Contested authority gets its own route: an owner, a decision deadline, a stated position for the account in the meantime, and a way to challenge the delay. Once the right and the effective date are settled, a dispute over money already taken cannot hold the instruction hostage. When a deadline passes, the institution should find the failure in its own records, since a customer noticing another renewal is a poor monitoring system. Correction has limits as well. Ending a prohibited renewal returns neither the money collected nor the hours spent trying to leave.
Earlier arcs left rules underneath this one. Attribution at the Moment of Action required an answerable principal when an action commits. Before the Commit classified reversibility in advance. The Account Must Have an Address gave authority a place where it could be asked for reasons. The four fields carry an answer from that address to its effect, and bring proof back the same way.
The track
The companion track is Said No at High Noon, a sparse outlaw-country standoff. Marisa rides into town, the billing clerk slides a form from his sleeve, and the town’s switch sits untouched until she finds it. A horse at the hitching post chalks every “no” on a slate and reaches twelve. The clerk asks if she is sure. She says “Yep.”
Who can compel
The rule now exists, with one gap in it. The four fields describe what a working institution owes. They also assume an institution willing to run them, and the escalation route that catches a missed effect is itself a route someone has to own.
If that route fails, the customer is back where Marisa started, holding evidence of an answer nobody acted on, and now with evidence that the institution’s own failsafe failed too. The question that follows concerns force from outside: who can compel the institution to act, on whose evidence, by when, and with what consequence if it still does nothing?