Integrate provenance into a useful artifact

Start with a bounded record that can retain its meaning outside your application.

The smallest useful record

Give the artifact a stable identity, a version, an author or issuer, an explicit claim, source references, known limitations, and a canonical return URL. If attested, include the actual receipt and verification procedure. Otherwise keep the attestation field empty.

One record, several representations

Generate human-readable HTML, Markdown, and JSON from the same versioned source. Carry the same claim scope, attribution, status, and limitations in each. Representation changes must not create stronger claims for machines than for people.

Public disclosure is a choice

Publish only material authorized for public release. A private family record, health history, or proprietary research corpus must not become enumerable through a discovery catalog. Even digests of predictable sensitive values can disclose information through guessing.

Bounded retrieval

A public explanatory object may be broadly retrievable while underlying private evidence remains access-controlled. Authentication, authorization, quotas, and selective disclosure belong at the evidence boundary. A robots policy is not an access-control mechanism.

Start with these working surfaces

The guide catalog provides versioned JSON and Markdown documents. The integrity checker provides local SHA-256 comparison. Public receipt issuance, hosted signature verification, MCP, and A2A services are not advertised as available. Contact Miskir to discuss an integration.

Cite this guide

Miskir. Integrate provenance into a useful artifact. Version 2026-10-15.1. https://miskir.com/guides/integration/

This editorial guide is not a signed receipt.