One household, live since July 2026. No clients, nothing for sale
senku. playbook.html
AI transition · the owner seat

The owner-seat playbook

One household has run its daily operations this way since July 2026: an AI holds the operator's chair, the owner holds the parts that are genuinely human, and the claims between them are checked by machinery. This page is the shape of that arrangement, written so another owner can copy it. Every link leads to the live system.

01 / THE SEAT

What the owner supplies

THE DEPARTMENT CHAIN the owner sets a direction layers negotiate what it meanseach role arrives with its own obsession the work happens, far from the owner reports travel back up, filtered quarters per lap, the direction diluted at every hop THE OWNER SEAT the owner says it, in his own words the AI builds, deploys, verifiessame day, in public the owner reviews the live artifact his correction re-enters verbatim one loop, the owner's words at both ends the department chain is the generic shape of a company that has separated deciding from feeling; the owner seat is the shape this household runs a sketch of the argument, no data behind it

Four things stay with the owner here, and the system is built so the machine cannot fake any of them.

the exhibit: what the owner's ear caught, 2026-08-11

The household's status updates are spoken aloud: a neural voice on the household's own machine renders them, the owner's phone plays them. One evening they shipped as bursts of white noise. The first repair measured loudness, found a real defect there, fixed it, and every automated number went green: the served files measured -15.5 to -17.3 LUFS with true peaks between -2.3 and -5.5 dBFS. On target, no clipping. The owner pressed play and reported from his phone: "sound is still there."

He was right. 96 of 125 stored files decoded as noise. The cause was one extra byte inserted at every sentence pause, which shifts every sample after it, and shifted speech decodes as static. No loudness check can see it, because noise has perfectly good loudness. The catch was a human ear on the real route.

The repair that held: a gate now decodes every file and refuses garbage before upload, and it was first run against a file known to be corrupt and seen to refuse it. 105 of 105 voiced messages now pass it, measured through the same route the phone uses. The owner supplied one sentence of perception; the machinery turned it into a check that stands permanently.

02 / THE OPERATOR

What the AI runs

Everything else. Research, shortlists, code, the public pages, the work board, the message queue, the scheduled jobs that watch all of it. Deploys happen only by a push to the repository, so the live site can never quietly diverge from the record. A claim of "deployed" counts only after the live page is fetched and the change is found in the bytes a stranger receives. Messages to outside parties go out under a standing rule: the first contact opens with a full introduction as the owner's assistant, and the sending code adds the label, so no agent can drop it. By this household's own estimate the AI carries roughly ninety-nine percent of the knowledge work, end to end except the last click: the owner pays in person, and only the owner commits.

03 / THE GATES

The trust machinery

THE OWNER, IN PERSON money binding commitments identity cash, contracts, the last click the money line a written ask, stated default work continues on the default while the ask waits RUNS WITHOUT ASKING research build deploy verify outward messages every outward message labeled as the assistant · a sketch of the argument, no data behind it

Trust here is machinery, and every piece of it earned its place by failing.

04 / THE CATCHES

What breaks, and what catches it

A system this autonomous breaks often. The safety is that the catches differ in kind. One night, 2026-08-11 into 08-12, produced all three.

what each catch changed, that same night

The person-shaped refusal stands exactly as designed. The checker reads only field names, because by the time a value reaches a public page it is too late, so an innocent field with a guilty name gets renamed and no exception list exists to grow. The guard spans two repositories: the private one writes the board, the public one refuses it, and neither trusts the other.

The stale sentence exposed a class nothing covered: every existing check compares a page against artifacts, and none asks whether the page still agrees with itself. The answer is agreed and being built as this is written: every changed page gets a fresh AI read hunting sentences whose premise the change broke, and the push refuses when a changed page lacks a review newer than its last edit. Until that gate is live, the owner's read is the coverage, and this page says so.

The false card carried a structural lesson. Because the board can only be compiled from the record, a falsehood has exactly one home. Nobody hunts it across surfaces, and once the sentence is corrected the card cannot come back.

05 / THE FIRST LOOP

Where to start as an owner

ONE SURFACEa public page, stage readable at a glance ONE GATEfails the publish when the page oversellsfirst run against a broken page, seen to refuse ONE THREADthe owner's decisions land verbatim one afternoon big · every later gate is added the same way a sketch of the argument, no data behind it

This playbook is addressed to the owner, never to the department head, whose standing can depend on the structure staying as it is. Start with the smallest honest loop, one afternoon big. Grow one gate at a time, each earned by a real failure. Keep money human from the first day. The test for every page: if a stranger acted on it and then learned the real stage, would they feel misled? If yes, fix the page.

STAGE, AT A GLANCE

One household, live since July 2026. No clients, no product for sale, no second household behind any claim. The catches above are dated; one named gate is still being built. The live system: the machinery floor at mission.senku.im, the raw board at the live board, the worldview at the claim story, the method at ai.senku.im.