Import SkillBundle

Paste a SkillBundle JSON to verify and store. Verify re-runs all six proof gates locally (content_hash, trace_completeness, no_hidden_capability, authority, redaction_verify, replay_fidelity). Bundles with overall verdict fail are inspected but not persisted.

Why re-verification is the point

A SkillBundle is not trustworthy because of where it came from. It is trustworthy because anyone holding the file can recompute the verdict — which is what this page does. Verification is pure and offline: no network call, no API key, no appeal to a server that says the bundle is fine.

What is checked: That the content hash still seals the bundle; that trace edges are contiguous and complete; that no capability was exercised without being declared; that every authorization present holds; that the declared redaction profile is idempotent on this trace; and that the trace replays to the same state hashes.
What a failure means: Each gate names its reason and the Invariant Arithmetic law it was derived from, so a fail tells you which claim broke rather than only that something did. A bundle that fails is still shown in full — it is just not written to the library.
Where bundles come from: Record produces them from sessions you already ran; Teach produces them from an interaction you drive here. The format is identical, and so is this check.