System cards help organisations document AI risks, responsibilities, provenance, performance, security, limitations and review obligations. KYE™ goes one layer deeper: it generates the runtime authority decisions, state checks, signed Signal Bus™ events, Decision Maps™ and Evidence Packs™ that make assurance cards verifiable.
KYE Assurance Card Profile™ turns KYE™ runtime evidence into a living assurance record for AI agents, models, tools, workflows, connectors and delegated systems. KYE™ makes assurance executable.
Defence-grade AI assurance work (Alan Turing Institute / Accenture / UK MoD) makes the case directly: model cards are insufficient where models are integrated with platforms, where assumptions change and where multiple models interact. Agentic systems need more than model cards. They need authority cards, runtime decisions and evidence trails.
KYE Assurance Card Profile™ sits above the runtime KYE™ stack. It turns the operating-model journey into a living lifecycle record, automates review-cycle triggering against the authority graph, and enforces the human-involvement plan as a runtime policy gate — not a documentation requirement.
Each stage emits a signed event onto KYE Signal Bus™ and is recoverable from the audit ledger.
KYEAssuranceCard drafted; intended use, prohibited uses, owner, accountable entity declared.pilot. Operating-model adoption pack bound; runtime evidence begins flowing.controlled_production / production; cascade-revocation hooks armed.KYEAssuranceReviewCycle watches authority-graph + provenance + risk-state for triggers.incident instantiates a review without operator intervention.scope_change on capability / gate / commit-boundary updates.retention on data / evidence retention windows.KYEDecommissioningPlan orchestrates revoke · quarantine · rotate · archive · notify · remove.Every claim on a KYE Assurance Card™ resolves to a runtime artefact a third party can replay offline against a published JWKS.
KYE Assurance Card™ · preview
kye:user:finance_owner_001kye:org:acme_ltdinvoice.read, payment.prepare, supplier.notifypayment.execute, contract.sign, credential.rotatekye:authority-record:finance_agent_001payment_execute · external_sendpayment_executionentity_and_descendantsSix involvement types · nine lifecycle stages. Bypass attempts are denied at runtime and emit a signed kye.human_involvement.bypass_denied event.
Every dataset, model, tool, supplier, licence and hardware lineage referenced by an assurance card is bound as KYEProvenanceEvidence. Verification status: verified / partially_verified / unverified / failed. Verification failure emits a signed kye.provenance.verification_failed event onto Signal Bus™.
| Element | What is recorded | Verification methods |
|---|---|---|
| Models | id, version, supplier, licence, checksum | self_attested · third_party_attestation · signed_evidence · registry_check |
| Datasets | id, version, licence, checksum, data classes | same |
| Tools | id, version, supplier | same |
| Suppliers | id, verification flag, method | same |
| Licences | SPDX identifier or named licence | registry_check |
| Hardware | id, vendor, model, attestation ref | signed_evidence |
Front-end illustration only — no data leaves the page. Real implementations call POST /v1/assurance-review-cycles/{cycle_id}:trigger.
When does it fire?
On the cadence declared by scheduled_frequency (weekly / monthly / quarterly / annual).
Reviewer roles: ai_governance_lead. Evidence captured: reviewer_identity, decision, reason_code, timestamp, state_snapshot, decision_map.
When does it fire?
When the bound KYEEntityAuthorityRecord adds or removes a capability, or when the KYEAuthorityGate set changes membership.
Reviewer roles: ai_governance_lead + security_admin. Evidence captured: scope_diff, decision_map, state_snapshot.
When does it fire?
When an incident signal is recorded (kye.compromise.reported, kye.agency_drift.detected, etc.) for a descendant of the assurance-card subject.
Reviewer roles: security_admin + ai_governance_lead. Outcome options: approve / deny / quarantine / escalate. SLA: 240 minutes.
When does it fire?
When KYEProvenanceEvidence.models[*].version changes.
Reviewer roles: ai_governance_lead + data_steward. Evidence captured: model_diff, evaluation_refs, performance_metrics.
When does it fire?
When KYEProvenanceEvidence.suppliers[*].verified changes from true to false, or a new supplier is added.
Reviewer roles: procurement + security_admin. Evidence captured: supplier_diff, verification_method, signed_evidence.
When does it fire?
When a model / dataset / tool licence changes.
Reviewer roles: legal. Evidence captured: licence_diff, registry_check.
When does it fire?
When the data / evidence retention window approaches expiry.
Reviewer roles: data_steward + legal. Outcome options: archive / extend / delete / decommission.
When does it fire?
When the assurance card transitions to deprecated or revoked, or the bound KYEDecommissioningPlan is executed.
Off-boarding: revoke_authority → quarantine_credentials → rotate_keys → archive_evidence → notify_owner → notify_supplier → update_catalog → remove_from_runtime. Cascade scope: per cascade_revocation.scope.
assurance-card-profile.json — profile manifestassurance-card.json — living lifecycle assurance recordhuman-involvement-plan.json — KYE Human Involvement Plan™provenance-evidence.json — supply-chain + model / dataset / tool lineageassurance-review-cycle.json — scheduled + event-triggered reviewsdecommissioning-plan.json — retention + off-boarding + cascade revocationOpen under Apache 2.0
Commercial / patent track