Describes discrete structural interventions, candidate-action evaluation, eligibility, cooldowns, and the distinction between changing parameters and changing the hypothesis class.
Research documentation: this page interprets a cited research source and defines evidence requirements. It does not claim a released Teleodynamic AI implementation.
Structural actions
Outer dynamics alter the hypothesis class: creating, deleting, replacing, composing, routing, or activating representational units. Changing a cache, context length, or execution backend is structural only when the declared hypothesis class actually changes.
Candidate ledger
For every eligible event, retain the complete candidate set, constraints, objective components, infeasible reasons, tie-breaking rule, and selected action. Missing alternatives prevent audit of local rationality.
Cadence
Document cooldowns, minimum evidence windows, and why outer actions become rare. An externally disabled structural loop is not emergent freeze.
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?