TEC Protocol · Draft 1.0

A public contract
for analytical evidence.

The standard separates what the registry can verify from what remains an analytical, accreditation, sampling, or regulatory judgment.

Public draft · implementations must not claim final conformance

Normative core

Six non-negotiable properties.

These properties define the minimum credible TEC. Extensions may add fields; they may not weaken provenance or erase history.

01
Permanent identity
A TECRID is opaque, globally unique, never reassigned, and remains resolvable after correction or revocation.
02
Issuer attribution
Every public record identifies an ICS-reviewed laboratory issuer and the scope under which it may issue.
03
Signed payload
Publication requires an Ed25519 signature that verifies against the issuer key reviewed by ICS.
04
Append-only versions
Corrections and revocations append a signed version; database triggers reject updates or deletion of prior version rows.
05
Structured evidence
Results preserve analytes, reported values, units, limits, methods, sample context, and timestamps as issued.
06
Interpretation boundary
A TEC proves attribution, integrity, and status—not representative sampling, regulatory compliance, or safety.

Trust model

01Issuer authorization

May this laboratory issue this type of evidence under its reviewed scope?

02Cryptographic integrity

Does the signature match the issuer key, and does the fingerprint match this exact version?

03Scientific relevance

Was the sampling, method, execution, and interpretation suitable for the decision being made?

Implementation status

Implemented: Permanent TECRID generation, public resolution, structured JSON, organization-scoped API keys, issuer application intake, Ed25519 issuance enforcement, independently verifiable public proof bundles, live fingerprint/signature checks, and append-only version records.
Requires ICS operation: Identity review, scope decisions, signing-key control verification, suspensions, appeals, and governance publication.
Not yet claimed: W3C Verifiable Credential conformance, regulatory recognition, universal LIMS interoperability, supplier declarations, custody linking, automated authenticity comparisons, or fitness for any safety decision.

Build against the draft