The complete semantic and architectural surface owned by a single accountable Planner. Contains every product capability, every technical layer, all invariants, all internal contracts, and all Cells. Planner-eligible peers may co-plan or rotate in; accountability stays with one person.
Domains, Tracks, and Cells.
GI gets its velocity from a clear, hierarchical geometry of responsibility. Planners govern Domains, Builders and Reviewers certify on Tracks, and Execution Plans target Cells.
A one-dimensional lane of responsibility. Capability Tracks represent product areas (Mapping, Identity, Notifications, Checkout). Layer Tracks represent technical layers (Mobile UI, Cloud API, Data, Firmware).
The atomic responsibility point. Each Cell is the intersection of a Capability Track and a Layer Track. It is the smallest unit of correctness in GI.
Atomicity for high-velocity flow.
Cells give you atomicity at high velocity without semantic sprawl. They're the enforcement points where invariants attach and architectural edges become predictable.
- 01 Execution Plans target a single Cell unless explicitly decomposed.
- 02 Review authority is defined at the Cell level.
- 03 Invariants are expressed at Cell boundaries.
- 04 Cross-cell work must pass through the Planner.
Certification, not org chart.
Certification grants permission, not assignment — a person can be certified for Builder and Reviewer work on the same Track and pick up either as needed. Staffing follows Track certification, not arbitrary team structures. Expertise becomes legible.
Certified on one or more Tracks. Requires semantic fluency, plan-execution accuracy, invariant familiarity, and capacity to handle every Cell involving the Track.
Deeper semantic mastery. Multi-Track fluency, awareness of cross-Cell implications, and judgment about invariant correctness. Not Cell-certified; Track-plus-oversight certified.
Eligible after certification across all Tracks in a Domain, demonstrated cross-Track reasoning, and proven ability to manage Cell interactions holistically.
- →No edits to a Track without Builder certification on that Track
- →No approvals on a Track without Reviewer certification on that Track
- →No review of one's own Builder work on the same artifact
- →Cross-Cell changes routed through the accountable Planner
- →Explicit contracts between Cells and Tracks
- →Invariants as first-class boundaries
- →Planners form contract surfaces
- →Execution Plans decomposed into respective Cells per Domain
- →No cross-Domain PRs
- →No cross-Domain mutable state
- →Coordination is Planner-to-Planner only