Defines stable event fields for state revision, candidate actions, objective terms, selected action, costs, rewards, transitions, phases, and externally imposed guards.
Research documentation: this page interprets a cited research source and defines evidence requirements. It does not claim a released Teleodynamic AI implementation.
Core event fields
- Event ID, UTC timestamp, run ID, seed, source revision, and state revision.
- Input and feedback references with privacy-safe redaction.
- Prediction, confidence, and task score.
- Candidate action IDs, feasibility, predictive term, complexity term, resource term, and total score.
- Selected action, reason code, structural before/after IDs, and parameter revision.
- Resource before, reward, penalty, decay, cost, and resource after.
- External guard flags, phase label, transition-rate window, and noop run length.
Privacy
Raw prompts or personal observations should not be placed in telemetry by default. Use opaque references, local retention, explicit consent, and bounded diagnostic exports.
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?