Developers
DoT profiles declare how deep a proof goes — from structured claim through offline validity to on-log recognition and hybrid crypto. Verifiers report which rungs passed; they do not collapse everything into one badge.
The DoT ladder (0–6) orders assurance levels. DoT-4 (offline-valid) is the integrator milestone: Sigil S4 (Proven) reflects this state. DoT-5 and DoT-6 require additional attachments and remain staged on the public network.
The hosted verifier is explicit about what it enforces today. DoT-0 through DoT-4 pass when crypto_ok is true — rungs 0–3 are declaration-only at this layer. DoT-5 requires a valid onlog_proof attachment. DoT-6 requires a valid hybrid_sig attachment. DoT-PRIV profiles fail closed. Unknown or undeclared profiles fail closed. Interpret dotSet and sigil from verifier output — never from UI copy alone.
Non-ladder DoT profiles bind domain-specific obligations — robotics, media, datasets, agents, settlement, privacy. They extend the kernel without changing receipt bytes structure.
Binds browser or retrieval environment evidence such as page state, tool context, and visible artifacts.
Binds transformation chains, input roots, output roots, and stage identifiers for data or content workflows.
Binds robotic command, asset, safety, pre-state, post-state, and operating context claims.
Binds data provenance, dataset roots, training run evidence, model manifests, and weight commitments.
Binds responsible AI controls, retrieval provenance, safety cases, hazard context, and policy evidence.
Binds time witnesses, supply-chain or infrastructure attestations, settlement proof, and sealed privacy commitments.