Treats maintaining the current structure as an explicit candidate action with a recorded score, reason, and recovery path rather than as silent inactivity.
Research documentation: this page interprets a cited research source and defines evidence requirements. It does not claim a released Teleodynamic AI implementation.
First-class candidate
Noop retains the current structure. It should be scored beside every feasible structural alternative rather than used as a default after alternatives fail silently.
Reason codes
- No structural improvement.
- Benefit does not cover complexity cost.
- Insufficient endogenous resource.
- Cooldown or eligibility rule.
- Ambiguous evidence or tie.
- External safety guard, recorded separately.
Observability
Log the noop score, strongest alternative, margin, consecutive-noop count, and whether inner dynamics still executed.
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?