THE NEXT PATIENTAI-driven health care intel

Enterprise operating model · reconciled view · static snapshot

Who creates value—and who controls it

Steve supplies intent and final approval. ChatGPT / Codex runs the production line; Grok, Claude, Fable, and other systems may contribute bounded research or design inputs. The protocol and named GitHub versions preserve continuity.

ConclusionSteve plus explicit gatesGitHub and R2 are the durable record. ChatGPT / Codex is the production workbench; contributors do not enter production unless Steve changes the operating model.
The system survives a change of model because authority lives outside the model.

What changed from the old maps. The Claude/Grok ownership split was removed. Jobs now belong to stations and evidence requirements, so the worker can change without redrawing the business.

02 / Organization · the command tree

One owner. A shared record. Replaceable work cells.

Authority descends from one seat, through a one-way membrane, into the shared record; the record feeds three replaceable work cells; observed evidence climbs back. Lime is decision authority, green is work and file handoff, blue is evidence returning.

  • Decision authority (descends)
  • Work and file handoff
  • Observed evidence (climbs back)
  • The seat · Steve
  • The spine · durable record

Steve controls the gate; the spine controls continuity; work cells are replaceable

GitHub is the continuity layer, not the boss. Steve owns scope and approval; ChatGPT / Codex owns the production handoffs. Files, not memory, cross the boundary between cells. Claude, Fable, Grok, and other systems may contribute named inputs, but they do not operate the production line.

Recorded in
system-map.html and schematics.js model map (visual-operating-system v1.3.2) · spine/PROTOCOL.md §3a
Where it goes deeper
Structure, not staffing or live integration status. X/Grok Bot scouting remains held; Grok Heavy remains the broad research surface; legacy operations are outside this product.
What this chart cannot do
Assign a permanent job to a model or certify a live integration. Selection changes the reading, not the record.

End-to-end flow

From signal to observed result

Files and links cross each handoff. Conversation alone does not.

No.
Owner
Stage
What crosses
01
Inputs
Signals
Primary records, Grok research, the newsletter screen, Gmail, and commissioned research.
02
Evidence
Source package
Provenance, date, links, context, and open questions. Candidate material—not decisions.
03
Production
Editorial factory
Select, copywrite, challenge, design, assemble, and verify on the current working baseline. Copywriting is a named pass—not implied by drafting.
04
Human gate
Steve approves
The named issue, action, or production version—and only that scope.
05
Surfaces
Deliver
Beehiiv for the publication; Cloudflare for operating and reading surfaces; Telegram for notices.
06
Observed evidence
Learn
Received email, rendering, clicks, replies, failures, and corrections feed the next run.

The operating cast

Role, not platform loyalty

The responsibility stays stable even if the tool doing the work changes.

Final authority

Steve

Sets intent, rejects bad paths, approves named production actions, and presses the irreversible gate.

Canonical record

GitHub master

Holds text, code, current-state routing, provenance, and manifests. It is not a binary store and it does not prove a live service is healthy.

Binary store

Cloudflare R2

Holds generated and working images, render proofs, and other binaries. GitHub points to them through the manifest.

Primary workbench

ChatGPT / Codex

Design, production, browser operation, verification, implementation, and orchestration within a named job.

Research worker

Grok

Fast discovery, broad searches, second opinions, and research packages. Its output enters as evidence, not truth.

Contributor

Claude / Fable

May supply named research, critique, or design candidates. Their outputs enter through the same evidence and approval gates; neither participates in routine production.

Publication surface

Beehiiv

Email template, posts, website, subscribers, polls, and delivery. Live behavior must be checked there.

Web infrastructure

Cloudflare

R2 assets and the current ops/reading surfaces. The R2 S3-compatible route moves objects; GitHub does not.

One-way membrane

Speed without accidental governance

The system is deliberately permissive before production and strict only at promotion.

Working room

Explore freely

Any system may explore, argue, test, or make competing candidates.

Name it
Named candidate

Inspectable version

A specific version becomes inspectable and comparable. Still non-authoritative.

Test it
Live proof

Real surface

The artifact is tested on its real delivery surface. Results—not confidence—move it forward.

Steve locks
Scoped approval

Named target

Steve explicitly locks a named target. Only then can current state or a decision record change.

Boundaries

What this map establishes—and does not

Establishes
  • Stable responsibilities across AI tools.
  • GitHub and R2 as the durable handoff layer.
  • Steve retains the human approval gates.
  • Evidence returned from every production run.
Does not establish
  • A permanent Claude-versus-Grok job split.
  • Approval of old source or editorial rules.
  • Health of any unverified live automation.
  • A new entry in DECIDED.md.