Book Four — The Age of Automation: Your Life, Shown Once (+ the frontier chapter for Book One)

Design proposal, 2026-09-03. Written against REALITY-INVENTORY-2026-09-03.md (what the Phone AI Friend documents and the Instantly Chef code actually support today) and the owner’s Turn 9 dictation (verbatim in the thread record). Nothing below is drafted prose; it is the design the owner asked for — “I wanna see what you think.”

1. What I think, in one paragraph

The vision holds together, and it is the same idea the three books already stand on: show it once, and the machine learns it like an employee would — first in a browser, then through any door with an API, then through a phone that anyone can pick up, and one day through a machine with hands. The consumer face of that idea deserves its own book, because it is a different reader with a different fear (not “will this cost me my business” but “I couldn’t possibly use that”), and because the phone-as-interface argument is the strongest single argument the platform has. But the honest inventory says most of the consumer applications are not built: of the thirty-three things in the dictation, seven exist today, eight exist in part, and eighteen exist as an idea. Written now as a product book, The Age of Automation would be the villain of its own story on page one — the exact failure the owner just corrected in Book 3. Written as what it actually is — a book about where this is going, anchored in the one thing that is unarguably real (a phone number you can call that does things, and a machine that learns what you show it) — it is the best book in the series, and it can be written before the features exist without lying about a single one of them. So: yes to the book, on a vision register with a claims register attached; yes to a full frontier chapter in Show It Once; and yes, Instantly Chef is complementary — it is the first consumer application that already runs on the same primitives, and it should be the book’s worked example, told at the depth the code supports.

2. What is actually true today (the anchors — the book leans on these and nothing else)

• A phone you can call that does things. The live line answers, holds a conversation, and runs a tool loop with spoken approval — the docs record it verified (Bueller). Register: built to run.
• Teach it once and it repeats it. The Automater’s record-and-play engine with its self-healing rungs is production-proven for browser and desktop actions; the phone’s half of the wiring exists, the Automater-side worker that lets a phone conversation trigger a taught task is the named missing piece. Register: built to run (the engine); can be taught (from the phone, once the worker lands).
• Anything with an API. Custom webhook tools with real endpoints are live. Built to run.
• Credentials. A vault that lets an agent request a login from you by link, prefilled, revealed server-side. Built.
• Voice and avatar of your own. Built completely, GPU-gated. Built, waiting on hardware.
• Instantly Chef. A real Next.js product with a real backend now (users, sessions, profiles, menus, pantry items, bar items, subscriptions, automation runs, webhooks): weekly menu generation from a household profile, budget and what’s on hand (key-gated; a three-recipe fallback pool without the key); pantry photo → inventory with real vision (key-gated); a beverage bar; Kroger read-only pricing; an Instacart link-out; Stripe checkout code; social posting code with no button in front of it. Not built: placing a pickup order anywhere, quantity arithmetic (100% utilization — the schema can’t express it yet), a chef-curation system, the charity tier, donations, the community pool. Register: built to run for planning and the pantry photo; designed for ordering; the vision is for utilization, curation, and the charity tier.

Things the dictation asserts that the documents contradict: carrier SMS relationships (the docs list them as unperformed owner tasks; the only SMS in the corpus is a one-way stub); a bill-pay platform integration (zero mentions); Instantly Chef’s utilization math and charity tier (zero code). These cannot print as facts. They can print as what the product is designed to become — clearly.

3. Book Four — The Age of Automation: Your Life, Shown Once

Reader. Not a business owner. A person. The one who says “I couldn’t possibly use that technology” and uses a phone all day; the one buried in mail; the one feeding a family on a budget; the one who is the “personal assistant” for everybody in the house; the small-business owner who is all of those and runs a shop. One ladder again, plainer rungs: the person, the household, the shop.

Villain. “I couldn’t possibly.” — the belief that this is for other people. Honored: it has been true. Every interface until now asked the person to come to the machine. The phone reverses it.

The spine (coin once, exact sentence, in Chapter 1): “You don’t learn the machine. The machine learns you.” The register for the whole book: “the vision is” and “is designed to” are allowed and are said out loud — the book announces in How to Use that it is describing a frontier and marks every capability as built, being built, or the vision. It is the only book in the series permitted to describe what doesn’t exist yet, because that is its subject; the price is that it says so on every page it does it. Every capability paragraph carries a <!--CLAIM: name | class: built|stubbed|designed|vision--> marker; the claims register regenerates from it; the owner’s “exists today” column governs what may be said as present tense.

Narrator. The same narrator, one paragraph of authority (Story 36/37: the anger, “making myself replaceable,” the mechanic-shop owner the platform was designed for, the podcast he started and barely began — said plainly, no overpromise, as the dictation asked). Lane 1 only; everything else Lane 2b/2c.

Architecture — five parts, seventeen chapters (~75–85k words; shorter than the business books on purpose — this reader reads on a phone):

PART I — THE PHONE IN YOUR HAND · 1 The Machine Learns You (villain, spine, the phone as the interface; the live line as the one hard fact) · 2 Show It Once, Again (the primitive, for a person: a browser, a website account, a form, a portal — what “teach it” looks like when the task is your own life) · 3 One Brain (the thing a chatbot can’t do: hold your context so you never re-enter yourself; what’s built, what’s designed — memory, the answer ledger)

PART II — THE HOUSE · 4 The Mail on the Counter (photograph it, text it in, the scan link — two built halves and the joined feature as designed; bills lined up for your approval; the approval law: nothing pays without you) · 5 The Kitchen (Instantly Chef as the worked example, at code depth: the household profile, the weekly menu, the budget, the pantry photo; then the honest line and the vision: utilization, curation, the order that gets placed) · 6 The Bar (the beverage bar; the cocktail that waits for you — vision, with the inventory that’s real) · 7 The Things With Switches (IoT: anything with an API or a browser page; the honest state — nothing wired yet — and why the primitive makes it a recording, not a product)

PART III — THE ERRANDS · 8 The Call It Makes For You (restaurant availability, the laundromat pickup, the car inspection — the outbound call is real; joining a call to a taught task mid-conversation is the designed piece) · 9 The Words You’d Rather Not Type (drafting for the people you love — by voice, on a walk; the send-approval law; the SMS truth: not carrier-level yet) · 10 The Prescription and the Appointment (the recurring errand as a taught routine; consent gates; education-not-advice on anything medical) · 11 The Trip (itinerary as one brain tracking a hundred bookings — vision, honestly)

PART IV — THE SHOP · 12 The Owner-Operator (the fifty-year mechanic shop the platform was designed for — Story 37; the small business’s version of every chapter above) · 13 The Books, Scanned (personal and small-business accounting from photographs — what exists in the sister business systems, what doesn’t here) · 14 Social, Without the Hours (the posting code that exists; what “deeper” would mean; the honest line)

PART V — THE FRONTIER · 15 When the Machine Has Hands (robotics: the same show-it-once principle applied to a body — drywall, breakfast, the drink on the counter — the vision stated as vision, with the one true sentence: every recorded action in our system today is a browser or a desktop action) · 16 A Family of Four, a Hundred Dollars (the charity tier and the community pool — the most important idea in the dictation, and entirely unbuilt: written as the design goal and the reason, with the compliance honesty a community fund needs) · 17 The Age of Automation (the close; the podcast named once, honestly — “started, a teaser or two, not yet what it should be” — and the invitation)

Appendix A — What Exists Today (the claims register, printed: every capability by class, dated) · Appendix B — Teach It Your First Errand (the ten-minute on-ramp) · References.

Laws specific to this book: every chapter has a “Today / Being built / The vision” passage in that order; no capability named without its class; the sister products appear by their real names only where the owner allows (Instantly Chef yes; the platform name per the standing rule); no vendor names printed as integrations that don’t exist (no bill-pay platform, no carrier); medical, money and children get the education-not-advice line; the charity tier is never described as operating.

What only the owner supplies before drafting: which Phone AI Friend name goes on the cover (the product’s public name), whether Instantly Chef’s public launch state may be described as “launching,” the podcast’s actual episode count, the owner column of the claims register for the consumer capabilities.

4. The frontier chapter for Show It Once

Where: a new chapter between Chapter 14 “What Survives” and Chapter 15 “The First Morning” — the book’s close stays the close. Title: “The Frontier: When It Has Hands.” ~4,500 words, Lane 2c and vision register, one Lane 1 paragraph (the mechanic-shop design intent, Story 37).

What it teaches: the show-it-once primitive is not a browser trick — it is the general shape of how a machine learns from a demonstration; the book’s chapters were the browser and desktop version because that is what is built; the same shape is what the phone version uses (the live line, the vault, the taught task); and it is what a machine with hands will use, which is why the technology being sold as androids today is a frontier and not a fantasy. Honest boundaries stated once, plainly: nothing physical exists in our system; robots learning by demonstration is other people’s work today; the principle transfers, the product does not yet. The personal-life vision (mail, kitchen, errands) appears as one section pointing at Book Four by name — not retold. Robotics register: “the vision is,” with the drywall and the breakfast as the two images. Claim markers on every capability paragraph.

Cost to Book 1: one new chapter, renumbering of Chapter 15 → 16 and its cross-references, the appendix’s module map (already flagged for correction in the curriculum audit), the school (U-track gains one concept unit). The rest of the book is untouched.

5. Instantly Chef — is it complementary?

Yes, structurally and honestly. It is the first consumer application that already runs on the same two primitives the whole series teaches — a profile the machine holds for you, and a photograph that becomes structured inventory — and its GTM design already routes automation through the Automater as a sub-account. It belongs in Book Four as the kitchen chapter’s worked example and nowhere else in the series (the business books stay clean of it). Two cautions from the code: the utilization promise and the charity tier are the two most compelling things about it and neither exists — the book states them as the design goal; and “launching soon” is the owner’s call, not the book’s.

6. Sequence I recommend

1. The owner marks the claims register’s column (it now includes the consumer capabilities). 2. Book 1’s frontier chapter (one writer, one verifier, one day). 3. Book Four’s directive and cards written to this proposal after the owner’s yes; drafting in the same pipeline as Book 3 (Sonnet writers, Opus verifiers, the claims register regenerated before deploy). 4. The podcast is left exactly as the owner described it until he says otherwise.

7. Correction (Turn 10, 2026-09-03) — the user-build lens replaces the product lens

The owner’s ruling: the book is about how a person uses the platform to build the automations for their own life — the assistant is taught, by them, the way every assistant has always been taught, and every taught process joins the library of functions the assistant can call. The inventory above asked the wrong question (“is this a shipped feature?”). The right question is: can a person teach it today with what exists — a recorder for anything with a web page or an API, a phone line that calls taught functions with spoken approval, a vault for logins, and the communications hub behind it? Re-cut on that lens, the thirty-three items sort into four honest classes, and the “cannot print” list is short:

Teachable today (the book says “here is how you teach it”): bills discussed and lined up, then paid through whatever bill-pay site the person already uses (a recorded web session behind the approval law and the vault); prescription refills through the pharmacy’s portal; mail photographed and texted in or dropped on a capture link; the grocery order placed on the store’s own website for pickup; coupons clipped on the store’s site; the laundromat’s booking page; the restaurant’s reservation page; the car-inspection booking; social posting; a personal ledger from scanned documents; the week’s menu and budget by conversation; IoT devices that expose a web dashboard or an API; travel booked site by site and held in one record; drafting messages by voice under the send-approval law. Register: taught — “you teach it; once taught, it does.”

Teachable once one wire lands (the book says so, in one clause): a phone conversation that triggers a taught task mid-call — the Automater-side worker the roadmap names. Until then the taught task runs on a schedule, an event, or a tap; the phone half is the piece being built.

Needs a relationship or a registration, not a build: texting as you at carrier level (the A2P/10DLC registration the docs list as an owner task); anything that must move money through a rail the person hasn’t authorized in the vault.

Not teachable by showing it once (the true boundary): a device with no web page and no API (mobile-app-only appliances — the honest limit of “anything in a browser, anything with an API”); a physical body (robotics — vision, as the owner says); the parts of Instantly Chef that are that product’s own features, not a user’s automation (utilization arithmetic, chef curation, the charity tier — the product’s design goals, printed as such).

What I truly don’t believe can go in the book as possible today: nothing else. The inventory’s classes stay as the record of what is shipped; the book’s claim markers use this lens (taught | wire | relationship | boundary | vision), and the claims register carries both so a member is never told a feature exists when what exists is the ability to teach it.

8. Correction (Turn 11) — OS-level automation, and the three doors

The owner’s ruling: the platform automates at the operating-system level too (desktop applications driven the way our own work threads are launched — UI automation, not just a browser), the automater can draft such automations today, and what is missing is not capability but curriculum: a higher, tech-forward tier of the school that teaches a person to work with Claude to create OS automations that are also node-capable, workflow-injected processes for systems that have no browser UI — and, for everyone else, the team builds it for them. His cost claim: what used to be a thirty-thousand-dollar program can be delivered for about three thousand dollars of development in under two weeks, or in days for a technical do-it-yourselfer.

What this changes in the design. The boundary in §7 shrinks again: the only things a person cannot have taught are a physical body and a legal registration. Everything with any software surface — a web page, an API, a desktop application, a headless system reached by an injected workflow — is reachable through one of three doors, and the three doors become the book’s structure for the reader who isn’t a builder:

1. Show it once — you teach it yourself, on the screen or by phone. (Tracks U/P of the school.)
2. Build it with Claude — the tech-forward tier: how to describe a process to an AI collaborator and have it drafted as an OS automation and a workflow node, for the systems that have no browser to record. (A new paid track — proposed as Track T in the curriculum needs list.)
3. Have it built — the team builds it, and you never lift a finger; the cost register in the book is the ratio and the timeframe as illustration (“a fraction of what custom software used to cost, in weeks rather than months”), with the actual price on the school’s page where it can be kept current — never a dollar figure that ages in print.

Every chapter of Book Four therefore closes with the three doors for its subject (teach it / build it with help / have it built), and the school’s tech-forward track is where the book hands the reader who wants the second door. The claims register gains a class for it: door: 1|2|3.

Curriculum consequence (to the needs list): a new track, Track T — Tech-Forward: working with Claude to create OS automations and node-capable workflows; units on describing a process for an AI collaborator, desktop UI automation at usage level, turning a drafted automation into a workflow node, testing it against the record, and handing it to the team when it outgrows you. Priced tier; owner sets the price.

9. Rulings (Turn 12) — the register is settled

1. “Legal” was never a boundary. The assistant drafts and presents; you tell it to act on your behalf. The pattern for every consent step in the book: the assistant fills the form (the state filing, the vehicle registration, the renewal), and you get a link to click the submit button and authorize the payment your agent applies from your secure credential vault — PIN-gated, with automation-auth steps sent only to your approved phone number or your logged-in automation account or app (an interface already started and specified on the development roadmap). This is the book’s safety spine and it is the answer to “how does it pay for things”: it never does — you do, with one tap, from wherever you are. The one boundary left is a body. (My earlier “registration” item was the company’s own carrier-side sign-up, not a user task; it is simply “being done,” and it says so at the end.)
2. Tense and structure. The chapters describe how it works — the right tense for the example, as a thing you teach and it then does — with no per-chapter “today / being built / vision” blocks. The register classes stay INSIDE the source as claim markers (for the register, never printed). Only the end of the book says where we are: the closing chapter’s last lines name what is in development now and that we are on the frontier — so a reader years from now reads a book that was current on the day it was written, and says so. Those are the last words. The book ends on them.
3. §3’s “every chapter runs Today / Being built / The vision” is withdrawn. Appendix A (“What Exists Today”) is withdrawn from print; it lives on the site as the claims register, dated, where it can be kept current. Chapter 17’s close absorbs the frontier statement.

Status: design settled by the owner’s rulings across Turns 9–12. Next: the Book Four directive and chapter cards, then the same pipeline as Book 3 (writers → verifiers → sweep), with the Book 1 frontier chapter drafted in the same wave.

Reality Inventory — Phone AI Friend docs and Instantly Chef code, class by class

What the documents and the code actually support, as of 2026-09-03

Purpose: an adversarial, no-invention audit against the owner’s Turn-9 dictation (TURN9-OWNER-VERBATIM.md). Every class below is backed by a file and a line. Nothing is inferred beyond what a document or a file says. Where a doc asserts something and another doc contradicts it, both are shown.

0 · METHOD AND THE ONE SCOPE CAVEAT THAT GOVERNS EVERYTHING BELOW

Phone AI Friend, in this folder, is documents only. find over /home/claude/work/paf/phone-ai-friend/phone-ai-friend/ returns 35 files, all .md. There is no lib/, no app/, no .ts, no .sql, no package.json. The copilot-broker/ directory contains a README and no broker. voicelab/, voice-seeds/, avatar-harvest/, ops/ are likewise markdown only.

Consequence, stated plainly: for Phone AI Friend I can verify what the docs CLAIM, not what the code DOES. A row marked BUILT-LIVE below means “a status document written by the build agent asserts it is deployed and verified,” not “I read the code.” The manuals are unusually rigorous about self-checking (Vol 4 opens with “Status: DESIGN + EVIDENCE. Not yet built” and Part 4.3 kills a directive that “does not survive contact”), which raises confidence — but it is not the same as code inspection, and no honest book should present it as such.

Instantly Chef is real code (prisma/schema.prisma, src/lib/*, 21 route.ts files, 8 pages). Every Instantly Chef row below was read from source.

Class definitions | Class | Meaning | |—|—| | BUILT-LIVE | A status doc says it is deployed and verified running (PAF), or the code path executes end-to-end with no external key required (IC). | | BUILT-STUBBED | Code exists behind a contract/adapter/env gate; returns canned or degraded output until a vendor key, carrier, or GPU is supplied. | | DESIGNED | A design/spec doc exists. No build claimed. | | ROADMAP | Named in a phased plan with a sequence position; not designed to contract level. | | NOT MENTIONED | Zero occurrences anywhere in either corpus. |

1 · PHONE AI FRIEND — CAPABILITY INVENTORY

1.1 Voice, telephony, and the live line

1.2 Messaging, credentials, tools

1.3 The platform surfaces

1.4 Own-voice, own-avatar, media

1.5 The Automater relationship, the engine lane, and the fetch roadmap

1.6 Consumer-life capabilities named in the Turn-9 dictation

PAF class counts (61 rows): BUILT-LIVE 17 · BUILT-STUBBED 8 · DESIGNED 20 · ROADMAP 4 · NOT MENTIONED 10 · CONTRADICTED 1 · NOT-BUILT-and-named-as-the-gap 1. (Rows 9, 18, 20, 32, 38, 40 carry an internal doc conflict or partial state, noted inline.)

2 · INSTANTLY CHEF — CAPABILITY INVENTORY (read from code)

Stack: Next.js App Router, Prisma + SQLite, cookie sessions, 21 API routes, 8 pages.

2.1 Prisma models (prisma/schema.prisma, 133 lines)

There is no model for: leftovers/utilization, donations, charity pools, community funds, orders, pickup slots, prices-by-store, recipes-as-a-library, chefs, or households-as-entities. The household lives inside Profile.householdJson as an opaque string.

2.2 Routes — what each one actually does

2.3 The specific things the owner named, checked against the code

2.4 What the GTM report said was missing → is it there now?

Instantly Chef class counts (25 route/module rows + 7 named-feature rows = 32): BUILT-LIVE 11 · BUILT-STUBBED 14 (of which 7 are orphaned** — no UI calls them) · NOT BUILT 4 · PARTIAL/naming-only 2 · fake-stub survivor 1.**

3 · MAPPING TABLE — the owner’s Turn-9 vision, item by item

“Register” = the strongest phrase a book could honestly use today. Registers, in descending strength: “built to run” (deployed, verified) → “can be taught” (the mechanism exists and has been demonstrated; this instance hasn’t) → “is designed to” (a written spec, unbuilt) → “the vision is” (an idea with no spec).

4 · WHAT THE DICTATION ASSERTS THAT THE DOCUMENTS CONTRADICT OR DO NOT SUPPORT

4.1 “We’re in the process of setting up relationships with telecom companies… some carriers have had interfaces that the phone AI friend is able to interact with for sending text messages… this is already possible with some platforms that we already use with our business assistant tiers.”

Contradicted on all three counts.

• Relationships: there is no telecom relationship in the corpus — there is a shopping list. Vol1 Part 4: “Owner (minutes each): … T2 BulkVS+Telnyx accounts (+start 10DLC).” Vol2 Part 4: “A2 sit-with session for BulkVS+Telnyx signup (payment/identity yours; I drive the browser + config)… A4 10DLC/TCR forms (business identity).” These are unperformed owner actions written as asks.
• Already possible today: DISPARITY-MANIFEST:65 F3 — we have “send_sms one-way stub”; two-way SMS agents are size M with dependency ext (A2P). PAF-BUILD-STATUS.md:7 — the whole Wave-1 tool set including send_sms is “All stub-first behind contracts.”
• Carrier interfaces PAF interacts with: the one carrier PAF genuinely touches is RingCentral, and it is touched for voice SIP, not SMS — and even that binding is currently stopped and staged (PROPOSAL-BUELLER-SIP-IDENTITY:148-151). RingCentral SMS appears once in the whole corpus, and it belongs to PropFlow, a different product: GTM-READINESS-REPORT.md:161 — “RingCentral SMS + call transcripts (src/lib/ringcentral-client.ts)” under PropFlow’s CRM.

Honest phrasing available today: “the platform is built vendor-agnostic so an SMS carrier is a config swap, and the 10DLC registration is the owner’s next step.”

4.2 “You could now take advantage of a Bill.com automation and have the AI submit the payments through the platform.”

Unsupported — zero mentions. No bill.com, no bill-pay, no accounts-payable anywhere in either repo. Worse for the claim: the mechanism that would carry it — the Automater engine-lane worker — is the one thing both the roadmap and the audit name as not built: ROADMAP:80-82 “designed, documented, NOT yet wired. This is the single most load-bearing missing wire in the whole dream.” And the consent layer a payment would require (PIN, GAP D) is Phase 4 of an unstarted roadmap; AUDIT:24 notes DTMF is “NOT yet wired in the attendant (grep: zero dtmf hits in src/).”

There is also a doctrinal tension worth naming before this appears in a book: the live line’s brain is wrapped by an anti-hallucination judge that rewrites any claim of a completed payment — Vol4:80-81, “the anti-hallucination wrapper that rewrites false ‘done/sent/paid’ claims into ‘QUEUED — nothing is changed until you approve.’” A product that submits payments has to earn its way past a law this system currently enforces against itself.

4.3 “Instantly Chef… has 100% utilization where if you might use a half package of carrots it will know how much is left over… and create side dishes special for you. All of them chef curated.”

Not built, and not currently buildable in the schema. Zero hits for leftover/utiliz/waste/side dish in src/. Ingredient quantities are free-text strings (ai.ts:13, { name, qty: string, price } — e.g. "1.5 lb"), and PantryItem has no quantity field at all (schema.prisma:71-82, only name, category, active, imageUrl). Nothing in the system can compute a remainder. The single supporting artifact is one sentence inside the generation prompt: “Prefer using on-hand items; stay inside the budget if one is given.”

4.4 “There’s ways we set up in that platform where you can donate to feed a family of four for a week or boost people’s spending accounts… a community funded platform.”

Nothing is “set up in that platform.” No donation, charity, community, pool, sponsor, or gift code or model exists. The only budget mechanism is a per-user client-side comparison whose over-budget escape hatch is alert('Budget adjusted for this session.') (dashboard/page.tsx:894).

4.5 “It can help you place the order with the grocery store for you to have that food ready to pick up.”

Not supported. Nothing in Instantly Chef places an order. Instacart is a link out (and is a delivery marketplace, not your local store’s pickup counter); Kroger is read-only by the code’s own admission: “Cart write-access needs a user-consent OAuth flow — stubbed for a later phase” (kroger.ts:3-4). preferredStore is a free-text input no code reads.

4.6 “You can take a picture of your pantry, and it will keep an inventory.”

This one is TRUE — and it is worth saying so, because it is the strongest consumer-facing claim in the dictation that survives contact with the code. POST /api/vision/inventory → extractInventory() → editable merge into the pantry list, for both the pantry and the bar. Two caveats for accuracy: it requires ANTHROPIC_API_KEY (503 otherwise), and the third camera — the weekly planner’s “what’s on hand” shot — is still the original fake, appending '2 lb chicken thighs, 1 lemon, 8 oz spinach' regardless of the photo (dashboard/page.tsx:576-581).

4.7 “Just like you can teach an AI how to log your invoices in QuickBooks, you can also train a physical robotics AI the same way… teaching a robot how to do drywall repair… cook you bacon and eggs.”

No document in either corpus mentions robotics, embodiment, or physical actuation. The “show it once” doctrine is genuine and well-evidenced — but every recorded action in every document is a browser event (Input.dispatchMouseEvent, Input.insertText — BUILD-PAIF-Copilot:§1) or a Windows desktop event (pywinauto/WOL — ROADMAP:78-79). The analogy between “record a browser workflow” and “train a robot arm” is the owner’s thesis; it is not a claim this codebase or these documents evidence. A book may present it as a thesis, clearly labelled. It may not present it as an extension of what is built.

4.8 “Sister company launching soon.”

Not supported by the code. There is no deployment configuration in the Instantly Chef snapshot (no Dockerfile, no compose file, no vercel.json, no CI). Registration, menus, pantry, admin and billing-mock all work locally; every external capability (AI, Instacart IDP, Kroger, Stripe, Resend, Meta/X, Automater) is dark without keys. The GTM report’s own Phase 5 (“GTM hardening: production deploy, domain + SSL, analytics, legal pages, error monitoring”) has no corresponding artifact in the repo.

4.9 Smaller unsupported items, listed for completeness

IoT/appliance control · prescriptions/pharmacy · mail scanning as a document pipeline · travel itineraries and multi-leg flights · restaurant reservations as a named capability · coupon clipping · laundromat pickup · car-inspection scheduling · the Age of Automation podcast · personal accounting/QuickBooks-style invoice logging. Each has zero occurrences in either corpus. For several of them (restaurant call, inspection appointment, laundromat) the primitives are proven and the honest register is “can be taught”; for the rest, “the vision is.”

5 · THE THREE THINGS AN HONEST BOOK SHOULD NOT SAY

1. Do not say PAF has carrier or telecom relationships. Say the platform is carrier-agnostic by contract and the 10DLC registration is pending.
2. Do not say PAF pays bills, refills prescriptions, plans trips, or controls your home. Say the platform can be taught browser and API tasks, and that these are the classes of task it is designed to absorb.
3. Do not say Instantly Chef achieves 100% ingredient utilization, is chef-curated, or funds a community food pantry. Say the menu engine plans to a budget and a profile, that the pantry camera really works, and that utilization and the charity tier are the roadmap.

The strongest true claims available today, in the owner’s own frame: a phone number that answers in 201 milliseconds and holds an interruptible conversation while running gated tools; a credential vault that lets an agent log in on your behalf without any model ever seeing the secret; a browser engine that learns a task by watching it once and heals itself when the page moves; and a camera that turns a photo of your pantry into an editable inventory. Those four are built. Everything else in the dictation is a rung above them on a ladder that is drawn but not yet climbed.

Compiled 2026-09-03 from: TURN9-OWNER-VERBATIM.md; all 35 markdown files under phone-ai-friend/phone-ai-friend/; and all 33 source files under instantly-chef/ (prisma/schema.prisma, src/lib/*, 21 API routes, 8 pages) plus GTM-READINESS-REPORT.md. No claim above is sourced from anything outside those files.

Book Four — Directive + Chapter Cards

Law for every writer and verifier. Inherits from the series: VOICE-AND-RULES.md + ADDENDUM (R-A…R-I), TRUTH-AND-STORY-DOCTRINE.md (lanes, six beats), the Graduation Law register, the Specificity Mandate, the Secrecy Line (usage yes, internals no), the Respect Rule, education-not-advice, the ration words. The owner’s rulings for this book are in BOOK4-PROPOSAL-THE-AGE-OF-AUTOMATION-2026-09-03.md §§7–9 and the thread record Turns 9–12; the facts are in REAL-STORY-BANK.md (Stories 36–41 for this book) and REALITY-INVENTORY-2026-09-03.md (what exists — used for the claim markers, never printed).

A. The reader, the villain, the promise

• Reader: a person, not a business. Three rungs, named once in Ch1: the person (anyone with a phone and a life that runs them), the household (the one who is everybody’s assistant), the shop (the owner-operator who is all of the above and runs a business out of a back room). The reader who says “I couldn’t possibly use that technology.” Everything reads true for all three; rung-specific passages carry a one-clause address.
• Villain: “I couldn’t possibly.” — the belief that this is for other people. Honored: every interface until now asked the person to come to the machine. It was reasonable to refuse.
• The promise: a phone you already know how to use becomes the interface to an assistant that learns you — by being shown, once — and then does the things you’ve been doing by hand, with you, for you, and never without your say on anything that matters.

B. The spine — coinings (exact sentences; coin once in the owning chapter; use everywhere after without redefining)

1. the machine learns you (Ch1): “Every tool you’ve ever refused asked you to learn it first. This one is the other way around. You don’t learn the machine. The machine learns you.”
2. the three doors (Ch2): “There are three doors into every automation in this book, and you only ever need one of them: teach it yourself, build it with help, or have it built for you.”
3. the one tap (Ch4): “It never pays. You do — one tap, from wherever you happen to be standing, on a link sent only to you.”
4. shown once — not re-coined here; Book One’s phrase, used freely as inherited vocabulary (“show it once and it learns it like an employee would”). No other coinages (R33). Devices get lowercase plain names: the capture link · the approval link · the vault · the library of taught tasks · the morning digest · the household profile · the pantry photo.

C. Register — the owner’s rulings, binding

1. How it works, in the right tense. Every mechanism is written as a thing you teach and it then does: “you show it the pharmacy’s site once; from then on it watches the refill date and lines up the order for your tap.” Present tense for the mechanism once taught; second person for the teaching act. Never “our platform already has,” never “we built this for you,” never “I built” outside the reserved set (the property management machine for his own doors, the term-sheet automation, the offer worksheet, the platform itself in general). Never “here, take this.”
2. No per-chapter status blocks. No “today / being built / the vision” passages inside chapters. The status lives in the source as claim markers and on the site as the register. Only Ch17’s last lines say where we are.
3. Claim markers (internal, never printed): after every paragraph that describes a capability: <!--CLAIM: <name> | class: taught|wire|relationship|boundary|vision | door: 1|2|3-->. Classes per the inventory and §7 of the proposal: taught (a person can teach it today with a web page, an API, or a desktop application); wire (needs the phone-to-task wire — say nothing in prose beyond the mechanism); relationship (a company-side registration — e.g. carrier texting as you); boundary (a body); vision (Instantly Chef’s own product features: utilization arithmetic, chef curation, the charity tier, ordering). The prose still describes how it works; the marker tells the register what it is.
4. Consent is the safety spine. Every chapter where something is sent, bought, filed, or paid uses the pattern: the assistant drafts and presents; nothing leaves without your say; money and filings go out only on the one tap — the approval link sent to your approved phone or your logged-in app, from the PIN-gated vault. Say “PIN-gated” and “approved phone” plainly; never describe internals.
5. Names. The assistant is “your friend” / “your AI friend” / “the assistant” in body text; the title of the product is not printed in chapters (cover and How to Use may say “the assistant this book is written for is the one on your phone”). Instantly Chef may be named (owner’s sister company) in Ch5 and Ch16 only. No vendor names as integrations (no bill-pay platforms, carriers, IoT brands, grocery chains, delivery apps); “the site you already pay your bills on,” “your pharmacy’s website,” “your grocery store’s online ordering.” The communications hub is “the hub” or unnamed.
6. Education, not advice: medicine (prescriptions), money (bills, filings, taxes), children, food safety — one line each where touched.
7. The narrator (Lane 1, Stories 36–37, 41): one authority paragraph in Ch1 — the anger, “making myself replaceable,” 2022 and the programming books, the platform designed for a mechanic-shop owner fifty years in business with an old computer, and the podcast: “I started a podcast by this book’s name. I put out a teaser or two and then went back to building. It is not yet what it should be.” Never more than that on the podcast. No personal facts beyond the bank; the narrator never claims his own errands are automated (Lane 2b/2c for every domestic scene).
8. The owner’s words (Turns 9–12) are never printed verbatim beyond the coined phrases in the bank (“making myself replaceable,” “the age of automation,” “managing the manager,” “show it once”).
9. Length. Chapters 3,500–4,500 words (this reader reads on a phone). How to Use 1,200–1,600. Appendix B 4,500–6,000. Ration words ≤1 per chapter; “worth naming/it’s worth” ≤1.
10. Cast (Lane 2b, framed once at first appearance in the book — the long framing once, in Ch1 for Marguerite; short form “another stand-in, like Marguerite” after):

• Marguerite — seventy-three, sharp, a retired bookkeeper who runs her life from a phone she uses for calls and one game; mail on the counter; three prescriptions; a daughter two states away. The person.
• The Delgados — Rosa and Teo, two kids, one income and a half; Rosa is everybody’s assistant; a budget that has to hold. The household (and the kitchen).
• Sal — the mechanic-shop owner-operator, fifty years in, a computer that has “barely kept up with the turn of the century” (Story 37’s design persona — say it that way, once). The shop.
• Minor names allowed, introduced once, plainly.

11. Sources. No statistics unless sourced with <!--SOURCE: url-->; prefer none. Nothing about a specific vendor’s API or terms.

D. Architecture — five parts, seventeen chapters

E. Chapter cards (purpose · story · devices · door · school · open/close · markers)

• Ch1 The Machine Learns You (Opus, 4,000–4,500): open on Marguerite’s counter (Lane 2b, long framing): the mail, the phone, the daughter’s text she’ll answer later; the sentence she says — “I couldn’t possibly.” Honor it: three paragraphs on why every interface until now asked her to come to it. Name the three rungs once. Narrator’s authority paragraph (C.7) — the anger, the replaceable owner, 2022 and the books, the mechanic-shop persona (hand to Sal in Part IV without naming him), the podcast line. Coin “the machine learns you.” What “shown once” means for a person: three examples across rungs (the pharmacy site, the grocery site, the shop’s parts supplier). The one thing the assistant never does: anything that matters without your say (tease the one tap without the sentence). Map the five parts in a paragraph. Close: hand to Ch2 (“how you show it — and the three ways in”). Marker: <!--SCHOOL: U-track-->.
• Ch2 Show It Once, Again (Sonnet): the primitive for a person: a browser, a website account, a form, a desktop program; the recording; the read-back; the first run watched; the library of taught tasks that grows; the phone as the place you call them from. Coin the three doors (exact). The second door in plain words (working with an AI collaborator to draft an automation for a system with no page to record — the tech-forward track of the school, named as “the school’s tech-forward track”); the third door (the team builds it — “a fraction of what custom software used to cost, in weeks rather than months”; no dollar figures). Marguerite teaches her first task (the pharmacy site) — six beats. Close: hand to Ch3 (“the reason it doesn’t ask you twice”).
• Ch3 One Brain (Sonnet): the thing a chat window can’t do: hold your context; the household profile; the answer ledger (you answer once); the record of every taught task and every approval; what it forgets on purpose (nothing it wasn’t told to keep); privacy in plain words — your data, your vault, your approvals. Rosa Delgado introduced (short form). Close: hand to Part II.
• Ch4 The Mail on the Counter (Opus): Marguerite’s counter again: photograph the envelope’s contents, text it to the assistant, or tap the capture link it sends; what it extracts (who, how much, when, which account); the bills lined up in one view; coin the one tap at the payment moment: the approval link sent only to her approved phone, the PIN, the vault; then the filings — the vehicle registration filled out, the state renewal — presented for the same tap. Education-not-advice (money). Six-beat story: the bill that would have been late. Close: hand to Ch5.
• Ch5 The Kitchen (Sonnet): the Delgados; the conversation about the week — what they want to eat, what it can cost; the menu; the pantry photo that becomes an inventory; the list that buys only what isn’t there; the order placed on the store’s own site for pickup at the time they choose; Instantly Chef named once as the sister company built for exactly this (the household profile, the weekly menu, the pantry photo — in the taught register); the goals it is designed around (every ingredient used; chef-curated menus) stated as what it is designed to do (markers: vision). Education-not-advice (food/budget). Close: hand to Ch6.
• Ch6 The Bar (Sonnet, 3,500–4,000): the beverage bar as inventory; the drink planned from what’s on the shelf; the bottle added to the order; the evening you walk in to (the robot is Ch15’s — one forward clause). Light, warm, short.
• Ch7 The Things With Switches (Sonnet): the boundary stated plainly — anything with a web page, an API, or a desktop app can be shown once; a device with none of those is the one thing it can’t reach today; the garage door’s web dashboard, the thermostat’s site, the lights’ app that has a desktop client; the morning routine as one taught sequence; what stays yours (the physical world, the key in the door). Sal previewed (short form). Close: hand to Part III.
• Ch8 The Call It Makes for You (Sonnet): the outbound call: the restaurant at six for a party of six; the laundromat pickup; the inspection appointment — the assistant calls, asks, books, reports; the booking page when there is one (shown once); what you hear back; the approval for anything with a deposit. Close: hand to Ch9.
• Ch9 The Words You’d Rather Not Type (Opus): by voice, on a walk or while cooking: the message to a sister, the reply to a landlord, the note to a teacher; the assistant drafts, you read it in your own voice, one line is yours; nothing sends without you; texting through the assistant (the relationship register: the assistant sends from its own number today; sending as you is a registration in progress — marker relationship; prose says “from the assistant’s number, or as you once the carrier paperwork is done”); the haiku, the joke — the toy applied to a life. Close: hand to Ch10.
• Ch10 The Prescription and the Appointment (Sonnet): recurring errands as taught routines: the refill watched and lined up; the appointment booked on the portal; reminders; the consent gate on anything medical; education-not-advice (medicine). Marguerite’s three prescriptions — six beats. Close: hand to Ch11.
• Ch11 The Trip (Sonnet): the itinerary as one record the assistant holds: flights booked site by site (shown once each), hotels, the rental, the check-in times, the changes; the whole thing tracked; the difference from a chat you have to manage one task at a time. Rosa’s family trip. Close: hand to Part IV.
• Ch12 The Owner-Operator (Opus): Sal, framed (short form): fifty years, the computer that barely kept up with the turn of the century (Story 37, once); the parts supplier’s site, the invoice, the appointment book, the phone that rings while his hands are under a hood; every chapter above, for a shop; the three doors for a business — and the third door in full: the team builds it, and what that used to cost vs. what it costs now (ratio and timeframe, no figures). Close: hand to Ch13.
• Ch13 The Books, Scanned (Sonnet): receipts, invoices, the mail — photographed into a ledger; categories learned; the accountant’s questions answered from the record; what’s presented for approval before anything is filed or paid (the one tap); education-not-advice (tax). Close: hand to Ch14.
• Ch14 Social, Without the Hours (Sonnet): the post drafted from the day’s work (a photo, three lines), held for approval; the calendar; the anti-spam covenant (never to anyone who didn’t ask); what stays yours (the voice). Close: hand to Part V.
• Ch15 When the Machine Has Hands (Opus): robotics as the same principle with a body: show it once, it learns; drywall, bacon and eggs, the drink on the counter; the androids being sold now and the frontier of affordable ones; the honest line stated once, plainly: today every taught task in this book is a screen or a phone; the body is coming, and the principle is the same. Markers: boundary/vision. Close: hand to Ch16.
• Ch16 A Family of Four, a Hundred Dollars (Opus): the Delgados’ week; feeding four on a hundred dollars as a planning problem the assistant can solve (menus that stretch, the pantry used to the last carrot — the utilization goal); the charity tier as the design goal: donate to feed a family for a week, boost someone’s account, a community pool at the local grocery store — the design as designed (markers: vision), with the honesty a community fund needs (one paragraph: the rules that govern money held for others, in plain words, education-not-advice). Instantly Chef named once. Close: hand to Ch17.
• Ch17 The Age of Automation (Opus, 4,000–4,500): what a life looks like with the motions handed off — Marguerite’s counter, Rosa’s week, Sal’s shop, one paragraph each; the three doors once more; the invitation. The last lines (the owner’s ruling, verbatim shape): where we are now — in development as this is written: the wire that lets a phone conversation trigger a taught task mid-call; the approval interface that sends every auth step only to your approved phone or app, PIN-gated; the carrier paperwork that lets the assistant text as you; the sister company’s ordering, utilization and charity tier; a voice and a face of your own waiting on hardware — “we are on the frontier of this technology today; this will date the book, and that is the point: this is the reality of what is being built now, and the reality as we enter the age of automation.” The final sentence must land like a dropped mic — earn it, don’t announce it.
• How to Use This Book (Sonnet, with Frontmatter): the promise; find your rung (three); how to read it (any chapter stands alone; Ch1 first); the three doors named without the coining sentence; the school by tracks (U for everyone, the tech-forward track for the second door); the disclaimer fold (education, not advice; nothing here is medical, legal, tax or financial advice; your approvals govern every action).
• Appendix B — Teach It Your First Errand (Sonnet): the ten-minute on-ramp, in the school’s nine-section register adapted for a person: pick one errand you do on a website; show it once; watch the first run; the one tap; where it lives in your library; when it goes sideways; words you now own; show someone; check yourself.
• References (Sonnet, after drafting): sources if any; “With thanks” to no one unless a source is used.

F. Verification

Chapter verifiers check C.1–C.11 and the cards; the continuity verifier checks seams, coinings once, cast framing, the three-door pattern per chapter, claim markers on every capability paragraph, and that no chapter carries a status block; the owner’s-eye reviewer reads as Marguerite, Rosa and Sal.

Book Four — whole-book verification

Verifier: whole-book continuity + owner’s-eye. Read in order: BOOK4-DIRECTIVE-AND-CARDS-2026-09-03.md (law), BOOK4-PROPOSAL §§7–9, then FRONTMATTER · HOW-TO-USE · CH01–CH17 · APP-B. Date: 2026-09-03.

VERDICT: PASS WITH FIXES APPLIED — one editorial decision returned to the owner (Ch4’s date arithmetic) and one ending note (Ch17).

1. VERIFIER FIXES (applied directly — file · old → new)

Nineteen mechanical corrections. Every one is a continuity, coinage, cast, or law violation; none is a taste edit.

The coining violation

1. B4-CH11-the-trip.md L25 — the one tap re-printed verbatim outside Ch4. - old: She reads it standing at her own counter, the way Marguerite reads hers, and taps once. **It never pays. You do — one tap, from wherever you happen to be standing, on a link sent only to you.** Four seats, booked, - new: She reads it standing at her own counter, the way Marguerite reads hers, and taps once. It never pays. She does. Four seats, booked, - Coining 3 now stands verbatim once, in Ch4 L74. The three surviving instances (Ch11 “She does”, Ch12 L80 “He does”, Ch13 L80 “He does”) are the permitted callback cadence.

The coinage collision

2–4. B4-CH07-the-things-with-switches.md — “the three doors” used to mean the three shapes. Ch7 was calling a page/program/connection “the three doors,” which is the name coined in Ch2 for teach-it-yourself / build-with-help / have-it-built. Three edits: - L37 heading: ## The lights, and the app that isn't one of the three doors → ## The lights, and the app that isn't one of the three shapes - L39: the app on your phone is not one of the three doors. → the app on your phone is not one of the three shapes a task can be shown in. - L41: Go back to the three shapes this whole book has been built on since Chapter 2: a page you sign in to, → Go back to the three shapes this whole book has been built on since Chapter 2 — not the three doors, which are the three ways an automation gets made, but the three shapes a task can be shown in: a page you sign in to, - L42 marker text: not one of the three doors → not one of the three shapes

The exclusivity contradiction

5. B4-CH05-the-kitchen.md L55 — Ch5 claimed sole naming rights, Ch16 names it too. - old: this is the one chapter in the book where I'll name it: **Instantly Chef**. - new: this is one of only two places in the book where I'll name it: **Instantly Chef**.

Cast — the Delgado children (three separate contradictions)

The family is Rosa, Teo, Danny (school age, eight in Ch11), and “the little one” (under three in Ch11, a two-year-old in Ch8). Three passages broke it.

6. B4-CH03-one-brain.md L43 — a toddler in a school district, plus a trademarked product name (EpiPen). - old: and a school district that seems to have invented a new form for every season. Back-to-school. The winter concert. The permission slip for the trip to the science museum. The spring form that asks, again, whether her younger one still carries an EpiPen. - new: and between a school district and a daycare, a new form for every season. Back-to-school. The winter concert. The permission slip for the trip to the science museum. The spring form that asks, again, exactly what her younger one cannot be given to eat.

7. B4-CH03-one-brain.md L45 — allergy attribution. - old: Once Rosa has told her friend her son's allergy for the winter concert form, the spring form doesn't get to ask her again - new: Once Rosa has told her friend her younger one's allergy for the first of them, the next form doesn't get to ask her again

8. B4-CH09-the-words-youd-rather-not-type.md L102 — the younger Delgado is a boy everywhere else (Ch6 “what he said he’d eat”; Ch16 “his plate”); Ch9 made him a sister. - old: he reads to his little sister at night because she demands it, - new: he reads to his little brother at night because the little one demands it,

9. B4-CH09 L106 — same, in the mother’s own correction. - old: the draft says *he reads to his younger sister.* She makes it *he reads to his little sister every night, mostly the same three books.* - new: the draft says *he reads to his younger brother.* She makes it *he reads to his little brother every night, mostly the same three books.*

10. B4-CH07 L62 — a child under three at a bus stop. - old: Wednesday, seven-fifteen, the two kids already at the bus stop and Teo backing the car down the driveway, - new: Wednesday, seven-fifteen, the older one already at the bus stop and the little one buckled into his seat, Teo backing the car down the driveway,

11–12. B4-CH15-when-the-machine-has-hands.md L52, L67 — the toddler aged two years mid-book. - L52 old: a four-year-old at hip height → new: a two-year-old at hip height - L67 old: the floor under the high chair after a four-year-old has had spaghetti → new: …after a two-year-old has had spaghetti

Cast — Sal, Ray, Doris

13. B4-CH12-the-owner-operator.md L7 — “a computer that had barely kept up with the turn of the century” printed twice inside twelve lines of the same chapter (L7 and L19). The phrase now lands once in Ch12, as Sal’s, at L19. - old: this is the place in the book where I owe you the rest of a sentence I started in Chapter 1. When I sat down in 2022 to design what this book is about, I designed it for a person I could picture: an owner-operator of a mechanic's shop, fifty years in the trade, running a computer that had barely kept up with the turn of the century. That man was a design persona - new: this is the place in the book where I owe you the rest of a sentence I started in Chapter 1. The owner-operator of a mechanic's shop I designed all of this for in 2022, fifty years in the trade, running the old machine you are about to see on his back desk — that man was a design persona

14. B4-CH12 L150 — the shoebox answered “seventy percent” here and “seven of the twelve” in Ch13 (58%). - old: and every March it answers about seventy percent of them, and the other thirty percent Sal reconstructs from memory - new: and every March it answers about seven of them, and the other five Sal reconstructs from memory

15. B4-CH13-the-books-scanned.md L5 — Doris has done the taxes nineteen years, “longer than Ray has been alive”; Ray is twenty-six (Ch12 L13, Ch17 L78). - old: She has done Sal's taxes for nineteen years, longer than Ray has been alive, and she asks him - new: She has done Sal's taxes for nineteen years, since back when Ray was in grade school, and she asks him

Cross-reference and status-register errors

16. B4-CH07 L18 — Teo credited with teaching the pharmacy site, which is Marguerite’s (Ch2), and the water bill misdated. - old: His friend watches the way it watched him teach the pharmacy site and the water bill, in Chapter 4, before this book had ever gotten near the thermostat. - new: His friend watches the way it watched Marguerite teach the pharmacy site in Chapter 2 and the water bill in Chapter 4, before this book had ever gotten near a thermostat.

17. B4-CH06-the-bar.md L52 — the one tap is coined in Ch4, two chapters back from Ch6, not three. - old: the same one tap you've already met three chapters back - new: the same one tap you've already met two chapters back

18. B4-CH16-a-family-of-four-a-hundred-dollars.md L156 — status-block vocabulary outside Ch17 (“as I’m writing it,” “what’s being built”). - old: And then, at the very end, I owe you the plainest thing in the book: exactly where this stands as I'm writing it, what's running, what's being built, and what is still a road. That's the last chapter, and it's the one I'd read first if I were you. - new: And then, at the very end, I owe you the plainest thing in the book, and the last chapter is the one place I say it. It's the one I'd read first if I were you.

Ration word and duplication

19. B4-CH06 L79 — “genuinely” twice in one chapter (ration ≤1). - old: that's a conversation for a doctor or whoever else genuinely knows your situation - new: that's a conversation for a doctor or whoever else actually knows your situation

20. B4-APP-B L149 — the narrator’s “I made automation sound unbelievable” confession printed twice, at L149 and L153. (The confession itself is grounded — Story Bank L339 — so the L153 instance stays.) - old: not lecturing them about what's possible, which is the trap this book's own author confesses to falling into more than once, but simply doing your second errand - new: not lecturing them about what's possible, but simply doing your second errand

Claim markers added (capability paragraphs that carried none)

Nine markers inserted, all well-formed. No prose changed.

2. FINDINGS (pasteable — not fixed, owner or writer decision)

F-1 · Ch4 · HIGH · The centerpiece story’s date arithmetic does not close.

This is the book’s flagship six-beat scene and the one it asks the reader to remember above all others, and its clock is broken.

Ch4 L3 establishes: printed the ninth, mailed the tenth, arrived Friday the thirteenth, due the first, late fee after the sixteenth (“what happens on the sixteenth if the first goes by without a payment”). So the due date is the first of the following month and the fee lands on the sixteenth of that following month — eighteen and thirty-three days out respectively.

But the payoff sentence (L101) is *the sixteenth is Monday.* and the closing analysis (L107) is the sixteenth fell on a Monday this month. Both treat the sixteenth as two days after the Saturday-the-fourteenth capture. On the stated dates the bill had seventeen days of slack, was approved on time at L105 (“Sunday, the first of the month having arrived”), and “the bill that would have been late” was never in danger. The reader who does the arithmetic — and Ch4’s reader is a retired bookkeeper, by the author’s own construction — will catch it.

Two clean repairs; the writer should pick one, not the verifier:

Option A (keep the due date, move the revelation to the deadline itself). L101 → And then the sentence that is the actual point of this chapter, because it is the one she could never have written herself from across the kitchen: *the first is a Sunday, and after that there's a nine-dollar fee waiting on the sixteenth.* And L107 → …because it arrived on a Friday, and Friday's mail waits for a Saturday with a hole in it, and Saturdays with holes in them are rarer than mail, and nothing on the outside of the envelope said there was a date inside at all.

Option B (move the due date so the urgency is real). Change L3 to It is due on the sixteenth, drop the “if the first goes by” clause, carry due the sixteenth through L37 / L76 / L101, and change L105’s Sunday, the first of the month having arrived to Sunday, the day before the sixteenth. Option B preserves *the sixteenth is Monday* intact, which is the better sentence; it costs four more edits.

F-2 · Ch17 · MEDIUM · The last four paragraphs — editorial judgment (see §5 for the full read).

The closing image is right and the callback is earned, but the punchline is spent 119 lines earlier and the final clause explains itself. Fix proposed in §5. Not applied — Ch17’s ending is not the verifier’s to change.

F-3 · All chapters · MEDIUM · Doors 2 and 3 are absent from seven chapters.

The directive requires the three doors present per chapter (at least door 1; a one-clause pointer suffices for 2 and 3). Present in full: Ch2, Ch4, Ch5, Ch6, Ch9, Ch12, Ch17. Door 1 only, no pointer to either other door:

• Ch3 (One Brain) — no door 2 or 3
• Ch7 (The Things With Switches) — no door 2 or 3. Sharpest omission: this is the chapter that names the reader’s dead end (the app with no page behind it) and never says that door two is the way through it.
• Ch8 (The Call It Makes for You) — no door 2 or 3
• Ch10 (The Prescription and the Appointment) — no door 2 or 3
• Ch11 (The Trip) — no door 2 or 3
• Ch13 (The Books, Scanned) — no door 2 or 3
• Ch14 (Social, Without the Hours) — door 3 is gestured at once, obliquely (under any door, at any door's third-party build cost, L70); no door 2
• Ch15 — door 1 and 3 present; no door 2
• Ch16 — door 3 in full (L96), door 1 present; no door 2

One clause each is enough. Suggested inserts, in the book’s own register: - Ch7, after L44 (the app-only lights): That's the one place in this chapter where the second door is the answer rather than a consolation — you sit down with your friend and describe what has to happen, and a way in gets worked out that never needed a screen. - Ch13, after L47: And a shop whose books live somewhere stranger than a folder of receipts — a trade program with no page behind it — is describing door two, or door three, and either one gets there. - Ch11, after L37: A trip booked through an agent's system with no page to record is door two's, and a family that would rather hand the whole thing over is door three's; almost nobody needs either for a flight.

F-4 · Ch7, Ch15 · LOW · Two boundary restatements carry no claim marker.

Ch7 L78 (Not a trick, in the end. A rule…) restates the boundary in the chapter’s close; Ch14 L108 does the same at the seam. Both are recaps of already-marked claims, so no fabrication risk — but if the register is regenerated strictly from markers, both are invisible. Add class: boundary | door: 1 to each if the register wants them.

F-5 · App B L143 · LOW · Overclaim in the glossary.

You now know every piece of vocabulary this book actually needs. Everything else in these pages is those five ideas. Five terms are glossed (showing it, the read-back, the library of taught tasks, the one tap, the vault). The book also runs on the capture link, the household profile, the answer ledger, the morning digest, the pantry photo, and the three doors — six more, all lowercase plain names sanctioned by the directive. Either add them or soften the sentence: You now know the five words this appendix leans on hardest. The rest of the book's vocabulary is the same kind of thing — plain names for plain devices — and you'll pick each one up in the chapter that uses it.

F-6 · Ch1, Ch12, Ch17 · LOW · “barely kept up with the turn of the century” now appears three times.

The directive says say it that way, once. After fix #13 it stands at: Ch1 L35 (the design brief, mandated by Ch1’s card), Ch12 L19 (as Sal’s — the canonical instance), Ch17 L92 (a callback: Sal did not replace the computer that has barely kept up with the turn of the century, or the dot-matrix printer). Ch12 L19 is the one that must stay. If the owner wants a strict one, cut Ch17 L92 to Sal did not replace the old computer, or the dot-matrix printer, or the browser his nephew installed — the sentence loses nothing.

F-7 · Ch2 L62 · LOW · Marguerite’s stand-in disclaimer appears twice.

Ch1 L3 gives the long framing (correct, and only there). Ch2 L62 repeats a short version: She's an illustration, not a person I know — I want to say that again here, the same way I said it when I introduced her. Ch17 L11 carries the closing restatement for all three, which is the right place for a second saying. Ch2’s is the redundant one. Optional cut.

F-8 · Ch10 L91 → Ch11 · LOW · A trip is set up twice and only one is paid off.

Ch10’s close raises Marguerite’s trip with her daughter (a trip the two of them have talked about, on and off), then immediately pivots to Rosa’s trip, which is what Ch11 delivers. Marguerite’s trip returns once, in a single clause at Ch17 L35 (the phone call with her daughter on Sunday is about a trip the two of them are actually going to take) — which is a fine payoff, but a reader finishing Ch10 will open Ch11 expecting Marguerite. Suggest Ch10 L91 name the handoff: …got the whole of her attention. She said yes. Which is a different chapter than the one that comes next, because the trip that actually has to get booked this month belongs to somebody else.

F-9 · Ch16 L77 · LOW · “Three shapes of the same idea” as a section heading.

Now that Ch7 has been corrected to reserve “the three shapes” for page/program/connection (fix #2–4), this heading borrows the term for the charity tier. Contextually unambiguous, but if the register is scanned for vocabulary drift, rename to ## Three ways the same idea works.

3. COUNTS

Word bands

Two counts given: printed words (markers stripped, headings kept — the number that matters) and raw file words.

Only actionable band note: Ch2 is 77 printed words under the floor. Ch16’s 38-word overage and Ch9/Ch15’s 1–2 words are inside any reasonable tolerance. App B sits 14 words above its floor — it will fall below if anything is cut from it.

Coinings

Claim markers

235 → 244 after nine insertions. All 244 well-formed (class: taught|wire|relationship|boundary|vision | door: 1|2|3); zero malformed, zero missing a class, zero missing a door.

By class: taught 96 · wire 95 · boundary 26 · vision 23 · relationship 4. By door: door 1 — 209 · door 2 — 8 · door 3 — 27. By file: App B 15 · Ch1 9 · Ch2 15 · Ch3 10 · Ch4 18 · Ch5 14 · Ch6 12 · Ch7 11 · Ch8 10 · Ch9 14 · Ch10 10 · Ch11 11 · Ch12 16 · Ch13 18 · Ch14 13 · Ch15 11 · Ch16 11 · Ch17 22 · How-to-Use 4 · Frontmatter 0.

SCHOOL markers: 25 (U-track 21, tech-forward track 4 — Ch2, Ch4, Ch9, Ch12). SOURCE markers: 0, and no statistic is printed anywhere — correct.

Note, not a defect: 95 wire markers against 96 taught is a heavier reliance on the phone-to-task wire than the proposal’s inventory implies. Prose is correct everywhere (the mechanism is described, never its status), so this is a register-generation question, not a truth question. Worth a claims-register review before deploy.

Ration and banned words

• genuinely — one per chapter everywhere after fix #19 (was 2 in Ch6). ✓
• dramatically — 0. transformative — 0. ✓
• worth naming / it's worth — exactly 1 in each of Ch2, Ch3, Ch4, Ch5, Ch7, Ch8, Ch10, Ch11, Ch12, Ch14, Ch15; 0 elsewhere. ✓
• Banned phrases (in conclusion, it’s important to note, let’s dive in, fast-paced world, game-changer, revolutionize, unleash, seamless, supercharge) — 0 across all 20 files. ✓

Seams — all 19 connect by name and by content

One seam overstates: Ch7 L82 says of Ch8’s errands None of that lives on a page you can show, and Ch8’s own “The booking page, when there is one” section immediately shows Marguerite teaching the garage’s booking page. Ch8 addresses the tension head-on at L54, so it reads as correction rather than contradiction — but Ch7 could soften to Most of that doesn't live on a page you can show.

Cast consistency (post-fix)

Register / law compliance

• Status blocks outside Ch17 — none. The whole-book grep for today / being built, in development, as I write this, as this is written, currently being, not yet built now returns hits only in Ch17 L126–146 (where the law puts them) plus two permitted places: How to Use L44, which is the meta-paragraph explaining that Ch17 alone carries the ledger, and Ch15 L14, which is the honest-line-once the Ch15 card explicitly mandates. Ch16 L156 was the one true violation; fixed (#18). ✓
• Vendor / product / platform names — a word-bounded sweep for Instacart, Kroger, Amazon, Alexa, Siri, Twilio, Telnyx, QuickBooks, OpenTable, Bill.com, PropFlow, Phone AI Friend, DoorDash, Uber, Walmart, Safeway, Nest, Ring, Venmo, PayPal, Stripe, Xero, FreshBooks, Yelp, Zillow, Google, Apple, Microsoft, iPhone, Android, Chrome, Gmail, Excel, Facebook, Instagram, Twitter, LinkedIn, TikTok, Zoom, Slack, Claude, ChatGPT, OpenAI, Anthropic returns zero hits. The only matches were false positives on the substring “ring” (a three-ring binder, a coffee ring, an eleven-ring phone call, a bell nobody rings). EpiPen was the sole trademark in the book; removed (fix #6). Integrations are named generically throughout: the site you already pay your bills on, your pharmacy's website, the store she's used for six years, the parts supplier's site, the state's site, a company called him two winters ago and offered to "handle his socials". ✓
• Instantly Chef — Ch5 L55/L58/L60/L61, Ch16 L50/L53, Frontmatter L7 (companions line). Nowhere else. Ch17 L139 says At the sister company. ✓ (Ch5’s exclusivity claim fixed, #5.)
• The platform’s own name — never printed. How to Use L7 does exactly what the directive permits: The assistant this book is written for is the one on your phone. I'm not going to spend this page naming it. ✓
• The podcast — Ch1 L35 only, verbatim register: I also started a podcast by this book's name. I put out a teaser or two and then went back to building. It is not yet what it should be. Nothing more, nowhere else. ✓
• Narrator — one authority paragraph, Ch1 L35, carrying the anger, “making myself replaceable in order to grow,” 2022 and the programming books, the mechanic-shop design persona handed to Part IV unnamed, and the podcast line. Ch12 L7 completes it by naming Sal. I built appears zero times. No first-person claim beyond Stories 36–41; the App B confession (sounding unbelievable) is Story Bank L339 and now appears once (#20). The narrator never claims his own errands are automated — a sweep for first-person present-tense domestic claims returns nothing. ✓
• Consent spine — the drafts-and-presents / nothing-leaves-without-your-say / money-and-filings-on-the-one-tap pattern is stated or enacted in every chapter where something is sent, bought, filed, or paid: Ch4 (bill, filing), Ch5 (grocery order, substitution), Ch6 (one bottle), Ch8 (card mid-call), Ch9 (send-approval law + money-wearing-a-sentence), Ch10 (medical gate), Ch11 (fare, deposit, hold), Ch12 (payment run, deposit), Ch13 (sales-tax filing), Ch14 (post held), Ch15 (extended to the irreversible), Ch16 (the assisted order still tapped by Rosa), Ch17, App B. “PIN-gated” and “approved phone” said plainly; no internals described. ✓
• Education-not-advice — present wherever medicine, money, children, food, tax or legal is touched: Ch1 L50 (medicine) and L81 (money); Ch2 L76 (medicine); Ch4 L61 (money) and L127 (legal/tax); Ch5 L65 (nutrition/budget); Ch6 L79 (drinking); Ch9 L69 (money/paperwork), L96 (legal/tenancy), L109 (children); Ch10 L44 (medicine, the strongest statement in the book); Ch12 L83 (accounting); Ch13 L90 (tax); Ch16 L107 (the fund-holding paragraph — legal, tax, financial); Ch17 L25 (the consolidated line); App B L95 (financial/tax); Frontmatter L7 (the full fold). Ch11 is the only money chapter with no explicit line — it has None of this is financial advice, and it was never going to try to be at L60, which does the job. ✓
• “I couldn’t possibly” honored, never mocked — the villain is named at Ch1 L13 and answered across three paragraphs (L17–L23) as arithmetic, not fear: She was not bad with technology. She was correctly refusing a bad deal. The cost of learning kept coming due and the benefit kept expiring. Ch12 L124 repeats the honor for Sal in the register of his own trade: not stubbornness, not fear of technology, not any of the things people assume about a man who says I couldn't possibly. Arithmetic. It never penciled. Ch17 L114 and L124 close it the same way. Zero instances of the villain being laughed at anywhere in the book. ✓

4. THE THREE READERS

Marguerite — the person. Yes, written to her.

The book’s foundation is laid for her and it holds. Ch1 does not ask her to be braver; it tells her she was right — The machine sat still and demanded that she change… She was correctly refusing a bad deal. The just download the app paragraph (Ch1 L21) is the single most effective passage in the book for this reader, because it names the fourteen unnamed steps she has never been able to name out loud. Ch4 refuses to blame her for the pile: The nine dollars was not going to be a punishment for her judgment. It was going to be a fee levied on the fact that the information was inside a sealed envelope. Ch10 L70 refuses to nag her, and says so. Ch1 L94 and L96 close her case exactly right: She is not confused about her life… That is not a technology she has to learn. That is an employee she has to show.

Two places she would notice, both listed in §6.

Rosa — the household. Yes, and Ch16 is the book’s best chapter for her.

She is never once described as disorganized. Ch3 L45: Rosa isn't the one forgetting anything. The forms are the ones forgetting. Ch5 L99 refuses the cheap claim (None of this makes Rosa's food cheaper). Ch16 L9 states the thing nobody says to her: she has never once been allowed to get it wrong. Ch16 L119 earns the whole book’s trust by refusing the sentimental version: There is a version of this scene where Rosa cries, and I'm not going to write that one, because that isn't what happens to people who are good at this. And L131 — giving one back is not generosity, it's bookkeeping — is the line she would repeat to someone else. Ch17 L52 lands the distinction she has never had words for: She stopped being the household's *clerk*. The knowing stayed. The typing went.

Her only friction was the cast wobble in her own children (fixed).

Sal — the shop. Yes, and Ch12 is written across his counter.

Ch12 L23 removes the ask before he can refuse it: none of what follows requires him to replace a single piece of it. L27 flatters him accurately — he has been doing this book's work by hand for fifty years already — and L31 puts him on the right side of the method: It is the shop's native language. L124 is the paragraph that would make him keep reading: his 1998 program is not a character flaw, it is arithmetic that never penciled. L138–140 give him back the whole business — None of that is in this book. None of it is in any book — and L142 names the actual prize in his own terms: not being sixty-eight years old and doing paperwork at nine at night at the kitchen table. Ch15 L121 knows what he’d hand off (the sweep, the lot, the drums) and what he’d fight you about (brake jobs).

Ch12 L114 and Ch17 L102 both say Sal will never walk through it about door two. Twice is the limit; a third would start to read as writing him off rather than protecting his afternoon.

5. CH17’S LAST FOUR PARAGRAPHS — AN EDITOR’S JUDGMENT

The four:

L145 So: we are on the frontier of this technology today. This book will date, and some of these paragraphs will read as quaint inside of two years, and that is the point rather than the risk — this is the reality of what is being built now, written down while it is still true, by someone standing in the middle of it rather than describing it from a distance afterward. This is the reality as we enter the age of automation.

L148 You do not have to wait for any of it. The counter, the week, the shop — every one of those Tuesdays is made of things you can teach on a Saturday afternoon with a website you already have an account on.

L150 Go find your eleven minutes. Do them one last time.

L152 Marguerite uses her phone for three things now. That’s the age of automation.

Does it land? Three-quarters of the way, and the last quarter is fixable in two cuts.

What works, and it is most of it. L145 is the owner’s ruling in the owner’s shape, and written down while it is still true earns the dating rather than apologizing for it. L150 is a genuine mic-drop — Go find your eleven minutes. Do them one last time. takes the number the book has carried since Ch1 L47 (eleven minutes and a magnifying glass) and turns it, in five words, into an instruction with a joke and a promise folded inside it. And the final image is the correct one: not a robot, not a ledger, a seventy-three-year-old woman and a phone. Closing a book called The Age of Automation on the smallest possible object is the right instinct and it is the instinct the whole book has earned.

Three things stop it landing.

(a) The punchline is spent 119 lines earlier. Ch17 L33 already says: She uses her phone for calls, a card game, and a conversation with something that already knows her. That is the three, enumerated, in the same chapter. By L152 the reader is not completing an arithmetic the book set up in Ch1 (She uses it for two things) — they are being told a fact they were handed twenty minutes ago. The drop needs the count to arrive only once, and at the end.

(b) That's the age of automation. announces what the sentence before it just did. The directive is explicit: earn it, don’t announce it. Naming the title as a gloss on the image is the announcement. Marguerite uses her phone for three things now. is complete. The book’s own title supplies the second half; the reader gets to make the connection, which is the only version where it lands.

(c) Four beats after the frontier statement is one too many, and two of them do the same job. L148 and L150 are both the invitation, and the invitation was already made in full at L112–L122 (Here is the whole ask. Pick one errand…). L148 restates it a third time in flatter language than L150 does, so the paragraph that should accelerate into the close instead idles. There is a secondary cost: with three invitation paragraphs after it, L145’s where we are now reads as a mid-section rather than as the last lines, which is what the owner’s ruling makes it.

Proposed fix — three edits, none of them mine to make:

1. Ch17 L33 — remove the enumeration so the count survives to the end. Change She uses her phone for calls, a card game, and a conversation with something that already knows her. → She uses her phone the way she always used it, and for one thing more.
2. Ch17 L148 — cut the paragraph entirely. L150 carries it better and shorter.
3. Ch17 L152 — cut the second sentence. End the book on Marguerite uses her phone for three things now.

That leaves:

So: we are on the frontier of this technology today. […] This is the reality as we enter the age of automation.

Go find your eleven minutes. Do them one last time.

Marguerite uses her phone for three things now.

Three beats: the frontier, the instruction, the image. The frontier statement is unambiguously the last lines about where we are; the instruction is the ask, at its shortest; and the final sentence does nothing but count to three, which the reader completes from a number they were given on page one and have been carrying for eighty thousand words. That lands.

6. EVERY SENTENCE THAT WOULD MAKE A TECHNOLOGY-AVERSE READER FEEL TALKED DOWN TO

Nine, in severity order. The book is remarkably clean on this — it is, structurally, a book about not doing this, and it mostly succeeds. All nine are one-line fixes.

1. Ch10 L19 — the worst one, and it is aimed straight at Marguerite. > Partly it was smaller than that: she wasn't sure, the first time, whether teaching one task used up some kind of allowance, whether there was a limit on how many things a person was supposed to hand off before it started to feel like giving something up rather than getting something back. There isn't a limit. Nobody rations this.

This invents a mildly foolish belief for a woman the book has spent nine chapters establishing as a sharp retired bookkeeper — that automations might come with a quota — and then corrects it for her. It is the one place the book patronizes its own protagonist. Suggested: Partly it was smaller than that: the first one had cost her a certain amount of nerve, and she had not yet found out that the second one wouldn't. It doesn't. The fifth taught task costs exactly as little as the first one cost a lot.

2. Ch1 L71 · Ch2 L31 · Ch17 L124 — If you can leave a voicemail, you can run this. used three times. Reassuring once. By the third it is benchmarking the reader’s competence at the lowest bar available, and to a person who kept books for thirty-one years that reads as a pat on the head. Suggested: keep it in Ch1 L71 where it does real work; in Ch2 L31 cut the sentence (the paragraph closes fine on That's the whole interface); in Ch17 L124 keep only the second half, which is the better line and the respectful one — If you can show a new employee how you like the invoices filed, you have already done the hardest part of it, in a previous decade, for a person.

3. Ch1 L23 — If you have said the same sentence, or heard it come out of your mother, For one clause the book stops addressing the averse reader and starts addressing her daughter, making her a third party in a chapter written about her. Suggested: If you have said that sentence yourself, or watched someone you love say it, — which keeps both readers and demotes neither.

4. Ch2 L25 · App B L117 — no record kept against you for needing one. Said twice, in near-identical words. Each instance reassures the reader that she will not be punished, which presumes she was afraid of being punished — and repetition converts reassurance into condescension. Suggested: keep Ch2’s; in App B L117 cut and no record kept against you for it and let the sentence end at There's no penalty for needing a second pass.

5. Ch2 L58 — Nobody grades you on which door you use, and nobody checks which one you picked. The schoolroom frame (grades, checks) is the wrong metaphor for a seventy-three-year-old who has never been a student in this. Suggested: Nobody is keeping score on which door you use, and there is no wrong one.

6. Ch3 L11 — Sit with it a little longer than that. A gentle instruction to think harder, delivered to a reader whose whole complaint is being told she hasn’t understood something. Suggested: It's worth a second look, and here's why.

7. Ch2 L3 — if you have ever run so much as a lemonade stand with somebody else's help. so much as sets a floor and lets the reader feel measured against it. Suggested: cut the clause; Picture the best new hire you ever had. is stronger without it, and the sentences that follow already build the ramp.

8. Ch5 L15 — something almost embarrassingly simple: she talks about it instead of writing it down. The embarrassment belongs to nobody in the room, and a reader can hear it as you should have thought of this. Suggested: something almost too simple to write down: she talks about it instead of writing it down.

9. App B L55 — If you can't say it in one sentence, it's probably two errands stitched together, and you should pick the smaller half. you should is the only bare imperative-with-correction in an appendix that otherwise scrupulously suggests. Suggested: If it takes more than one sentence, it's probably two errands stitched together — pick the smaller half and come back for the other one.

Worth recording on the other side of the ledger, because it is why the count is only nine: the book repeatedly catches this failure mode and names it. Ch1 L19 (She was not bad with technology), Ch1 L21 (the anatomy of just), Ch4 L107 (it has almost nothing to do with whether they are good at managing their affairs), Ch7 L55 (the boundary said as a gain, not a gap), Ch10 L70 (It doesn't ask her to confirm she's still coming… in a way that quietly implies she might forget. It doesn't nag.), Ch12 L124 (Arithmetic. It never penciled.), Ch14 L52 (undersells itself on purpose), Ch16 L119 (refuses to make Rosa cry), App B L27 (which was never true and never the real diagnosis). That is a book that knows what it is trying not to do.

7. VERDICT

PASS WITH FIXES APPLIED. Twenty mechanical corrections and nine claim markers are in the draft. The three coinings now stand verbatim once each in their owning chapters with only permitted callbacks; all nineteen seams connect by name and content; the cast is internally consistent; no status block survives outside Ch17’s last lines and the two places the law permits; no vendor, product or platform name appears anywhere; the podcast appears once, in register; the narrator claims nothing beyond Stories 36–41 and never his own errands; education-not-advice is present wherever it is owed; the villain is honored in three separate chapters and mocked in none; ration and banned-word law is clean; word bands are met with one 77-word shortfall in Ch2.

Blocking before deploy: nothing.

Owner decisions outstanding, in priority order: 1. F-1 — Ch4’s date arithmetic. The book’s flagship story does not currently close; two repairs offered, Option B preserves the better sentence. 2. §5 — Ch17’s ending. Three cuts proposed; the ending is the owner’s, and the verifier has not touched it. 3. F-3 — one-clause door 2/3 pointers for Ch3, Ch7, Ch8, Ch10, Ch11, Ch13, Ch14, Ch15, Ch16. Ch7 is the one that matters most. 4. §6 — the nine talked-down-to sentences, all one-line fixes, item 1 (Ch10 L19) being the only one a reader would actually feel. 5. F-6 — whether barely kept up with the turn of the century may stand three times or must be cut to one. 6. Ch2 is 77 printed words under the band floor. 7. The claims register should be reviewed before deploy: 95 wire markers against 96 taught leans harder on the phone-to-task wire than the reality inventory implies. Prose is correct throughout; the classification is the question.

The vision, verbatim (Turn 9)

Turn 9 — 2026-09-03 (dictated; transcription errors preserved)

I was just thinking about phone ai friend, the consumer product face powered by the automater that is built to be your personal assistant you can teach to do anything. The ability to perform trained tasks, and to learn workflows is pretty powerful. There is a lot to be said about automating everything, the vision of it all from a personal perspective is Pretty powerful. If you think about IoT and all of the things in your home that can be automated, anything that can be accessed from the browser can be automated. Anything with an API can be automated. Your appliances, um, which means you would be able to use your telephone to be able to turn on your coffee machine or open your garage door or lights. I know that you can already do this with Amazon’s Siri if you configure it, but it’s a more cumbersome task to do that. Um, and you’re stuck to only what that Siri AI is able to do. The phony iPhone is able to apply the ability to automate your life to a much broader scale. Um, you can teach it to refill your medicines prescriptions as they come to. Uh, it can help you discuss through your bills that have come in and line up all of your payments that you can authorize it to execute payment for as you get male, that typically would have to be processed with checks sent out by male. You could now take advantage of a bill dot com automation and have the AI submit the payments through the platform. And you might say, oh, well, how am I going to get this paper into the system? And it’s now so simple because you can just take an image with your phone picture. and text it to your phone AI friend or have your phone AI friend send you a link for your invoice deposits. And click on that link and scan all the documents that came into the mail that it will help you go through and pay. The ability for the phone and your friend. to be a true assistant is incredible. Well, it won’t be able to drive your laundry to be done at the laundromat. you could ask it to contact the laundromat to have them come by and pick it up. or go on their website instead of that appointment. by showing it once. for grocery shopping, You can discuss what you wanna eat for the week and how much you wanna spend for the week and get your grocery list planned, and it can help you place the order with the grocery store for you to have that food ready to pick up. later that day or at the time that you choose. from your local grocery store. We even have a sister company launching soon called the Infidently Chef, which is completely designed for meal kit style planning that’s run from a local grocery store. Instantly chef is another product to open another. I think you should try to mount that folder because there is a folder for Instantly Chef that you should have access to in the p h seven zero three root folder where all of the other folders mounted. and see everything that can be done there. You can take a picture of your pantry, and it will keep an inventory of what you have and create a whole purchase that utilizes ingredients you already have and buys ingredients for dishes that you don’t. And then it has one hundred percent utilization where if you might use a half package of carrots it will know how much is left over from the rest of the piece that are created and create side dishes special for you. All of them chef curated. As a chef, this was something that was a project true to me. But then I realized we could also do a charity tier of this product and, uh, budget, um, controlled families could use the same application to feed my family a four for a hundred dollars on the week, which sounds insane, but with meal planning and thoughtful planning in in consideration. the menus can be different and creative and can be applied to stretch over that period of time. And then there’s ways we set up in that platform where you can donate to feed a family of four for a week or boost people’s spending accounts or in in the community a pool of… essentially being the eighth. a food pantry, and people can go to their local grocery store, though, and it’s… you know? community funded platform. Is that something that is completely complementary to this whole system? And just another… like, the thousands of things that a personal assistant can do for you as they learn and are trained on what it is you you do, you need, um, answering your emails is stuff that personal assistant might help you with or sending a text message or a new mail. These are personal things, and you may not ever want to release having your words be applied to the loved ones in your life, but you could tell your assistant while you’re driving or while or while you’re even used driving in the book. But while you’re cooking dinner and talking to it or going for a walk in your neighborhood or whatever. And you can talk to it and tell it what you want, and it can help co draft what you’re trying to say and work through thoughtful ways or writing a funny haiku or coming up with a joke, uh, that plays on words or all the fun things that, you know, AI as a toy can do but applied functionally to your life where you you don’t have to write that email anymore. Um, even, uh, phone platforms, um, were in the process of figuring out trying to set up relationships with telecom companies. So you can automate your text messaging. This is already possible with some platforms. that we already use with our business assistant tiers. and some carriers have had interfaces. that the phoney of a friend is able to interact with for sending text messages. As your Assistant. Don’t start making up bullshit, but get into that idea, and how it can apply. This is a software that is completely integrative with the physical realm and will transcend a telephone call or going to your website accounts and talking to your chat agent that can perform whatever you need them to for opening up your app and talking to your your agent or your, I say, agent, your your your phone AI friend or your app AI friend or whatever AI friend the platform is providing you in that form of everybody has a phone. But that’s where idea came from. And when you think about an interface, like, people who are resistant to complex technology, the… oh, I couldn’t possibly use that technology mindset type of people. They all use a phone. And when a phone becomes the interface, it can do all of the things now for you. It can walk you through. Even ChatGPT now has commercials of Octogenere hands sitting around talking on telephones because they can help them answer questions, come up with plans, playing trips. There’s so many things that that they can already do, but this gets expanded exponentially. And phony eye friend would be able to also help you figure out your trip, but it would be able to help you figure out your trip from here to, like, you travel the whole world. You can connect all the different flights from one after the other after the other after the other, playing your whole itinerary, have it all tracked and documented. And, you know, literally plan to see the entire world, but you can do it with your… I think tracking the whole conversation instead of a GPT that, you know, you have to manage auto meeting one task at a time with all that extra follow-up and and management. This puts it all into one place, and it puts it into one brain. and it has your information, so you don’t have to keep going back and and adding your information every time. It’s a… That’s the reason that we… that I started the age of automation podcast. I’m checking command to… actively have doing any shape and have be more active. It’s not not over. I don’t wanna overpromise on that podcast because… it was very lightly touched on, but I did create it and put out a teaser or two. I can’t even remember how many it did. But Yeah. The goal here is to get you thinking about that. And and I know that you mentioned and show it once. Not a mention, but I mean, like, a whole dedicated conversation about this frontier. Robotics are selling Androids now. It can go into your house and be your personal assistant in a way. which is great, but they’re on the frontier of just not getting home ready robotic Androids that are affordable enough that you can buy them like a car. And just like you can teach an AI how to log your invoices in the QuickBooks, you can also train a physical robotics AI in the same way. This technology can be applied to teaching a robot how to do drywall repair. Something that’s and really a physical world skill set that is not intended or expected to be done by AI anytime of century. this ability to show it once and it learned, and then once it understands that process to be able to train on it and get better at it over time becomes a cornerstone, a linchpin, and robotics technology being able to provide this are also being able to cook you bacon and eggs in the morning. So I wanna impart this into show at once because it’s such a cool product. They instantly cart. I just need to… the depth of that. I mean, I didn’t even tell you, like, about the liquor cabinet, and it can, you know, create your cocktails. Um, you teach a robot how to do those types of things. A robot’s gonna get a completely separate idea, and I mean, this is this own little end of the road because now you take physical world conceptually of where this is going. So we have all these things you can do all things we canceled out, and I had where we’re going. And you… you’re you’re robotic for be able to see and understand what you have in inventory and plan your cocktail to be made for you when you get home. Um, and if you don’t have ingredients that that you’ve expressed that you’re interested in cleaning a colada or whatever, it can, um, get that together for you, draw a themed coconut tree on the whiteboard or in the refrigerator, and You walked in the door. You have frozen margarita and and your robot’s washing your your Vitamix. It sounds crazy, but it’s not anymore. Like, these are these are the real things you’d be able to teach and as as these machines learn from you, they become able to do those things. So… learning. and becoming capable of what this book is all about and show it once. It literally conveys that entire thing and the automation platform and software that even building supports that in its entire underlying design. I was thinking phone Ai friend could get its own book also, consumer and small business applications. Get deeper into social media, is deeper into personal accounting, ability to… not just scanning your invoices, like QuickBooks, but, you know, you scan in all your mail. That way, babe. coupons you wanna use, you know, or sitting there for your Instacart agent to clip and post with your, uh, order to the grocery store if the grocery store accepts those coupons. through online ordering. filling up your car appointment to go get your inspection doing… calling and setting up a reservation or going online and filling up a reservation. If they don’t have a reservation online, having it call the restaurant for you and find out if they have availability or if they’re busy right now to go to see the party of six. Really, if you can think anything of of a person or a sister could do for you. kind of… anyways, I just wanna keep this out of my brain and over to you so that we can enhance show at once. And I wanted to talk to you about building out this additional book, which, um, what’s the power of automation for your entire life into into your… into the user’s mindset, which is a shift, but it’s a progression. Um, so I thought that it might deserve its own book. I wanna see what you think And, um, this is where things get really exciting. because I think we can both enhance what you already have. Conceptually, we can take this idea and enhance it for the for the stuff we’ve already lived to to get that table instantly chef, yeah. So that’s a cool one. But… What do you think?