Lindsey Provenance Discipline
Open-source · Python · MIT licensed
An LLM will happily write the code and the documentation that says the code works. This is the discipline that keeps those two honest.
What it is
A small set of practices that, together, let one person keep AI-collaborative work auditable at scale. It doesn't limit what you build. It gives you a structured place where the gap between what an artifact actually is and what you wish it were shows up early — early enough to close by doing the missing work, instead of quietly absorbing it into a claim.
The reference implementation is a Python package. The companion arXiv preprint is in draft.
Install
Standard library + numpy only. No deep-ML dependencies. Python 3.10+.
The four practices
Tap a practice to see how it works.
idea → planned → implemented → simulated → artifact-generated → physically-validated — and the machine is monotonic. You can't describe something in artifact-generated as physically validated. The words have to match the state..docx, .eml, whiteboard photos, handwritten notes. A seven-phase pipeline ingests, classifies, and binds them to the project's evidence surface before any code is written — so intent doesn't get lost in a long thread.Resources
- → github.com/bradmlindsey/lindsey-provenance — source, license, docs
- → Verification procedure — validate the Ed25519 retro-signed ledger yourself
- → arXiv preprint — Phase-Chain Freeze and Closed-Form Re-Route. Forthcoming.
Author
Built by Brad M. Lindsey — independent engineer, Master Electrician, Master HVAC Technician — across April 4 to May 27, 2026, in roughly 280,000 lines of LLM-collaborative Python. ORCID 0009-0004-6392-2720.