Self-report and attestation
State the evidence source before discussing confidence in a runtime claim.
Research note · November 14, 2026Research question
How does a worker’s assertion differ from independently appraised attestation evidence?
Method
- Draw the reporting boundary: which process observes the state, which process sends the report and which party evaluates it. Identify shared privileges that could let one compromise affect both observation and reporting.
- For a self-report fixture, explicitly assume that a compromised worker can lie. Test the collector’s handling of internally consistent but false fixture claims without labeling that test an attestation evaluation.
- If evaluating an attestation system separately, document the attester, verifier, reference values and relying-party policy. Preserve the evidence format and appraisal result rather than reusing an unqualified verified label.
Records to retain
- Observer and reporter identities
- Trust-boundary diagram
- Evidence format and appraisal policy
- Assumptions about compromised components
Source basis
RFC 9334 defines distinct roles and conceptual messages for remote attestation. A conventional worker report does not become attestation merely because it is signed or transported over an authenticated connection.
Interpretation & limits
This is a comparison of evidence models. Vraelis Contour’s published reference remains worker self-report; this note does not announce a hardware-attestation integration.
Next experiments
- Review every verified label against its actual evidence source.
- Document which host compromises remain outside the reporting model.
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.