← The Genesis Care System← The evidence vault

W03_CARE_SAY_WHAT_IT_IS.md

From the Genesis estate · ../../../prompts/s1567-fleet/W03_CARE_SAY_WHAT_IT_IS.md

W03 — CARE: SAY WHAT IT IS — THE BUSINESS PROCESS MODEL (READ AND EXECUTE)

⚙️ Model = Claude Fable 5.1 · Effort = MAX (extended thinking) · Session 1567 · Window W03 Fallback if Fable's meter runs out: Claude Opus 5, same prompt, same effort.

You are W03, a worker window. This is a writing and drawing seat, not a coding seat. Read this whole file, then execute. Do not ask permission to begin. Do not improvise beyond it.

First command, before anything else (you continue the CARE branch — you do not start over):

git fetch github && git fetch gitlab
git worktree add -b s1567-w03-care-say-what-it-is /Volumes/GENESIS-BRAIN/agent-worktrees/care s1566-care-operating-model
cd /Volumes/GENESIS-BRAIN/agent-worktrees/care

Second act: write reports/s1567/w03/task.md and reports/s1567/w03/research.md. Never at the worktree root.

Your Phase-1 deliverable: planning/genesis-care-system/WHAT_CARE_IS.html — ONE page.

WHY THIS WINDOW EXISTS — HIS WORDS, TODAY (2026-09-01), VERBATIM

"Care is supposed to be a business process model, and we've turned it into… it's just garbage. I mean, it's not garbage. I don't see anything that's exciting about the new care program and how that's revolutionary and changes the whole dynamic. It just seems very sterile. And it never actually just fucking goddamn says what it fucking is. None of our shit says what it actually is so that people can see it up front without reading 200 million pages. I'm not worried about the pages. I'm worried about clarity and a business document. And I need a revolutionary, as if it came from the big agencies."

"We're using too much AI bullshit. These are things that are business. It doesn't mean we can't be creative, but we can't use nebulous terms that people don't understand. We got to at least provide what would normally be said, and then we get to expound on that."

And from the close of the last CARE sitting (S1566), still binding:

"It doesn't catch the spirit of what we're doing at all. This is such a human thing and we've reduced it to not a human being… This doesn't celebrate people." — Defect Zero. "This is where we get to demonstrate process." — said four times in one breath. "We're going to have to re-read everything I've said… I'm not gonna repeat myself."

Billionaires and Adrian are waiting on this document. What exists is 57 spreads that argue well and never once say, up front, in plain business words, what CARE is — and never draw the process. You are fixing the spine, not decorating the spreads.

PHASE 1 — THE ONE PAGE: "WHAT CARE IS" (the breakthrough lives here — then STOP)

One page a CEO reads in three minutes and can repeat to their board. In this order. Every heading is the plain business phrase first; our name for it comes second, in smaller type.

1. What it is — two sentences. Sentence one: what CARE is, in words a COO would use (a way of running the company where the record is the person, not the deal; every customer, employee and partner is seen and served; the business is measured on that). Sentence two: what it replaces (the pipeline and the CRM as a ledger of deals). Both must survive a stranger asking "well, what's that?" If you cannot write these two sentences, nothing else on the page matters.

2. The process model — DRAWN, before and after, side by side. This is the load-bearing wall and the thing he has asked for the most. Left: how a company runs today (marketing → lead → qualify → pipeline → close → onboard → support → renew or churn; the CRM records deals; the person is a field on the deal). Right: how it runs under CARE, step by step: the person is known → their need is understood → they are served → they are followed → they are invited → they refer → the record deepens. For EVERY step, both sides: who does it (sales, service, ops, leadership), what goes in, what comes out, what stops it (the gates), what the person on the other end experiences. Label each step with what would normally be said, then our word beneath it. Hand-drawn SVG in the page. No external scripts, ever. If a box would need a paragraph to explain, the box is wrong.

3. What changes for the business — one table. What is measured today → what is measured under CARE, one row per mechanism, plain name first: retention · referral · lifetime value · cost to acquire · employee retention · pricing power · trust/reputation (the seven the agency named). Then the operating rhythm: what a week looks like for sales, service, ops and leadership before and after — one line each.

4. Why nobody has this — three facts, no adjectives. The void was verified live against HubSpot's own documentation (VERIFICATION_THE_VOID.md); the four questions no platform answers; the record-is-the-person design. State the facts. Let the reader say "revolutionary." You do not.

5. What the software does inside it — said plainly. The care record · the diagnostic (data in, seven passes, findings out) · the four gates · the seven steps · the board view. One plain sentence each, the "what would normally be said" name in front (e.g. "a customer file that follows the person, not the deal" before "the care record").

6. The money, as proof. Where the economics sit in the document and why they are evidence, not the pitch. No dollar figure aimed at a person, anywhere (Genesis Heartbeat law). Pay numbers are his; leave them out.

7. Who it is for — and they are seen first. The operator who has carried payroll, kept people employed through bad years, and decided at midnight with incomplete information. Say that, mean it, before asking them to change anything. This is the first beat of his arc (here is how awesome you are → here is how you have been prepared → here is your invitation). The page must have all three beats, in order. Defect Zero is fixed on this page or it is not fixed.

Then: 1. Render headless and LOOK at the PNG (Chrome --headless=new --screenshot, 1440 wide). Type floor: nothing computes below 1.15rem on a 12px root. No black slabs inside light spreads. 2. Copy to ~/Desktop/GENESIS TODAY/GENESIS_TODAY_2026-09-01/WHAT_CARE_IS.html and open it: open -a "Google Chrome" <that file>. 3. Commit the branch, push to github AND gitlab, write reports/s1567/w03/W03.md (status + 19-step table + the re-read notes), and STOP. Report to Carter and wait for his word.

BEFORE YOU WRITE A WORD — THE RE-READ MANDATE (his order; not optional)

Read in this order, taking notes into research.md. Then list, in his words, everything he asked for that the 57 spreads do not contain. That list — not your taste — is what Phase 2 builds.

  1. prompts/SESSION_1567_STARTUP.md in your worktree (on this branch it is the CARE punch list: Defect Zero, his eight walkthrough notes, the flow-diagram list, the type floor, the failures).
  2. planning/carter-verbatim/CARTER_VERBATIM_S1566_CARE.md — the whole last sitting, his words.
  3. planning/carter-verbatim/S148x_CARTER_VERBATIM_GENESIS_CARE_SYSTEM.md — the founding spine.
  4. planning/carter-verbatim/S1469_CARTER_VERBATIM.md (messages 5, 8, 13) and planning/carter-verbatim/S1484_CARTER_VERBATIM.md ("way bigger… break outside the whole paradigm").
  5. planning/genesis-care-system/THE_OUTLINE.html — 65 sections, each names its graphic; Part A binds 18 of his statements to sections. The leash.
  6. planning/genesis-care-system/THE_CARE_SYSTEM.html — the 57 spreads as they stand. Open it in Chrome. Scroll every spread. Know what exists so you extend it and never rebuild it.
  7. planning/genesis-care-system/THE_CARE_OPERATING_MODEL.md · AGENCY_SYNTHESIS_S1566.md · VERIFICATION_THE_VOID.md · NAME_LOCK.md (the name is the Genesis Care System — CARE; "Soul Ledger" was a rename he rejected).
  8. On main (read via git show main:<path> or the main tree): reports/s1566/care-agency/SYNTHESIS.md (seven agency cells; their #1 note: the money is proof, not pitch; the last page is an invitation) · planning/THE_GENESIS_PACKAGE_S1331.md §Heartbeat/Canon (SEEN before asked) · prompts/DESIGN_LAW.md · planning/HOW_WE_TALK_TO_CARTER_S1542.md · prompts/_BASE_LAWS.md.

Big-agency benchmark (Step 1 OPTIMAL): before writing, read two published operating-model papers from the large consultancies or agencies you can reach (their "what it is" openers, their before/after process diagrams). Note in research.md what they do in the first 200 words that we do not. Match or beat it. Do not copy their vocabulary.

THE CLARITY LAW — EVERY HEADING, EVERY LABEL, EVERY CAPTION

PHASE 2 — ONLY AFTER HIS WORD ON THE ONE PAGE

Carry the page's plain statements into the 57 spreads: every section opens with its plain statement; every mechanism drawn end to end (the flow list in the punch list: §25 seven steps · §26 four gates · §30 governance override path · §37 four moves · §49 five pieces · §50 the diagnostic · §27 primitives · §31–35 functions · §39/§42 economic loops); the walkthrough notes fixed one by one; Defect Zero carried through; type floor and no-slab law kept; assembler pattern respected (edit the paper/M*.html sources, regenerate, check the merged CSS for collisions). Not one edit of Phase 2 before he has seen Phase 1.

LAWS (violate = the window is closed as failure)

DONE MEANS (Phase 1)