How it runs when the products are in place.
Fictional sample. A fictional mid-sized asset manager on Microsoft 365. Nothing here describes a real customer.
-
1
Every agent gets a policy before it gets a user
Westbrook writes its rules in Simple Council: which systems an agent may read, which data classes need a person, which actions are never automatic. Council's policy engine applies them and writes every decision to a hash-chained evidence ledger, so a decision made in March reads the same in September.
-
2
The examiner asks for the record, not the policy
The compliance lead exports the evidence pack: the agents, the policies in force, the approvals and who gave them, the refusals. The pack is built from the ledger, not written for the visit. The blueprints run from ISO 42001 to CMMC Level 2, so the mapping to the framework the examiner names is already there.
-
3
Operations run to the same rules
The client-onboarding project runs in SimpleOS Delivery from the signed engagement letter, and time against it is captured and approved in Simple Time before it is billed. The same seam, a person approving before anything leaves, holds on the operations side as on the governance side.
Every sentence above describes what the named products do today, in the words of each product's own "what works today" list. What a product does not do yet is on that product's page, with the date it was checked.