Documentation

Component Stability

Stability classification for the 213 components in the registry snapshot below, last audited 2026-04-20. G6 has 269 components in total, so 56 carry no classification yet. Below the registry table: how G6 builds itself — the same self-training methodology used on external benchmarks, applied to the system’s own production readiness.

Built in G6

How G6 Builds Itself

G6 is built using its own developer-supervised self-training methodology — the same diagnostic loop used on external benchmarks (BBEH, GAIA, Omni-MATH) applied to the system’s own production readiness. Below is how 200+ components went from mixed-maturity stubs to today’s state, as a frontier system under active development, demonstrating Type 3 (theory-building) capability: identifying failure categories, constructing targeted fixes, and validating end-to-end through hardware integration.

Maturity Tier System

Before fixing anything, a theory of what “production ready” means was needed. The maturity tier system provides this — a Type 3 (theory-building) artifact that defines seven levels of component readiness.

The Self-Diagnosis Loop

This work is a Type 3 (theory-building) application of G6’s self-training methodology. Unlike Type 1 (one-shot harness engineering) or Type 2 (continuous resampling), Type 3 required the development team to use G6 tools to build a theory of what “production ready” means, diagnose where it falls short, categorise failures, iterate through targeted fixes, and validate end-to-end including hardware.

Lessons and Anti-Patterns

Connection to Type Hierarchy

The production readiness process itself is a Type 3 artifact — the development team using G6 to diagnose gaps, constructing a theory of how to close them, executing the plan, and documenting the meta-process for future reference.