Compares the empirical no-op claim with the appendix proof that guarantees freeze through maximum-move and structural-phase caps, then defines stronger counterfactual tests.
Research documentation: this page interprets a cited research source and defines evidence requirements. It does not claim a released Teleodynamic AI implementation.
Two distinct propositions
The empirical narrative claims that noop becomes dominant before external limits bind. A separate appendix argument guarantees eventual freeze when a configured maximum number of structural moves or structural-phase steps is reached. The latter is a termination guarantee, not by itself evidence of endogenous halt.
Reason-coded separation
Use distinct outcomes for selected noop, infeasible structural action, cooldown, endogenous-resource restriction, maximum moves, disabled structural phase, timeout, cancellation, memory guard, and process failure. A chart that collapses these causes into “no structural action” cannot support the stronger claim.
Counterfactual protocol
- Publish every hard cap and its observed utilization.
- Repeat with materially expanded caps.
- Run a cap-free research case where the host can do so safely.
- Compare noop margins and transition-rate trajectories before any cap becomes relevant.
- Use a conventional hard-stop controller as an explicit baseline.
- Verify that inner parameter adaptation remains active after the claimed freeze.
Acceptance criterion
Classify the result as emergent only when sustained noop selection and structural freeze occur with non-binding external guards, remain compatible across reasonable cap expansion, and preserve active inner adaptation. Otherwise classify the cause as externally bounded, inconclusive, or failed.
Safety boundary
Production hard limits remain mandatory. The experiment only requires that they be non-binding for the particular emergent-halt observation being claimed.
Scope
This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.
Engineering considerations
- Identify the source, version, target environment, and owner.
- Separate observed values from estimates and externally reported values.
- Record trade-offs, unsupported cases, and fallback behavior.
- Link performance statements to a compatible benchmark methodology.
Verification questions
- What exact artifact, revision, backend, and environment were reviewed?
- Which assumptions could change the result?
- Which data should be retained so another engineer can reproduce the conclusion?