Decionis
How are policies managed and versioned when they change? #2
|
Two questions that usually come together once the model clicks:
|
Replies: 1 comment
|
Policies are managed by the organizations themselves — the owners of the rules stay the owners. On staying up to date: when a policy changes, we don't update it in place — we create a new version, the way GitHub treats commits and pull requests. The engine automatically knows which version is current at decision time, and the Decision Dossier states exactly which version each decision was evaluated against. An auditor can always trace a decision back to the precise policy text that produced it. On who writes them: policies differ by vertical but share a common structure. That's why we ship Policy Packs — starter sets per vertical that an organization can bootstrap from and improve on, rather than starting from a blank page. Related: What is Decionis, in plain terms? · Where Decionis sits in the stack Have a different architecture or integration question? Start a new discussion — we answer publicly whenever we can. |
Policies are managed by the organizations themselves — the owners of the rules stay the owners.
On staying up to date: when a policy changes, we don't update it in place — we create a new version, the way GitHub treats commits and pull requests. The engine automatically knows which version is current at decision time, and the Decision Dossier states exactly which version each decision was evaluated against. An auditor can always trace a decision back to the precise policy text that produced it.
On who writes them: policies differ by vertical but share a common structure. That's why we ship Policy Packs — starter sets per vertical that an organization can bootstrap from and improve on, rat…