mine-provenancelisted

# Mine Provenance Make a portfolio honest by tying every claim to a ground-truth artifact — a commit, a file, a passing test — and by calling out anything the evidence says is derived rather than originated. Overclaiming is the real risk here: a portfolio that quietly presents a *forked* repo as *originated* is the failure mode this prevents. Two rules hold the whole skill together: - **Artifacts verify; transcripts only lead.** A claim becomes VERIFIED only when a commit, file, or test backs it. Session transcripts are conversation, not proof — use them to *find* work worth checking, never as a citation. - **Never argue; sort.** Do not dismiss or debate a claim in conversation. Put it in the right bucket and let the evidence speak. "Unproven" and "derived" are buckets, not verdicts on the user. ## Steps 1. **Locate the portfolio doc.** Use the path the user gives, or default to a `skills.md` / portfolio doc in the current repo. Read it and any provenance definitions it references (e.g. a `CONTEXT.md` defining "Built" vs "Modified"). This doc's prose is the user's — you audit and extend it, you never overwrite it. 2. **Extract the claims.** Pull out each discrete claim: every skill, accomplishment, or "this proves X" statement, with whatever provenance label it already carries. 3. **Verify each claim against artifacts only.** For each claim, hunt for a backing artifact and record the exact reference: - `git log --follow`, `git blame`, and commit hashes for authorshi