Guided Intelligence
Read paper
§6 · Layered Safety

Velocity without safety is useless.

GI holds stability through a layered, always-on safety architecture. It replaces sprint-based QA cycles with continuous validation, fast containment, and clear severity-driven rules.

§6.1–6.3 · The stack

Seven layers, no single point of perfection.

Each layer is tuned for speed and minimal blast radius. Together they let every merge ship by default while preventing any severe issue from propagating.

Layered safety architecture
Seven overlapping layers. No single layer has to be perfect; together they protect velocity.
  1. 01

    AI Tests & Contract Invariants

    Pre-review

    Unit, contract, migration, smoke. Run on every build.

  2. 02

    Reviewer Semantic Gate

    Pre-merge

    Final human authority. Intent, invariants, domain coherence.

  3. 03

    Ring Deployments

    Deploy

    Ring 0 (internal) → Ring 1 (limited real users) → general.

  4. 04

    Feature Flags & Blast Radius

    Deploy

    Contain unknowns. Toggle without redeploy.

  5. 05

    Monitoring & Observability

    Runtime

    Logs · metrics · traces · domain health checks.

  6. 06

    PAT Continuous Validation

    Runtime

    Async exploratory + regression on running system.

  7. 07

    Severity Model (Sev1–5)

    Governance

    Standardized response. Only Sev5 stops the line.

§6.4 · Severity Model

Severity, not process, governs flow control.

Severity determines how a defect impacts flow. Only a Sev5 stops the line.

Severity governs flow control
Only Sev5 stops the line. Everything else flows through with appropriate response.
Sev 5
Stop-the-Line
Catastrophic invariant break · unsafe migration · domain-violating logic · reproducible crash threatening stability Action Freeze merges & promotions · rollback or flag-off · fix immediately · resume once invariants are restored
Sev 4
Major
Localized API errors · noticeable performance degradation Action Flow continues · prioritized fix · optional domain-level constraints
Sev 3
Moderate
Non-catastrophic bugs · UI errors · regressions in narrow surfaces Action Flow continues · scheduled fix · extra checks applied if needed
Sev 2
Minor
Minor UI issues · edge-case quirks Action Logged · scheduled · no effect on flow
Sev 1
Trivial
Logging noise · cosmetic inconsistencies Action Logged · scheduled · no effect on flow
§6.5 · Sev5 protocol

Stop-the-Line

When a Sev5 surfaces at Ring 0 or Ring 1, the response is sequenced and immediate. The key point: a Sev5 halts future flow. It does not ship buggy code to production. Ring 0/1 guarantees safe containment.

  1. 01 Immediately freeze merges
  2. 02 Halt promotions
  3. 03 Rollback or toggle flags
  4. 04 Notify domain stakeholders
  5. 05 Patch fix through the GI Flow
  6. 06 Resume once domain invariants are restored
§6.8–6.12 · PAT

Asynchronous system validation.

PAT runs alongside the GI Flow. It probes the deployed system instead of gating individual PRs or waiting on a batch of merges. Its influence is interrupt-driven, not gate-driven.

Exploratory testing

Freeform, curiosity-driven probing for edge-case failures, unexpected system interactions, stateful errors, and cross-domain inconsistencies. AI handles permutations while human intuition picks the direction.

Regression testing

Automated, maintained, and evolved by PAT. Covers domain-critical workflows, integration paths, invariants, and known-sensitive operation sequences. Runs continuously across rings.

The long-term equilibrium: humans test ideas, AI tests permutations.

Over time, PAT evolves into a self-improving guardian layer. Human testers point at the semantic areas worth probing and AI handles the mechanical sweep. The safety net scales with system complexity without slowing flow.

§6.7 · Defining property

Velocity and safety are both continuous. Flow only stops when the system has to be protected.