The tools and surfaces that make up VDC's working environment, and the discipline that governs how they connect. The agent reads this before proposing any new tool, integration, or automation.
The conversational AI surface for both Bill and Peter. Used in browser or via the Claude desktop app, depending on the device. This is where the everyday work happens: drafting, thinking, planning, prepping for meetings, working through problems with the agent.
Both owners hold Claude Pro accounts. The Anthropic GitHub connector is configured inside each owner's account and points at the private AIOS repo so that every conversation in claude.ai loads VDC's foundational context automatically.
The terminal-based Claude environment. Used by Peter when he wants direct access to the AIOS repo on his own machine and a more developer-flavored loop. Bill does not need this surface; his work happens entirely in claude.ai.
When Peter uses Claude Code, he reads from a local clone of the same AIOS repo claude.ai connects to. There is one source of truth across both surfaces.
The private repo holds the AIOS itself: the foundational context files, the agent definitions, the skills the AIOS provides, and the engagement-related project material that should travel with the system.
Bill and Peter are admins. Natalee is a collaborator who pushes updates. Both owners can read the repo through the GitHub connector inside claude.ai without ever opening GitHub directly.
The partnership's email, calendar, and document infrastructure. A Business Associate Agreement (BAA) is signed with Google, which makes Workspace a HIPAA-covered environment for A New Life patient and operational documents.
Operational documents, intake forms, billing, contracts, and any patient-related material live in Google Drive, never in GitHub. The AIOS repo holds context and methodology; Drive holds business data.
The active operating tracker for the A New Life launch. Three sections, none more, none fewer:
Each card carries an owner, a due date, and a status (green, yellow, red). The agent never proposes adding a fourth section, never recommends migrating to another tool, and never duplicates Trello content into the AIOS repo.
Anthropic's task-queue product, used by Brian to hold the Launch Tracker hydration brief. The brief sits in the queue with an activation prompt that tells CoWork where to look and what to execute.
The agent treats CoWork as a running process, not as a surface to design new work in. New CoWork briefs are written deliberately and only when the work behind them has been run manually enough times to be stable.
A custom executive dashboard hosted on Replit, built before the AIOS engagement. It exists alongside the rest of the stack. The AIOS does not rebuild, replace, or reach into it. The agent never proposes work that touches the dashboard.
A Linux virtual machine Peter operates on DigitalOcean for power-user exploration. Adjacent to the rest of the stack, not yet integrated with it. The agent treats this as Peter's personal sandbox and does not assume the rest of the stack runs through it.
Three rules, installed during the Builder Immersion Session and inherited by every agent that operates inside VDC's environment.
The shape of the stack reflects this discipline directly. Every tool above earned its spot by being the single right place for the work it holds. The agent's default disposition toward any new tool, any new integration, or any new automation is no, until the case for it has been made by the work itself.
Items to confirm or correct directly with Bill or Peter as the engagement progresses.