Operating model
Three rails, one standards spine
The spine is the same artifact checklist; rails differ by facilitation density and response time—not by removing legal hygiene.
| Capability | Async archive | Vector cohort | Intensive bridge |
|---|---|---|---|
| Live critique hours | — | Weekly | Daily (5-day block) |
| Template depth | PDF + sheets | Versioned packs | Pack + sandbox data |
| Cross-team facilitation | Self-guided | Optional add-on | Included |
| Office hours | Monthly forum | Weekly room | Twice daily |
| Best when | Solo PMM calibrating | Steady release train | Pre-launch crunch |
Vector cohort is the default recommendation for teams running overlapping launches; choose Async archive if you only need templates this quarter, or Intensive bridge when three functions must align inside a month.