Compliance Machine (Functional Requirements and Quality Constraints)

Trevor has usefully stated some of the general quality constraints for the compliance machine. Easy installation and configuration, low/remote management, non-intrusive, and so on.

What we now need is a clear summary of what the machine will actually do. Trevor proposes to build one and show us. In the meantime, perhaps the rest of us can discuss what we are hoping that Trevor will be able to demonstrate. If it's a proof of concept, what exactly is the concept?

I'm particularly keen to find some organizations to pilot Trevor's machine, and the better we understand what a general compliance machine could/should do, the easier it will be to present the pilot properly.