Scope
This note defines the minimum mathematics needed to turn an indication into a decision-bearing result. It connects the metrology audit, Candidate 014, and the energy model. It does not replace a domain-specific measurement procedure.
Result record
For one measured quantity, retain
where:
| Symbol | Meaning | Unit or declaration |
|---|---|---|
| measurand: quantity intended to be measured | physical unit or named reference scale | |
| value estimate attributed to | same unit as | |
| combined standard uncertainty | same unit as | |
| expanded uncertainty | same unit as | |
| coverage factor such that | dimensionless | |
| object, population, component, state, location, and conditions | typed metadata | |
| measurement procedure and model | versioned identifier | |
| calibration chain, references, corrections, and validity scope | dependency record | |
| environment and influence quantities | values with units | |
| sampling, selection, missingness, and association contract | probability/model record | |
| decision rule, tolerance, guard band, and risk allocation | versioned rule | |
| data, software, instrument, certificate, and transformation provenance | dependency graph | |
| start and end of the supported interval | seconds on a named time basis |
The tuple is incomplete when a field that can alter the downstream decision is missing. A confidence score alone cannot represent these distinct dependencies (C-519–C-524).
Measurement model and dimensional validity
Let
where input quantity has unit and has unit . Every additive term produced by must have unit . Software, coefficients, numerical precision, and preprocessing that implement are part of . A coefficient of friction is therefore not portable without its interface pair, load/motion state, environment, procedure, support, and history (C-1497).
For estimates , first-order covariance propagation gives
has unit and covariance has unit , so every summand has unit . Removing off-diagonal terms asserts independence; it is not a harmless simplification when calibration, clock, environment, preprocessing, prior, or training data are shared (C-525, C-533). For nonlinear or discontinuous models, propagate sampled input distributions and report empirical interval coverage.
Error, correction, and coverage
Given reference value ,
Error , correction , and corrected estimate have unit . The estimated correction remains uncertain. Expanded uncertainty is
where is dimensionless. A stated does not by itself establish a coverage probability; the distributional method and achieved coverage must be reported (C-524, C-526).
Repeatability and reproducibility
For replicate result from location , operator , run , and system , a variance-component null is
and every random effect have unit ; their variances have unit . The design declares which factors are fixed or random and which are confounded. A short run with one system estimates repeatability, not broad reproducibility (C-527, C-528).
Decision rules and guard bands
Let specification require , where has unit . A simple guarded acceptance rule is
where guard multiplier is dimensionless. Increasing generally reduces false acceptance while increasing false rejection. Choose from a declared loss or risk allocation; do not hide that choice inside “confidence.” The rule version, tolerance version, uncertainty method, and cost owner are dependencies of the decision (C-531).
Drift and recalibration
Represent indication drift relative to the last accepted calibration as
where , check-standard result , and reference value share unit . The review policy is a function
where is calibration/check history, is decision risk, is current uncertainty, is calibration cost, and is equipment and environment state. Inputs keep their native units; returns a categorical action such as continue, check, restrict, recalibrate, or quarantine. A calendar interval alone is not evidence of stability (C-532).
Dependency invalidation
Let a directed acyclic graph contain calibration, raw-data, software, model, transformation, result, and decision versions. Edge means that node depends on node . If dependency changes or fails review, its invalidation cone is
where denotes a directed path and is a set of version identifiers. Each affected node is re-evaluated, superseded, restricted, or withdrawn; provenance alone does not decide which action is correct (C-534, C-535).
Energy-measurement instantiation
For sampled power at time with interval ,
where is W, is s, and is J. The model must name the electrical boundary, voltage/current/phase calibration, bandwidth, anti-aliasing, clock alignment, integration rule, missing-sample policy, warm-up, idle allocation, retries, useful outputs, and facility attribution. Uncertainty propagates through the integration model with shared meter, coefficient, and clock covariance retained.
Compare candidate and baseline only after both satisfy the same quality, risk, latency, and workload envelope. For paired run ,
where energies are J, is a qualified-event count, and is J/qualified event. Report absolute values, paired effect, coverage, and all failed or rejected runs. A software counter or narrow device boundary may rank systems differently from calibrated end-to-end measurement; the direction is an empirical question (C-536).
Falsification conditions
Reject the cross-layer composition as a distinct systems contribution if:
- a complete conventional metrology, statistics, and content-addressed provenance stack matches its coverage and stale-decision frontier;
- it improves results only by receiving extra sensors, calibration runs, compute, storage, or analyst time;
- dependencies are recorded but do not trigger correct downstream action;
- uncertainty intervals become narrower while empirical coverage worsens;
- shared dependencies are counted as independent evidence; or
- the metadata and review burden costs more than the errors or work it avoids.