Missing reports are not matches
Make absence of evidence visible without assigning an invented machine state.
Research note · November 14, 2026Research question
What should an operator see when a machine has no usable report?
Method
- Create three controlled cases: a matching report, a differing report and no report. Confirm that the third is not counted in either of the first two groups.
- Add a case with a previously matching report followed by silence. Display the latest known identity with its age, while marking current availability separately.
- Exercise connection failure, rejected authentication and malformed payloads as distinct collection outcomes. Retain the diagnostic information without claiming it reveals what the machine actually loaded.
Records to retain
- Machine identifier
- Latest accepted report
- Collection errors and times
- Counts by evidence state
Source basis
The RATS architecture separates evidence generation, appraisal and relying-party decisions. A missing input cannot be appraised as if it were successful evidence. The same discipline applies to ordinary runtime reports without implying attestation.
Interpretation & limits
Silence does not establish compromise or an operational fault. This method concerns evidence presentation, not diagnosis of every possible network or host failure.
Next experiments
- Test summary counts with only unreported machines.
- Review stale-report wording with an operator before selecting escalation rules.
References
Technical reference
Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.