provenance-engine

Name: provenance-engine
Availability: InStock
Author: Justin

Generate traceable citations and source registries for OCR and transcript outputs.

Updated Aug 27, 2026

Search Tags:#audit #provenance #citations #transcription #OCR #traceability

Ready to run

npx skills add https://github.com/JustinChaney2023/orate --skill provenance-engine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: provenance-engine
Source: https://github.com/JustinChaney2023/orate/tree/main/roles/provenance-engine
Command: npx skills add https://github.com/JustinChaney2023/orate --skill provenance-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Make every extracted value traceable to concrete source evidence (transcript segments and OCR regions). Enable auditors and staff to answer: “Where did this come from?” quickly and reliably.

Core Features & Use Cases

Stable IDs: Source spans must have stable identifiers that survive UI rendering, exports, and reprocessing (when possible).
Minimal ambiguity: A citation should point to a specific segment/region, not an entire document.
Enforceability: The system must be able to reject outputs that lack required citations.
Outputs: Generates source_index.json, citations.json, citation_validation_report.json, and UI highlight payloads (span -> offsets/bbox mapping).

Quick Start

Run the provenance-engine to generate traceable citations for your transcripts and OCR outputs. Provide transcript.json and ocr_output.json as inputs, with optional pasted_text that is chunked into spans.

Frequently Asked Questions about provenance-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make OCR and transcription outputs traceable to specific source evidence?▼

Trace extracted values by enforcing stable span IDs and validating citations that point to specific transcript segments or OCR regions. The system rejects outputs lacking required citations and generates exportable registries like citations.json.

What is citation validation in audit and compliance workflows?▼

Citation validation is the process of ensuring every extracted value points to concrete source evidence. It generates a citation_validation_report.json and rejects outputs lacking required citations to maintain audit traceability.

How do I generate a source index for transcript and OCR data?▼

Generate a source_index.json by processing transcript.json and ocr_output.json inputs. The system assigns stable identifiers to source spans that survive UI rendering, exports, and reprocessing.

Can I use pasted text as input for citation tracking?▼

Pasted text is supported as an optional input that gets chunked into spans for citation tracking. It works alongside transcript.json and ocr_output.json to create traceable citations and UI highlight payloads.

How does traceability handle UI highlights and offset mapping?▼

Traceability for UI highlights uses span-to-offset and bbox mapping payloads to render specific source regions. This ensures citations point to precise OCR regions or transcript segments rather than entire documents.

Why does my compliance workflow reject outputs lacking citations?▼

Compliance workflows enforce traceability by rejecting outputs without required citations. This ensures every extracted value is traceable to concrete source evidence and generates a validation report.