Hugging Face — capability
What the model is and what it can do: weights, evals, model card, lineage. This is where you build and compare.
Your model is on Hugging Face. Its authority isn't.
Hugging Face shows the world what your model can do. It does not tell a bank, a hospital, or a regulator whether they may use it. KYE Protocol™ answers that — and proves it.
You keep building on the Hub. KYE Protocol™ binds your model to the obligations its use carries, so a regulated buyer can adopt it without guessing.
The problem: capability is solved, authority is not
The Hub answers "what can this model do?" brilliantly — weights, benchmarks, model cards, datasets. It leaves the questions that block regulated adoption unanswered.
- May you use this model in this jurisdiction, for this purpose, as this entity?
- Which obligations apply when you deploy it — EU AI Act, GDPR, DORA, SOC 2?
- Can you prove all of that to an auditor months later, from public artifacts?
The split that matters
Capability and authority are different questions. The Hub owns one. KYE Protocol™ owns the other. You need both before a regulated team can ship.
KYE Protocol™ — authority
Whether you may use it here, under which obligations, with what evidence. This is what a regulated buyer asks for before adoption.
The solution: an AI Bill of Materials + a governance posture
KYE Protocol™ binds your model to an AI-BOM — the dataset, weights, and model provenance — and maps its use to the obligations each framework carries.
- Chain of Authority — KYE Protocol™ records which datasets trained which weights composed which model, under which licence.
- Obligation mapping — KYE Protocol™ maps the model's use to the obligations it carries, drawn from one canonical registry.
- Replay-Proof™ evidence — every decision seals into an evidence pack an auditor can re-verify from public keys.
- Honest scope — KYE Protocol™ certifies provenance and governance posture, not capability, safety, or fairness.
Dataset
provenance · licence
Weights
training lineage
Model
Hub artifact
KYE™ binding
AI-BOM · authority
Obligation map
EU AI Act · GDPR · DORA · SOC 2
Evidence Pack™
Replay-Proof™ · public keys
The Chain of Authority: dataset → weights → model, bound by KYE Protocol™ to the obligations its use carries and a signed Evidence Pack™ an auditor can re-verify from public keys alone.
Who this is for
Three audiences feel this immediately. You are probably one of them.
- Model & dataset publishers — you want a governed signal that makes your artifact adoptable by regulated buyers.
- Regulated adopters in finance, health, and government — you must prove governance, not assert it.
- Builders of agentic systems — you need an authority check at the action boundary, not a post-hoc audit.
How you get governed
Governance is a short path, and you climb it one posture at a time.
Declare
posture AI-BOM captured
Assess
posture obligations mapped
Certify
posture signed evidence pack
Declare
Identify the model and capture its AI-BOM — provenance and licence. Your model is now declared.
Assess
KYE Protocol™ maps the obligations your use carries and reviews your evidence. Your model is now assessed.
Certify
A signed evidence pack backs framework coverage. Your model is now certified — and adoptable.
Canonical KYE™ surfaces referenced on this page: Evidence Pack™ · KYE Protocol™.