Evidence frozen at capture
What they knew at the time — value, source definition, freshness, and provenance snapshotted the moment evidence informs a decision. Not a screenshot, not a stale export.
Boss Loops is open core — inspect and self-host the Apache-2.0 engine, or run governed decisions on Boss Loops Cloud.
Explore Boss Loops Cloud →Loading
The Decision Record
One record holds the situation, the evidence — frozen at the moment it was used, from governed sources, not a link that may have changed since — the policies that applied, the people and AI that participated, the outcome that followed, and the learning it produced. GRC holds policy. BI holds metrics. Workflow holds steps. Chat holds the AI's reasoning until the window closes. None of them holds all of it, linked, as one auditable artifact.
In Boss Loops this isn't a convention a well-behaved workflow follows — it's enforced by the engine. A consequential decision cannot commit without frozen evidence, recorded provenance, and a record reconstructable from its primary objects — immutable, hashable, replayable by construction, not by discipline. Approvals are captured on that record with the evidence presented, under the approver's own name.
What they knew at the time — value, source definition, freshness, and provenance snapshotted the moment evidence informs a decision. Not a screenshot, not a stale export.
Approvers sign under their own name, and the sign-off is captured with the evidence presented. Human, automation, and AI actors share one attribution model.
Who decided, on what evidence, under which policy, and whether it worked — retrieved as a record, not reconstructed across four systems.