Maps theoretical resource variables to measurable browser proxies while warning that CPU duration, owned bytes, and battery hints are not direct thermodynamic-energy measurements.
Research documentation: this page interprets a cited research source and defines evidence requirements. It does not claim a released Teleodynamic AI implementation.
Architecture topic: this page does not claim that the WordPress website implements or executes the described runtime behavior.
Available proxies
Candidate measurements include worker duration, operation estimates, owned WASM memory, GPU buffer allocations, cache bytes, active structural units, and application-level task feedback.
Unavailable or unreliable signals
Browsers generally do not expose trustworthy total system memory, thermal headroom, per-origin joules, or universal battery state. Feature availability and privacy restrictions vary.
Design rule
Define a deterministic internal ledger from the signals the implementation actually owns. Keep physical-energy calibration as a separate experiment and retain external hard limits for safety.
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?