skills.rest
apply-the
apply-theOFFICIAL
Explore all skills by this author →
GitHub

canon-inspect-evidence

Retrieve evidence bundles, invocation lineage, and runtime surfaces for a Canon run.

1|Updated Mar 26, 2026
Search Tags:#artifacts#evidence#run#inspection#canon#lineage#invocations
One-click install
npx skills add https://github.com/apply-the/canon --skill canon-inspect-evidence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: canon-inspect-evidence
Source: https://github.com/apply-the/canon/tree/main/.agents/skills/canon-inspect-evidence
Command: npx skills add https://github.com/apply-the/canon --skill canon-inspect-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect and validate the complete evidence context of a Canon run, including the evidence bundle, invocation lineage, and runtime surfaces, to support audits and troubleshooting.

Core Features & Use Cases

  • Retrieve the full evidence bundle and associated invocations for a given run.
  • Trace the generation and decision lineage to understand how artifacts were produced and linked.
  • Use cases include debugging failed runs, verifying evidence integrity, and preparing packets for review or publication.

Quick Start

Provide a RUN_ID to inspect and retrieve the evidence bundle and lineage for that run.

Frequently Asked Questions about canon-inspect-evidence

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

FAQPage Schema
How do I inspect the evidence bundle and lineage from a Canon run?▼

To inspect evidence and lineage from a Canon run, provide a RUN_ID to retrieve the full evidence bundle, invocation lineage, and runtime surfaces. This returns a concise inspection summary with actionable next steps for auditing provenance.

What is an invocation lineage and how does it trace artifact generation?▼

Invocation lineage traces how artifacts are produced and linked across invocations within a Canon run. Inspecting this lineage allows you to verify evidence integrity and understand the complete decision path from generation to final artifact.

How do I audit provenance and verify evidence integrity for a specific run?▼

Audit provenance and verify evidence integrity by inspecting the evidence bundle and invocation lineage for an existing Canon run. Providing the RUN_ID resolves the runtime surfaces and decision links needed for a complete provenance audit.

Can I debug a failed Canon run by tracing its decision lineage?▼

Yes, you can debug a failed Canon run by inspecting its evidence bundle and tracing the decision lineage. This process reveals how artifacts were produced and linked across invocations to help identify where the failure occurred.

What do I need to retrieve the evidence context for an existing Canon run?▼

To retrieve the evidence context for an existing Canon run, you need a RUN_ID or resolution to the latest run. This allows you to inspect the evidence bundle, invocation lineage, and runtime surfaces to support troubleshooting and review preparation.

Related Skills

Explore More Software Engineering Skills→
apply-theapply-the
1

canon-inspect-artifacts

Return Canon-backed artifact paths under .canon/artifacts/<RUN_ID>/ for a run.

Official
Intermediate
danielbaustindanielbaustin
4

architecture-fitness-function-author

Convert architecture findings into fitness-function candidates with validation commands.

Community
Intermediate
nrakownrakow
1

data-lineage

Trace data lineage across dbt sources, transformations, and reports.

Community
Advanced
bcmcpherbcmcpher

datalad-log

Trace DataLad run provenance by listing and inspecting recorded runs.

Community
Intermediate