canonical-route-provenance-auditor

Audits AI measurement runs for canonical runtime paths and complete route provenance fields.

Updated Sep 24, 2025
One-click install
npx skills add https://github.com/chriso789/pitch-1 --skill canonical-route-provenance-auditor-chriso789
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: canonical-route-provenance-auditor
Source: https://github.com/chriso789/pitch-1/tree/main/.agents/skills/canonical-route-provenance-auditor
Command: npx skills add https://github.com/chriso789/pitch-1 --skill canonical-route-provenance-auditor-chriso789

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI measurement pipelines often accumulate multiple code paths that write to the same tables, making it impossible to tell which route created a row or whether a claimed pipeline phase actually executed. This Skill audits measurement runs to enforce a single canonical runtime path and requires full provenance stamping on every canonical row. ## Core Features & Use Cases - Canonical path enforcement: Verifies every run follows PullMeasurementsButton → useMeasurementJob.startJob → start-ai-measurement → autonomous-graph-solver → MeasurementReportDialog/render-measurement-pdf. - Provenance field validation: Checks that canonical rows carry created_by_function, created_by_component, solver_entrypoint, canonical_measurement_route, route_audit_version, and geometry_report_json.route_provenance. - Legacy route flagging: Blocks legacy routes from silently creating canonical-looking rows and requires route_warning = legacy_noncanonical_measurement_path. - Phase-execution honesty: Refuses to mark phases (3A, 3C, 3D, 3E) implemented without executed = true diagnostics or an explicit skipped_reason. - Use Case: Before merging a change to the measurement pipeline, run this audit to produce active and legacy route tables, canonical row proof, and a minimal migration plan. ## Quick Start Audit the current AI measurement pipeline and produce the active route table, legacy route table, and canonical row provenance proof before proposing any fixes.

Frequently Asked Questions about canonical-route-provenance-auditor

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

FAQPage Schema
How do I verify an AI measurement run used the canonical route?▼

Check that the run followed PullMeasurementsButton → useMeasurementJob.startJob → start-ai-measurement → autonomous-graph-solver → MeasurementReportDialog/render-measurement-pdf. The resulting row must also carry canonical_measurement_route = true and full provenance fields.

What provenance fields must a canonical measurement row include?▼

A canonical row must include created_by_function, created_by_component, solver_entrypoint, canonical_measurement_route set to true, route_audit_version, report_renderer_version if rendered, and geometry_report_json.route_provenance.

How should legacy measurement routes be handled?▼

Legacy routes may not create canonical-looking rows. They must stamp canonical_measurement_route = false, record the actual legacy function name in created_by_function, and set geometry_report_json.route_warning to legacy_noncanonical_measurement_path.

When can a pipeline phase be marked as implemented?▼

Only when the module file exists, is imported at the call site, the call site is reached at runtime, and diagnostics persist executed = true or an explicit skipped_reason. Code existing alone is not proof of shipment.

What must the debug-measurement-runtime endpoint prove?▼

It must identify which route created a row, which solver ran, which renderer rendered it, the status of phases 3.5/3C/3D/3E, and the customer gate state including customer_report_ready and block_customer_report_reason.