Autopoietic
Controlled Runtime AST Transformation inside Isolated Execution Environments
Stability Conditions · Structural Invariants · Differential Verification · Controlled Deployment
from the ability to establish its admissibility."
Separating Code Generation from Code Admissibility
A program transformation may produce syntactically valid source while introducing structural inconsistencies or behavioral regressions. Runtime code rewriting therefore cannot be validated by a single check. It requires layered evidence.
Syntactic
Does P₁ parse? Is the signature preserved? Are imports and decorators unchanged? S1–S6 cover formal validity.
Structural
Do all names have bindings? Are dependency cycles valid? Are there orphan variables? T1–T5 cover relational integrity.
Behavioral
Do return values, exceptions, and stdout match over a corpus? Are there new side effects? B1–B4 cover observable behavior.
No Dimension Guarantees Another
Isolation
Can candidate execution be separated from the original process? Evaluated via multiprocessing tests.
Verification
Does the candidate satisfy defined acceptance conditions? Evaluated via I_s ∧ I_t ∧ I_b.
Transition Integrity
Can activation occur without partial or inconsistent deployment? Evaluated via atomic swap.
Recoverability
Can the previous required state be restored? Evaluated via rollback and State Restoration Fidelity (deferred).
Phase I Complete · 118/118 Tests
View Test Results
Live view of implementation status: module-by-module tests, Phase I completion, and roadmap.
Open Dashboard →