THE NEXT PATIENTAI-driven health care intel

Control tower · GitHub master checked live

Where truth, approval, and files live

This is the reconciliation layer: the present authority chain, the storage map, and the disposition of the older TNP diagrams and specifications after comparing revision dates and supersession language.

Newer does not automatically win. The current router names what wins.
Forensic rule used here

Read the revision trail, note explicit supersession, compare it with today's NOW.md, then verify the live surface. A filename, “locked” label, or old approval is insufficient.

Authority tree

How current truth is established

Routing selects the room. The protocol controls promotion. Live evidence can correct recorded state but cannot silently rewrite it.

The Next Patient authority tree Steve's explicit scoped approval governs promotion. AGENTS and README route to The Next Patient NOW, protocol governs writes, NOW names working artifacts, and live Beehiiv evidence verifies operations. PROMOTION AUTHORITY Steve's scoped approval Named target · named scope · no inference WRITE AND DECISION GATE spine / PROTOCOL.md Build is not approval · discussion is not a rule CURRENT RECORDED STATE Motel / The-Next-Patient / NOW.md Names what to use · does not prove live health ROUTING ONLY AGENTS + README OPERATIONAL EVIDENCE Live Beehiiv surface Verify, then update deliberately CURRENT WORKING Brand REV 2 Core identity + email profile CURRENT WORKING Email V5.6 Visual baseline Not client-certified WORKING Positioning Current language Not doctrine REFERENCE Editorial craft Historical voice Partially superseded POINTER LAYER Asset manifest 78 verified R2 object pointers
Nothing below NOW.md may promote itself upward.Live evidence informs a deliberate state update; it does not create one automatically.

Current named sources

What can speak today

“Current working” means use it as the starting point. It does not mean final, universal, or live-certified.

ConcernCurrent sourceAuthority boundaryVerified
Repository governancespine/PROTOCOL.mdControls writes and promotion. Build, test, or strong language does not create a decision.GitHub master · 4 Sep
TNP current stateMotel/The-Next-Patient/NOW.mdLast recorded state, not proof that a live service is healthy.Commit 3cb18595 · 4 Sep
Brand identitywork/brand-kit/ REV 2Core logo, palette, and general type family. Working package, not universal doctrine.Reconciled · 4 Sep
Email applicationbrand-kit/applications/EMAIL.mdEmail-specific colors, sizes, hierarchy, and module order; does not automatically govern the website or decks.Commit 3cb18595 · 4 Sep
Email designemail-template/the-next-patient-email-v5.6-working-base.htmlCurrent visual baseline. Not final Beehiiv production HTML or client-certified.Commit 3cb18595 · 4 Sep
Positioningwork/POSITIONING.mdWorking positioning. Its version blocks do not become production doctrine by themselves.Named by NOW · 4 Sep
Editorial craftresearch/voice-constitution-2026-07-18.mdHistorical craft reference, partially superseded; cannot override positioning or a production brief.Boundary named by NOW · 4 Sep
Binary pointersMotel/The-Next-Patient/assets/MANIFEST.csv78 verified R2 pointers. Store and object location are resolved through the manifest.Reconciled · 4 Sep
Reader-facing productionLive Beehiiv publicationBeehiiv is authoritative for what readers can actually see, receive, and click.Live review · 4 Sep

Storage and work surfaces

One pointer layer, several homes

A file's home reflects its function. None of these surfaces replaces the authority chain above.

Text & code

GitHub master

Canonical working record for Markdown, HTML, CSS, scripts, manifests, and version history.

Generated binaries

Cloudflare R2

Working and generated imagery, candidate outputs, and render proofs. Accessed through its S3-compatible API.

Static archive

Google Drive

Medical records, signed or executed documents, scans, and static history. It is not workspace memory.

Live publication

Beehiiv

Email editor, templates, posts, subscribers, polls, landing page, and actual send behavior.

Published utilities

Cloudflare surfaces

ops.ztsholdings.com and read.ztsholdings.com remain delivery destinations for the legacy Intel and research flows.

Local navigator

Obsidian

A visual local checkout and working interface. It mirrors or edits the repo but does not outrank GitHub master.

Workrooms

AI chats

Useful for exploration and production. Durable conclusions must be handed off as named files or evidence.

Pointer layer

Asset manifest

The stable bridge between GitHub text and binary storage. Changing the store should require changing the pointer, not every artifact.

Revision forensics

What the older documents became

The disposition below is the key reconciliation. The files are not treated as parallel authorities.

First factory snapshot

Three-track picture. Its status began aging the day it was drawn.

First physical line

Recorded how the initial Issue 00 draft actually moved.

REV 3.2

Newest legacy factory structure. Later changes ended its authority claim.

Issue 00 live

Strongest evidence that the older line could publish and deliver.

Authority reset + V5.6

NOW.md names the current baseline and makes old process HTML reference-only.

The timeline explains sequence; NOW.md establishes present authority.REV 3.2 is the last old map—not the current operating command.
2026-08-06-factory-floor.htmlSuperseded snapshot

First full three-track map. Useful for the distinction between issue production, audience building, and surface/payment work; its status badges and old machine state expired immediately.

2026-08-19-production-line.htmlExecution evidence

Documents how the first draft line physically ran on 19 August. Superseded as current process by the 26 August run, 31 August publication, and 4 September V5.6 baseline.

claude-grok-station-map-2026-08-20.htmlOwnership retired

The station-level handoffs remain useful. The Claude/Grok ownership split is stale and conflicts with the new model-neutral orchestration design.

the-board-spec-2026-08-21.mdLatest old structure

Evolved through REV 3.2 on 27 August. It is the strongest legacy description of stable spatial organization, but its rules, platform assignments, v3 template, and live claims do not transfer automatically.

2026-08-22-STATE-OF-PLAY.mdState overtaken

A dated synthesis of product and reader state. Later positioning work, Issue 00 publication, the authority cleanup, and V5.6 overtook it.

2026-08-25-harvest-rank-criteria.mdRevalidate mechanics

Explicitly superseded the 19 August criteria and was exercised in one production run. Its source layers, gates, ranking language, and cadence still require review under the September promotion boundary.

the-tnp-factory-floor-rev3-2026-08-26.htmlHuman reference

The REV 3.2 render is the latest old visual. It supplies spatial and station clues only; the 4 September NOW.md explicitly makes old process HTML reference-only.

issues/2026-08-31-issue-00-v00/Observed evidence

The strongest proof that the old line could create and publish a complete issue. It is a production record, not the template direction for the next issue.

NOW.md + REV 2 email profile + V5.6Current baseline

The current starting point for new production. Design rationale lives in the lineage file, but only the named V5.6 artifact and scoped email values control the work.

Reconciliation verdict

Keep, replace, revalidate

This is the logic applied to the new system and factory views.

Keep

Durable structure

Station-based flow, file handoffs, reversible work before Steve's gate, live-surface proof, and feedback into the next run.

Replace

Expired specifics

Old owners, Claude-as-manager, v1/v3 template assumptions, self-updating status labels, obsolete prices, and Pages as reader-facing authority.

Revalidate

Process doctrine

Source layers, kill gates, ranking rules, editor machinery, image rules, cadence, and any instruction created by compiling a conversation.

Anchor

Current baseline

September 4 NOW.md, REV 2 core identity, the email application profile, V5.6, the room manifest, and observed Beehiiv behavior.

Never promote from conversation

  • Brainstorms and alternatives.
  • Straw-man or steel-man arguments.
  • Research conclusions and model language.
  • “Locked” filenames without scoped approval.
  • Status that was not verified on the live surface.

Eligible for explicit promotion

  • A named artifact or production version.
  • A scoped execution plan Steve explicitly approves.
  • A live behavior verified on the real surface.
  • A repeated production lesson Steve chooses to make durable.
  • Only the portion actually named in the approval.