Beyond the
accepted.

Verify the artifact. Enforce the boundary.

Independent research. Tools to verify AI, enforce control, and make knowledge usable.

01 / The system

Reads the bytes.
Enforces the verdict.

Fig. 01Registry → Tessera → verdict → promotion → admission webhook → workload. Rescans close the loop.
02 / The work

Five programs.
All open.

Tessera / v1.4.2 / Go

Read the artifact.

Bill of materials from the bytes. Offline. Zero dependencies.

Repository →
Cupel / v0.9.0 / Go

Enforce the boundary.

Admission enforcement for model registries on Kubernetes.

Repository →
hf-survey / dataset / Go

Measure the drift.

666 models measured. 11.4% contradict their own config.

Dataset →
Octavo / v0.24.1 / TypeScript / AGPL-3.0

Make knowledge usable.

Documentation that reads like a book. One container, one file.

Repository →
Itemize / v0.5.0 / Python

Audit the bill.

A medical bill, checked against federal data.

Repository →
Research notes

Published findings.

Findings, written up as they land.

Read the notes →
03 / The evidence

A signed document
can still be wrong.

11.4%
of 666 public Hugging Face models declare a precision their tensors do not carry.
666 models analysed Consistent — 457 models (68.6%) No precision declared — 133 models (20%) Contradicts its tensors — 76 models (11.4%) 457 consistent 133 no precision 76 contradict of the 76 Quantization drift — 49 of 76 (64%) Other mismatch — 27 of 76 49 quantized to 4/6/8-bit, config still says bfloat16 — 64% 27 other
consistentno precision declaredcontradicts tensors
04 / Real systems

What was not read
is part of the verdict.

Cupel console: a model scan with findings by severity, coverage, and verdict Tessera Studio holding a model in quarantine with its findings
Fig. 02Cupel scan · Tessera Studio quarantine. Unretouched.
05 / Open questions

Lines the code draws.
Questions it hasn't closed.

  1. Where does the file end and the behaviour begin?

    — tessera/docs/design.md

  2. How do you score restraint?

    — hf-survey/FINDINGS.md

  3. Can a bill of materials stay true?

    Tessera re-derives every claim from the bytes months later, including documents other tools produced. A signed document that has drifted from its bytes is a cryptographically impeccable lie. — tessera README