provenance

Audit hash-chained decision logs and trace evidence behind yeaboi's automated signals.

4|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/yeaboi-ai/yeaboi.ai --skill provenance-yeaboi-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provenance
Source: https://github.com/yeaboi-ai/yeaboi.ai/tree/main/claude-plugin/yeaboi/skills/provenance
Command: npx skills add https://github.com/yeaboi-ai/yeaboi.ai --skill provenance-yeaboi-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an automated tool flags a blocker, nudges a practice, or adjusts a confidence score, teams need to know why — and to trust that the record of that decision has not been altered. This Skill verifies the integrity of yeaboi's tamper-evident, hash-chained decision log and traces the evidence behind any recorded signal. ## Core Features & Use Cases - Chain integrity verification: Run a provenance audit over a configurable window (1–365 days) to confirm every record's checksum, link, and sequence number, with explicit break types (checksum_mismatch, chain_break, truncated_tail) when tampering is detected. - Decision inspection: List recent decisions and counts by record type, including practice signals, blocker signals, confidence adjustments, conflict cards, and performance review records. - Evidence tracing: Follow a specific decision's trail — including retractions and the records behind each piece of evidence — up to a configurable depth. - Use Case: A manager preparing for a compliance review asks why an engineer was flagged for WIP sprawl last month; the Skill verifies the chain is intact, then traces the exact rule, date, and evidence keys behind that flag. ## Quick Start Ask the assistant to audit the provenance chain for the last 30 days and trace why a specific signal was raised.

Frequently Asked Questions about provenance

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

FAQPage Schema
How do I audit an automated decision log for tampering?

Run a provenance audit over a time window to verify every record's checksum, chain link, and sequence number. A chain_valid result of true means the whole chain verified; false returns a breaks list identifying checksum mismatches, chain breaks, or truncated tails.

How do I trace why an AI tool made a specific decision?

Use a provenance trace with the entity id from the audit output, such as a standup practice signal id. The trace returns the entity's own records including retractions, plus the latest record behind each piece of evidence, up to a configurable depth.

What does a hash-chained audit log actually prove?

It proves that stored records were not edited, deleted, or reordered after the fact, since any change breaks the chain verifiably. It cannot defend against an adversary who rewrites both the rows and the head anchor together, since the chain is a local file with no external anchor.

Why is the provenance chain empty on a fresh install?

An empty chain is normal before any workflow runs. Decisions start recording when a standup or performance workflow executes, so the audit returns a warning rather than an error until then.

Does the decision log contain private conversation or ticket content?

No. Records carry decision ids, rule and model names, evidence keys, and counts only — never transcript content, ticket bodies, or one-on-one notes. The log shows which rules fired, when, and on what evidence keys.