Sample report · EMET · witness surface

A witness is not an authority.

EMET is the witness anchor in the proof-surface stack. It checks whether bytes and presented views still match what they claim to represent, then emits a restrained verdict instead of asking for trust.

Surface

Field	Value
Repo	`HarperZ9/emet`
Surface class	`S:witness-tool`
Review mode	Public README and repo presentation surface
Access	No credentials, private files, or protected payloads

Role

EMET is the witness point in the release-readiness stack:

source bytes -> presented view -> witness verdict -> reviewer handoff

It records a comparison. It does not become the authority.

Evidence present

Evidence	Status
Public README	Present
Conformance badge	Present
Python reference implementation	Present
Rust second implementation	Present
Node.js third implementation	Present
Language-agnostic conformance suite	Present
Threat model, spec, security docs	Present
Claim boundary	Strong: independent different-author implementation is not yet met

What should stay prominent

EMET reports facts.
EMET does not say TRUSTED.
EMET does not decide whether a model is safe.
EMET does not edit, sign, or block anything.
EMET runs outside what it audits.

Gap before stronger claims

The public repo already has same-author Python, Rust, and Node.js implementations agreeing on public conformance vectors. The stronger gate is still independent different-author re-derivability.

Proof-surface verdict

Category	Status
Legibility	Strong for technical reviewers
Bounded claim	Strong
Evidence visibility	Strong
Buyer usefulness	High for diligence, AI oversight, and release-readiness narrative
Overclaim risk	Low if the no-TRUSTED boundary remains prominent
Next action	Recruit or record an independent implementation