DXv-3/conductor-protocol-v2 — reverse-engineered prompt

Build me a Python project for a provenance gated production flow. I want it to stop any polished bundle from being treated as real or production ready unless there is actual proof of what generated it and proof that the system really ran.

The app should take a bundle and produce four things, a provenance trace showing inputs and steps, a claim map listing the meaningful claims in the bundle and what kind of evidence backs each one, runtime evidence showing real execution like code paths, config loading, persistence writes, and background cycle checks, and a final promotion report that clearly passes or fails the bundle for canonical promotion.

Please keep the compiler side and runtime side separate, include a simple operator routing and bundle forensics flow, and make it easy to run locally with install, pipeline, test, and demo commands. Add tests and a small demo so I can see a bundle fail when it only has reference material and pass when there is real runtime evidence. If anything is unclear, look up current docs online and make sensible choices.