GitHub master
Canonical working record for Markdown, HTML, CSS, scripts, manifests, and version history.
Control tower · recorded evidence cutoff 4 Sep 2026 · static snapshot
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.
Core findingRevision 3.2 is not today's authorityIt was the latest old factory picture. The 4 September NOW.md explicitly makes old process HTML reference-only and names V5.6 as the current email baseline.
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.
06 / Chain of custody
Working material crosses one explicit promotion boundary
Papers move left to right. Nothing in the workroom carries a seal. The barrier lifts only for a named candidate, and Steve’s seal is stamped on exactly the approved scope; NOW.md then points at the sealed baselines. Live evidence arrives as mail and can justify a deliberate correction, not a silent one.
- Custody moves forward
- Sealed · explicit scoped approval
- Revise · observed evidence returns
- Promotion boundary
- Unsealed working paper
Nothing below NOW.md may promote itself upward
Routing selects the room. The protocol controls promotion. Live evidence can correct recorded state but cannot silently rewrite it. Working material becomes a specific candidate, is tested in its intended use, and crosses an explicit approval boundary; only the named portion Steve approves is eligible for promotion.
Workroom
Discuss + explore
Any system may explore, argue, test, or make competing candidates. Strong wording and confident conclusions do not constitute approval.
Takes inQuestions, options, research and reactions.
Hands onCandidate ideas and artifacts.
CheckStrong wording and confident conclusions do not constitute approval.
Reviewable version
Named candidate
A draft with a clear scope and version—something Steve can inspect and choose. Candidates stay candidates until explicitly promoted; a candidate may be returned to the workroom to revise.
Takes inA draft with a clear scope and version.
Hands onSomething Steve can inspect and choose.
CheckCandidates stay candidates until explicitly promoted.
Promotion boundary
Steve approves
Named target, named scope, no inference. Material becomes authoritative only when Steve explicitly approves a named plan, artifact, version, or production action. DECIDED.md records that specific approval and its scope.
Takes inThe exact item, scope, and requested action.
Hands onAn explicit selection, execution approval, or durable decision.
CheckOnly the named scope is promoted. No inference from conversational tone.
Observed on surface
Live evidence
Received messages, files and real behavior—evidence that can justify a deliberate correction. Cloudflare Pages serves the root product website; Beehiiv serves the www publication, subscriptions, accounts, upgrades, and email. Verify each behavior on the system that delivers it. Verify, then update deliberately.
Takes inReceived messages, files and real behavior.
Hands onEvidence that can justify a deliberate correction.
CheckObservation informs an update; it does not silently rewrite NOW.
Current room pointer
Motel/The-Next-Patient/NOW.md
Names what to use; does not prove live health. A deliberate state update and approved references produce the current starting point for the next worker. Routing files (AGENTS + README) lead here; old sessions do not override it.
Takes inA deliberate state update and approved references.
Hands onThe current starting point for the next worker.
CheckRouting files lead here; old sessions do not override it.
Named baseline
Core brand / REV 2
Core logo, palette, and general type family. Working package, not universal doctrine. Email-specific learning does not silently replace core guidance.
Takes inThe scoped core identity.
Hands onGeneral identity reference.
CheckEmail-specific learning does not silently replace core guidance.
Scoped application
Email / V5.6
Email application profile and selected template produce the newsletter baseline. Current visual baseline; not final Beehiiv production HTML or client-certified. Selected design is not proof that a live send is ready.
Takes inEmail application profile and selected template.
Hands onThe newsletter baseline.
CheckSelected design is not proof that a live send is ready.
- Recorded in
- authority-assets.html and schematics.js authority map (visual-operating-system v1.3.2) · spine/PROTOCOL.md §3a
- Standing
- The existing approval principle is visualized here. No new rule or decision is being written by this design revision.
- What this tower cannot do
- Promote anything. Selection changes the reading, not the record.
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.
Concern
Current source
Authority boundary
Verified
Repository governance
spine/PROTOCOL.mdControls writes and promotion. Build, test, or strong language does not create a decision.
GitHub master · 4 Sep
TNP current state
Motel/The-Next-Patient/NOW.mdLast recorded state, not proof that a live service is healthy.
Commit 3cb18595 · 4 Sep (re-verified 6 Sep in NOW.md)
Brand identity
work/brand-kit/ REV 2Core logo, palette, and general type family. Working package, not universal doctrine.
Reconciled · 4 Sep
Email application
brand-kit/applications/EMAIL.mdEmail-specific colors, sizes, hierarchy, and module order; does not automatically govern the website or decks.
Commit 3cb18595 · 4 Sep
Email design
email-template/the-next-patient-email-v5.6-working-base.htmlCurrent visual baseline. Not final Beehiiv production HTML or client-certified.
Commit 3cb18595 · 4 Sep
Positioning
work/POSITIONING.mdWorking positioning. Its version blocks do not become production doctrine by themselves.
Named by NOW · 4 Sep
Editorial craft
research/voice-constitution-2026-07-18.mdHistorical craft reference, partially superseded; cannot override positioning or a production brief.
Boundary named by NOW · 4 Sep
Binary pointers
Motel/The-Next-Patient/assets/MANIFEST.csv80 R2 pointers recorded in the room manifest (6 Sep). Store and object location are resolved through the manifest.
Reconciled · 4 Sep
Reader-facing production
Cloudflare product site + Beehiiv publication
Cloudflare Pages serves the root product website; Beehiiv serves the www publication, subscriptions, accounts, upgrades, and email. Verify each behavior on the system that delivers it.
Live review · 4 Sep (product site verified 6 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.
Cloudflare R2
Working and generated imagery, candidate outputs, and render proofs. Accessed through its S3-compatible API.
Google Drive
Medical records, signed or executed documents, scans, and static history. It is not workspace memory.
Beehiiv
Email editor, templates, posts, subscribers, polls, landing page, and actual send behavior.
Cloudflare surfaces
ops.ztsholdings.com and read.ztsholdings.com remain delivery destinations for the legacy Intel and research flows.
Obsidian
A visual local checkout and working interface. It mirrors or edits the repo but does not outrank GitHub master.
AI chats
Useful for exploration and production. Durable conclusions must be handed off as named files or evidence.
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 timeline explains sequence; NOW.md establishes present authority. REV 3.2 is the last old map—not the current operating command.
Three-track picture. Its status began aging the day it was drawn.
Recorded how the initial Issue 00 draft actually moved.
Newest legacy factory structure. Later changes ended its authority claim.
Strongest evidence that the older line could publish and deliver.
NOW.md names the current baseline and makes old process HTML reference-only.
File
Disposition
Why
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.
Durable structure
Station-based flow, file handoffs, reversible work before Steve's gate, live-surface proof, and feedback into the next run.
Expired specifics
Old owners, Claude-as-manager, v1/v3 template assumptions, self-updating status labels, obsolete prices, and the retired direct Stripe checkout on Pages. The independent root product website is now live on Pages; paid checkout remains with Beehiiv.
Process doctrine
Source layers, kill gates, ranking rules, editor machinery, image rules, cadence, and any instruction created by compiling a conversation.
Current baseline
Current NOW.md, REV 2 core identity, the email application profile, V5.6, the room manifest, and observed behavior on the root product website and Beehiiv.
Promotion
Never from conversation · eligible when named
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.