Critical Infrastructure
When the consequence is physical
Software that moves physical things is held to a different standard.
Operators of essential services are already expected to document how their systems change. AI coding agents introduce a contributor that most change records have no way to name, in exactly the environments where an unexplained change matters most.
Nobody asks how AI-written code entered a repository until something goes wrong or somebody audits it — and by then the record either exists or it does not. PromptWake is cheap to run before you need it and impossible to reconstruct afterwards.
Questions this sector asks
Does it work in an isolated network?
Yes. Local capture has no outbound dependency and the whole system can be self-hosted.
Our vendors write much of this code. Can we require a record?
That is the more interesting use. The same report a supplier runs internally can be requested at delivery.
What happens during an incident?
You can ask which prompts produced the code in the file involved, and when. That is usually faster than reconstructing it from commit messages.
Incidents are investigated on records, not recollections.
Recording costs almost nothing while nothing is wrong.