What this goes deep on, and what is only the setting.
A resource worth trusting is honest about what it is. This site is the operating system and governance doctrine for becoming an AI-native biotech, and that is where it goes deep. The biotech lifecycle is the setting that doctrine applies to. This map shows both plainly: what is covered, what is started, and, for the lifecycle, what is adjacent territory rather than a coverage promise.
The AI operating system
- Covered Strategy and operating model Permission, People, Programs
- Covered Sizing and sequencing the work The Scope Ladder
- Started Responsible use and governance AI Use Policy (control model still expanding)
- Covered Change and adoption The People-First Playbook
- Covered Use-case intake and routing The Build-vs-Buy Framework
- Covered Where to point AI, and where not The Value Map
- Covered The translating role and workforce The AI Product Partner
- Started Value, measurement, and benchmarks The PPP Scorecard (benchmark data to come)
- Covered AI-native knowledge work Thinking and writing with AI
The biotech lifecycle (the setting)
The operating system above is the subject, and where the depth is. The lifecycle is where that doctrine gets applied. A few functions are mapped; the rest is adjacent territory, deepened only when a real engagement makes the writing honest, not a checklist the site owes you.
- Started Discovery and target identification The Day-One Target Safety Triage (target safety first, more to come)
- Planned Preclinical development Adjacent territory, not the current focus.
- Planned Translational medicine and biomarkers Adjacent territory, not the current focus.
- Started Clinical development and operations Where AI Touches a Clinical-Stage Biotech
- Started Regulatory affairs and quality The validated-workflow boundary
- Planned Pharmacovigilance and safety Adjacent territory, not the current focus.
- Planned CMC, process development, and manufacturing Adjacent territory, not the current focus.
- Planned Medical affairs and commercial Adjacent territory, not the current focus.
- Planned Data, software, and AI infrastructure Adjacent territory, not the current focus.
- Planned Board and investor oversight Adjacent territory, not the current focus.
This is a deliberate scope, not a delay. The subject is the operating system and governance doctrine for becoming AI-native, and that is where the work goes. The lifecycle functions are mapped as the setting, and they deepen only when a real engagement makes the writing honest, never as invented coverage. New functional maps land on the model set by the clinical-stage map. If a function you need is still open, tell me what you are trying to do. A real problem is what moves it, not a promise on a roadmap.