Software Engineering
The domain in which the methodology has been most extensively studied to date.
Verifier-governed research into candidate mutation, abstraction reuse and cross-repository transfer on TypeScript/JavaScript codebases of production-scale complexity, under deterministic validation with evidence retention, rollback and falsification. External artifact production has been demonstrated in the H3, Hono, Vite and TypeORM ecosystems under the Foundation v1.0 baseline. Autonomous software engineering is not asserted to be solved and no commercial production deployment is claimed.
- Languages outside the current verified surface (Rust, Go, Swift) are not yet measured.
- Design-level architectural refactors are out of current scope.
- Continuous autonomous production improvement of live codebases is not claimed.
- Long-horizon stability beyond 500 epochs in a single lineage is not yet observed.
Runtime verification methodology
Invariant classes and gate criteria that decide whether a mutation may promote.
Structural compounding hypothesis
Hypothesis relating dependency structure and abstraction reuse to observed compounding of verified capability.
Model-substitution methodology
Model-agnostic evaluation: findings must hold under substitution of comparable frontier or specialist models.
Each reference links to the signed dossier for that experiment. Nothing on this page claims deployment — these are the artifacts that inform the current scope.
- How does portability behave in Rust and Go once a verification substrate is built?
- What is the failure mode for chains beyond depth 20?
Extend the verification surface to a second language stack with a public evidence summary and an access-controlled reproduction kit.