Glossary

The intersection of a capability track and a layer track.

Represents the entire semantic surface a Planner oversees, comprising all capability and layer tracks and the cells they form across the product or system.

The AI-generated plan that bridges Planner intent to Builder execution. It outlines steps, constraints, scope, contracts, and success criteria.

The continuous, non-batched, core pipeline of the velocity model.

The operating framework. A structured, AI-native engineering model built around continuous flow, layered safety, and human semantic oversight.

A principle and responsibility model where humans provide semantic judgment, constraints, and contextual decisions while AI performs most mechanical execution.

The primary input to the GI Flow. A structured statement of what the system should achieve.

A condition, rule, or system property that must always hold true within a domain. Invariants define the non-negotiable behaviors, data relationships, contracts, and assumptions that protect system correctness.

Work that can be executed deterministically by AI: code generation, refactors, boilerplate, test creation, formatting, and structured analysis.

A continuous, asynchronous validation layer that performs exploratory testing, regression verification, invariant checking, and system-level validation outside the main flow.

Canary deployment stages. Ring 0 = internal validation environment; smallest blast radius. Ring 1 = limited real-user exposure before general release.

The primary human contribution within GI. Humans evaluate meaning, correctness, intent alignment, trade offs, and domain invariants rather than mechanical implementation.

The standardized classification system for bugs, regressions, and system anomalies. Sev5 stops the line; Sev1–4 allow flow to continue with appropriate response.

Structured HIL role that defines who holds responsibility at each stage of the flow. Shifts define boundaries, prevent role bleed, and ensure clear semantic ownership at every step.

A GI Team consists of Builders and Reviewers. Individuals may belong to multiple GI Teams. The Planner oversees the entire Domain rather than any single Team.

A one-dimensional lane of responsibility within a Domain. Capability Tracks correspond to product capabilities, and Layer Tracks correspond to technical layers.