Defines the resource as internal state changed by outcomes and action costs, consulted by action selection, and coupled to both adaptive timescales rather than imposed only as an external cap.
Research documentation: this page interprets a cited research source and defines evidence requirements. It does not claim a released Teleodynamic AI implementation.
Required properties
The resource must be stateful, changed by actions or outcomes, consulted when determining action viability, and coupled to both adaptive processes. A fixed token budget or memory limit alone is external.
Units and calibration
Publish whether the resource is dimensionless, normalized, cost units, or calibrated physical energy. Do not label a synthetic score “joules” without measurement. Record initial value, bounds, decay, reward schedule, penalties, action costs, and restart behavior.
Good engineering
Hard memory and safety limits remain mandatory even if they are external. Record them separately so a crash-prevention guard is never mistaken for endogenous regulation.
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?