K08 · traceable Machine Intelligence knowledge infrastructure
Protocol Provenance and Truth Boundaries
Direct answer
Hashes, signatures, timestamps, receipts, and logs can strengthen integrity and provenance, but they do not transform a false or unauthorized claim into truth.
Authority and evidence boundary. K08 publishes governed research, synthetic reference traces, non-certifying workbooks, acquisition evaluation structures, offline planning records, and bounded protocol experiments. It does not prove historical authority, facility truth, compliance, certification, contract award, deployment, current operation, or authorization for external effects.
What each control can support
| Evidence | Supports | Does not independently prove |
|---|---|---|
| Hash | Byte identity relative to a recorded digest | Accuracy, truth, authority, legality, or safety |
| Digital signature | Key-controlled authorization of a payload | That the signer was correct, authorized for the real-world decision, or truthful |
| Timestamp | A bounded time assertion under the timestamp system | That the underlying event occurred exactly as described |
| Transparency log | Append-only publication and consistency evidence | Truth of logged content or legitimacy of the actor |
| Provenance graph | Declared derivation, revision, and attribution relationships | That every input was complete, unbiased, or factually correct |
K08 evidence rule
Integrity evidence protects the container and history of a claim. Epistemic evaluation still requires source quality, observation method, scope, contradiction handling, currentness, and competent review.