mif-provenancelisted

Stamp witnessed provenance into a MIF document's frontmatter from the hook-observed session ledger, verify an existing provenance block against it, or check whether capture is actually active for the current session — hook-observed facts only (agent, agentVersion, session activity URN), never model-asserted. Use after authoring a MIF document in a session with capture enabled, to make its provenance witnessed rather than asserted; use verify to detect drift between a document's provenance block and what the ledger actually observed; use status when you just enabled capture or updated this plugin and want to confirm hooks are actually wired before trusting anything gets stamped. Anti-trigger; for writing the rest of the frontmatter use mif-frontmatter (asserted provenance from drafting context), and for schema/level/round-trip conformance use mif-validate.
modeled-information-format/mif-docs-plugin · ★ 0 · API & Backend · score 71

Install: claude install-skill modeled-information-format/mif-docs-plugin

# mif-provenance The suite's **witnessed** provenance helper — the fifth authoring helper, closing the gap the other four cannot: `mif-frontmatter` writes provenance *asserted* from drafting context, and `mif-validate` passes any schema-valid block regardless of whether the named agent ever touched the document. This skill stamps only what the plugin's capture hooks actually observed, and the model being described is never the source of the facts describing it. ## What it does - **`stamp <file>`** — writes ONLY ledger-witnessed fields into the document's frontmatter `provenance` block: `agent`, `agentVersion` (only when witnessed; omitted, never invented) and `wasGeneratedBy` (the session activity URN `urn:mif:activity:claude-code-session:<id>`), plus `trustLevel` from fixed policy. It modifies only the `provenance` block and the `modified` timestamp (set to the latest witnessed touch, so stamping is byte-idempotent), preserves every unowned provenance field, and **declines** when the ledger records no touch of the document by the selected session — provenance naming a session that did not touch the document is the defect class this whole helper exists to prevent. - **`verify <file>`** — deterministically re-derives the expected block from the ledger and reports **match** or per-field **drift**. It never restamps; reconciliation is an explicit `stamp`. No LLM judgment is in the path (the `mif-validate` precedent): identical document + ledger + confi