Specifies reproducible seeds, ordering, ablations, counterfactual controllers, raw traces, phase metrics, hard-stop controls, and failure criteria for a teleodynamic claim.
Research documentation: this page interprets a cited research source and defines evidence requirements. It does not claim a released Teleodynamic AI implementation.
Pre-register the claim
State which of the five commitments is being tested, the exact implementation revision, data, baseline, metrics, and failure criteria before collecting results.
Minimum runs
- Teleodynamic controller enabled.
- Resource coupling ablated.
- Structural actions disabled.
- Hard-stop baseline.
- Multiple seeds, orderings, and initial-resource values.
Required outputs
Release raw event traces, phase metrics, final structures, model scores, resource trajectories, configuration, hardware and browser environment, and analysis code where licensing permits.
Falsification examples
The claim fails if structure freezes only because an external cap binds, if resource state never changes action viability, if structural and parameter updates are indistinguishable, or if phases cannot be recovered beyond post-hoc labeling.
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?