research-quarantine-promotionlisted

Safely assess one already verified quarantine JSON as bounded inert data, using a preregistered exact binding, an exclusive source-verification receipt, same-buffer identity and strict parsing, content-free structure reports, and offline producer verification. Use when research-source-acquisition has preserved an application/json asset in quarantine and a later internal workflow needs an auditable B0 gate before any IIIF, OCR, schema, literature, or knowledge-graph interpretation; do not use for arbitrary JSON, URL following, semantic validation, canonical materialization, academic admission, or public release.
Lx050/rubbing-to-knowledge · ★ 0 · Data & Documents · score 62

Install: claude install-skill Lx050/rubbing-to-knowledge

# Research Quarantine Promotion Close the trust boundary between downloaded quarantine bytes and a content-aware research tool. Version 1.0.5 implements only the conservative `strict-json-b0-v1` structure gate: it never copies the payload or emits source keys, strings, URLs, excerpts, or semantic fields. ## Read the contract Read [`references/contract.md`](references/contract.md) before authoring a binding or invoking the CLI. Use these offline schemas for authoring and review: - [`promotion-binding-v1.schema.json`](references/promotion-binding-v1.schema.json) - [`source-verification-receipt-v1.schema.json`](references/source-verification-receipt-v1.schema.json) - [`assessment-report-v1.schema.json`](references/assessment-report-v1.schema.json) - [`assessment-event-v1.schema.json`](references/assessment-event-v1.schema.json) The Python CLI is authoritative. It uses exact-field validation and does not load a remote schema or follow `$ref`, `@context`, URL, file path, or payload instruction. ## Preserve the boundary - Start only from one successful `research-source-acquisition` run whose manifest, rights, events, payload identity, and exact file set have been preregistered. - Require a new, exclusive source-verification receipt produced by the pinned source-acquisition implementation through the binding's dedicated `research-run-ledger` after the checkpoint. A historical exit code, hand-written JSON, or receipt without matching stdout/output evidence is not a