Claims Register — every capability, one row each, with your column

Every automation the three books say we have, in one list. Compiled 2026-09-03.

Sources: REGISTER-book1.md, REGISTER-book2.md, REGISTER-book3.md (Table 1 claim rows, Table 2 deduplicated capability lists, the BUILT cross-checks against REAL-STORY-BANK.md, and Book 2’s membership/school obligations table) · BUILT-FIXLOG-books12.md · the eight RETHEME-LOG-*.md files in /home/claude/work/book3/v2/verify/ · and a live grep of the 295 <!--CLAIM: … | class: …--> markers now sitting in /home/claude/work/book3/v2/draft/.

What this is, and how it got built

This is the list you asked for. You said you weren’t sure anybody was keeping track of all the automations we’ve basically promised or claimed we have — the ones that need to be there for members if people are paying for membership — so we don’t end up the villain in our own story. This is that track. Three people read all three books line by line, adversarially, and pulled out every sentence that says or implies a machine does something: “I built,” “the platform does,” “it checks and flags and routes,” “available to any reader through membership,” “the school keeps that current.” That came to 1,081 individual claim sentences. Those were then collapsed to one row per actual capability, across all three books at once, so the same thing promised in three places shows up here once. The result is the checklist below: 272 distinct capabilities, sorted so the ones with the most exposure sit at the top. The last column is blank on purpose. It’s yours. Y, N, or partly — that’s the only thing this document is missing, and it’s the only thing that turns it from an inventory into a plan.

Every claim is sorted into one of four classes, and the class is what tells you how much trouble a row is. MEMBERSHIP or SCHOOL means we told a reader they can have it, or that the school carries it and keeps it current — that’s homework owed the day somebody pays. BUILT means the narrator says in the first person that he built it and it runs. POSSESSION or PLATFORM means the book says the product already does it — no “I,” but a reader will hear no difference. TAUGHT / MECHANISM means the book explains how the reader teaches it and what it then does; and ROADMAP means the book says out loud that this one isn’t there yet. The hard rule underneath all of it, and the one that governs every future draft: “I built” is reserved for what the story bank holds as real. That is the property management machine on his own doors, the term-sheet automation, the offer worksheet, and the platform in general. Everything else got moved — into what the reader teaches, into what somebody else built, or into what a machine does once taught. The right-hand “story-bank status” column carries that verdict per row: REAL means the bank holds it, not held means we said it and the bank does not back it, n/a means it was never a first-person claim in the first place and the bank has nothing to say.

1 · THE CHECKLIST

One row per capability, deduplicated across all three books. Sorted by exposure: membership/school promises and built claims first, then possession claims still standing in Books 1–2 and platform claims in Book 3, then the taught/mechanism layer, then the roadmap items the books already fence honestly. Chapter columns name where each book carries the capability or its nearest equivalent — a row can cite chapters in more than one book, and often does.

2 · MEMBERSHIP AND SCHOOL OBLIGATIONS

Every promise of availability to a member or reader, and every “the school carries this / keeps this current,” with the sentence that makes the promise. This is the day-one list. If somebody pays for membership on the strength of these books, these are the things they will go looking for.

2a — Membership: what a paying member is told they get

2b — School: what the school is said to carry and keep current

Membership/school obligations: 64. Twenty-two of them (rows 22–33, 47–52) carry the sharpest exposure, because the sentence promises availability today and the story bank does not hold it — most acutely the term-sheet automation promised free to every reader while the V9 ruling records that funnel as not live, and the Property Management Machine promised as a hosted member service when the bank holds it only for his own doors.

3 · COUNTS

Distinct capabilities

By class (merged checklist)

By book (rows citing at least one chapter in that book)

(These exceed each book’s own capability count because a merged row names the nearest equivalent chapter in every book that carries it.)

Story-bank status

The remaining exposure: possession/built claims still standing

Book 3’s 295 claim markers now read: taught 217 · platform 65 · built 6 · roadmap 7. Across 179 distinct marker names that is 129 taught-only · 27 platform-only · 9 both · 7 built · 7 roadmap. The seven built-class names are the property management machine for his own doors (Ch1, Ch16), its four PM sub-builds in Appendix A-20, the watching-and-learning platform in general (Ch1, Ch2), and a friend’s expired-listing automation, explicitly attributed to the friend.

Stated the way you’d want it stated: across three books we claim 272 distinct capabilities exist. 49 of them the story bank actually holds. 64 are promises of availability to a paying member or of something the school carries and keeps current. 93 still stand in Books 1–2 as things the product simply does. Book 3 no longer stands on that ground at all — after the re-theme, it claims one property management machine on his own doors, one platform, and one friend’s build, and everything else it says the reader teaches.

4 · WHAT THE BOOKS NO LONGER CLAIM

Book 3, the re-theme (eight logs, 2026-09-03). Book 3 used to open on a promise: “a practice that comes pre-built — the machinery standing up before the book of business does,” and “this book hands it to you already built.” That promise is gone. Every “pre-built,” “already knows,” “already running,” “already built” and “already set up” that described the product was converted to the taught register: the book now teaches the practice and then teaches how each part of it gets taught to a platform that watches how you work and learns it the way a new employee would. All 97 rows of the hunt list were worked, including three sentences that carried the same promise without any of the trigger vocabulary (“All of it is sitting there, unopened, the moment you are” is now “Teach it as you go, and by the time you need it, it will be ready”). First-person “I built” was cut back to a reserved set: the property management machine on his own doors, the term-sheet automation, the offer worksheet, and the platform in general. That removed the three overbroad umbrella claims (“I built the machine,” “This book is what I built,” “What I built instead is the chart’s other half”), both first-person claims over the Ch13 guardianship flags, and the Ch22 first-person budget-queue operation. The Ch16 property management section keeps its “I built” verbatim, because Story 5 holds it — with a new transition sentence marking where the narrator’s own build ends and the reader’s taught version begins; the rent, deposit, disbursement, year-end and trust-account block that sits outside Story 5 was re-registered as taught. The six roadmap items (the anniversary check, the week’s call list, live-call patch-through, the after-call summary, the time-value view, the avatar channels) kept their honest not-built labels, and 295 <!--CLAIM: … | class: taught|platform|built|roadmap--> markers were laid into the draft so this register can be re-derived from the text at any time instead of re-read by hand.

Books 1 and 2, the BUILT fix pass (BUILT-FIXLOG-books12.md). Eleven files were edited against one rule — the narrator may not say “I built” anything a member cannot touch, and the story bank is the only source of what is real — keeping the mechanism and the lesson in every case and removing only the first-person possession. In Book 1: the absolute audit-record guarantee (“nothing that happens is ever invisible”) became a design instruction to the reader; the expired-listing machine became a friend’s build (“his list, his machine, not mine”); the configured rate-standard auto-dispatch and the summary-digest artifact came out of Ch12; the repair-quote ceiling and the contractor-first in-window check-in came down from “running in my business” to teachable and to design; Ch15’s construction line was narrowed back to what Story 27 and Story 29 hold, with the trained human eye restored to where the bank puts it; and Ch15’s community library stopped naming four guaranteed installable builds and became “a growing collection rather than a finished catalogue.” In Book 2: the three sentences claiming lead capture, evaluation, follow-up and “every piece of it” were built converted to “can be taught”; the Ch7 offer-worksheet teardown moved from first-person discovery to a teardown the reader can run, with the backmatter’s constructed-example fence extended to cover the forensic specifics; the Ch19 quarterly authority review became the reader’s review rather than the narrator’s ritual; and Ch20’s “I built… the school behind it” became “I’m putting the work into the school behind it.” Two things were deliberately left standing and are still open: the “six figures in 0% APR capital” figure in Book 2 Ch12, on your instruction, and the whole membership/school availability layer in both books — which is exactly what Section 2 of this document is for.

Blank column, last on the right of the checklist: Owner — exists today? Y / N / partly. Nothing else in this file needs your hand. That one does.

Book One — every claim, classed

Built from: /home/claude/work/register/books/book1-v5/ — B1v5-00 through B1v5-16 (all 17 files, appendix included) Method: every sentence asserting that an automation, feature, machine capability, tool, data feed, integration, dashboard, or membership benefit exists, runs, was built, or is available. Read adversarially — a claim counts even when it is wrapped in a hypothetical, a glossary definition, a walkthrough step, or a production comment, because a member who reads it will expect to touch it. Scope note: in-text <!--BUILD-APPENDIX--> production comments are included and labelled (build note) — they are in the delivered files and each one promises a specific build in a reader-facing appendix. Sourcing/verification comments (<!--SOURCE-->, <!--QUOTE SOURCE-->) are excluded; they make no capability claim. Claims about the third-party coaching program and the crashed voice-AI license in Ch 2/9 are excluded — they are claims that someone else’s product failed, not claims that we have something.

TABLE 1 — EVERY CLAIM

Chapter 1 (B1v5-01) carries zero capability claims. It is entirely narrative — the food-truck and BRRRR ceiling story. Its only technology sentences are negative (“the tools… simply didn’t exist yet”), which assert the absence of a capability, not its existence. Chapter 2 (B1v5-02) carries only the three “worker with hands” premise rows (#6–#8); everything else in it is a claim that a third party’s product failed, which is out of scope.

TABLE 2 — DEDUPLICATED CAPABILITY LIST

Strongest class ranked: BUILT > POSSESSION > MECHANISM > TEACHABLE > MEMBERSHIP/SCHOOL > ROADMAP.

Distinct capabilities: 89.

CROSS-CHECK — BUILT CLAIMS vs. REAL-STORY-BANK.md

Every BUILT row (first person “I built / we built / I have,” or “runs in my business”) checked against the bank.

Held as REAL by the bank

FLAGGED — BUILT claims the bank does not hold as REAL

1. Expired-listing offer machine, claimed in the first person (row 123, Ch 10): “I lived the paradox on one kind of list and built the answer on another.” The bank’s Story 16 is a Lane 1.5 story — a real friend’s machine, de-identified, built collaboratively (“They ran the scrape”). Ch 5 and Ch 10 elsewhere handle it correctly as a second-person hypothetical (“Picture building a machine…”, rows 42–45, 124–125). Row 123 is the one sentence that converts a de-identified friend’s build into the narrator’s own. Recommend rewording to “the answer got built on another” or an explicit “with a friend.”
2. “The offer worksheet tool” — no bank entry exists. There is no worksheet tool anywhere in REAL-STORY-BANK.md (zero hits for “worksheet”). Book 1’s nearest claims are rows 50 and 226 — the appendix/school “worksheet for writing out a task’s implicit rule, plus the full show-it-once test checklist” (Module P04). These are classed MEMBERSHIP/SCHOOL, not BUILT, so nothing in Book 1 overclaims it as an existing product — but the promised worksheet has no source artifact in the bank and must actually be produced before the appendix ships.
3. DSCR sweep — scope drift risk (rows 137, 139). The bank (Story 8) supports “runs across all DSCR products, comparing rates across far more of the industry.” Row 137’s “every DSCR lender I had a relationship with” is supported; row 139’s “the DSCR products I trust it with” is appropriately hedged. No overclaim, but note the standing bank caveat (V9 ruling): Century Key Capital’s automations are unfinished and the funnel is not live, so any reader who follows this claim to a product may find nothing there yet.
4. Story 19 (“the cracks”) — the incident is real; the fix is not asserted as built. Story 19b supports the no-call-no-show scene verbatim, and Ch 7 tells it truthfully. But the bank’s fix is a post-visit follow-up (“Just making sure so-and-so made it out…”); Book 1 upgrades it to a contractor-first, in-window check-in with a tenant fallback and an auto-opened shared thread (rows 78–82, 180, 181). Ch 7 states it as MECHANISM (“the fix is…”) but Ch 13 states it as POSSESSION — “a message goes out on its own to the contractor first” — describing his live PM Routine. The bank does not document the contractor-first in-window variant or the shared-thread feature as built. Recommend either bank confirmation or softening Ch 13 to the design register used in Ch 7.
5. Audit record / “nothing that happens is ever invisible” (rows 21, 68, 73). The showing log is supported by Story 21 by implication; a general platform-wide immutable audit record is not documented anywhere in the bank. It is asserted as an absolute in Ch 6 (“not on this rung or any other”). Flag as an unsourced absolute.
6. Post-run reporting / summaries (row 153). “I found out about most of it after it was already resolved, in a summary.” No bank entry describes a summary/digest artifact. Plausible from Story 5b but not documented. Flag as unsourced.
7. Repair-quote ceiling (row 172) and auto-dispatch against a rate standard (row 152). The bank has vendor rates and the bench (Stories 26/28) and the approve-gate pattern (Story 31), but no entry documents a configured dollar ceiling running in his PM company, nor automatic dispatch without his approval. Both are stated in the first person. Flag as unsourced first-person specifics.
8. Ch 15’s three-company summary (rows 198–200). All three are supported in outline (Stories 5, 27/29, 31). The phrase “I built the construction side to… verify its own completed work” is the strongest of the three; Story 29 documents a trained person doing the calling-out with the automation described as the gate to build. Supported but at the outer edge of the bank; keep the “systems watch for what needs a person” framing rather than implying the construction company is fully autonomous.

Also worth flagging (not BUILT, but the strongest-claim risk in the book)

• The community build library (rows 204–206) is stated as existing and populated — “a growing collection of builds other people have already taught… already built, ready to be shown a second time.” The bank supports a library existing (Story 15: “The community library of automations exists now; many entries are AI skills”), but not the specific inventory named in Ch 15 (vendor approve-gate, follow-up sequence, verification check, whole chained morning). These four are named to the reader as installable and must exist on day one of membership.
• The school’s 11 named modules (P01, P05, P04, U4, P02, A3, U5, P03, P06, P07, P10) are promised by code. The appendix itself flags two as provisional (row 214). Every one is homework owed.
• Ch 15 promises two further books by title (Automating REI, Automating Real Estate Agency) as things a reader can go get.

COUNTS

By file: Intro 5 · Ch1 0 · Ch2 3 · Ch3 15 · Ch4 13 · Ch5 26 · Ch6 15 · Ch7 8 · Ch8 21 · Ch9 15 · Ch10 8 · Ch11 16 · Ch12 17 · Ch13 25 · Ch14 5 · Ch15 20 · Appendix 76.

Distinct capabilities: 89. By strongest class carried anywhere in the book: BUILT 26 (asserted as already running in the narrator’s own businesses) · POSSESSION 19 · MECHANISM 25 · TEACHABLE 3 · MEMBERSHIP 9 + SCHOOL 3 = 12 capabilities that exist only as promises — appendix walkthroughs, school modules and tracks, the community build library, membership access, and two unwritten companion books — ROADMAP 4 (explicitly not live, not final, or disclaimed).

The homework total, stated the way the owner asked for it: 89 distinct capabilities are claimed to exist somewhere in this book. 26 are claimed as already built and running. 12 are owed to a member the day they pay. 4 are honestly labelled as not there yet. The remaining 47 are described as things the platform simply does — POSSESSION, MECHANISM and TEACHABLE rows — which a paying member will read as no different from built.

Book Two — every claim, classed (membership promises flagged)

Built 2026-09-03 per REGISTER-BRIEF.md. Source: every file in /home/claude/work/register/books/book2/draft/ (front matter, how-to-use, CH01–CH20, APP-A, APP-F, backmatter). Read adversarially: every sentence asserting that an automation, feature, machine capability, tool, data feed, integration, dashboard, or membership benefit exists, runs, was built, or is available.

Claim classes: BUILT · POSSESSION · MECHANISM · TEACHABLE · ROADMAP · MEMBERSHIP · SCHOOL Promised to: reader · member · narrator (narrator’s own business)

TABLE 1 — EVERY CLAIM, IN READING ORDER

B2-FRONTMATTER.md

No capability claims. The file is a title, a subtitle, and an education-not-advice disclaimer. 0 rows.

B2-HOW-TO-USE-THIS-BOOK.md

B2-CH01-the-grind-gospel.md

B2-CH02-the-program-that-sold-automation.md

B2-CH03-first-with-full-sight.md

B2-CH04-the-machine-that-finds.md

B2-CH05-feeding-the-hunter.md

B2-CH06-the-first-walk-in.md

B2-CH07-the-blank-cell.md

Chapter is a forensic audit of a third party’s spreadsheet. Rows here are (a) the narrator’s own first-person audit act, and (b) claims asserted about that third-party product. No forward capability promises are made in this chapter.

B2-CH08-offers-are-outputs.md

B2-CH09-every-way-to-buy.md

B2-CH10-if-it-goes-badly.md