Decionis vs manual maker-checker
Keep the second-person control where it adds judgement. Bind that approval to the action that actually reaches execution.
Public sources checked . Our architectural assessment follows the scope of the sources below. Send a correction; accepted corrections update this date.
When is manual maker-checker the better choice?
- Action volume leaves time for meaningful human review.
- Your existing ERP approval is enforced at the execution boundary.
- Its records meet your evidence requirements.
- A second system would duplicate a control without improving it.
What changes at the execution boundary?
| Dimension | Decionis | manual maker-checker |
|---|---|---|
| Control boundary | One exact action, with authority re-evaluated immediately before commit. | Business Central documents approval requests, designated approvers and approval workflow state. Such workflows are real controls, not merely notification systems. |
| Evidence | Signed Decision Dossier; verify the covered artifacts with the appropriate public keys, without an account. | Inspect whether the approved record can change before commit, how authority is refreshed, and whether evidence remains independently checkable outside the workflow system. |
| Deployment responsibility | The integrating host must isolate credentials, prevent bypass and enforce the decision. | Evaluate the chosen deployment and its enforcement boundary; a product category is not evidence of a specific installation. |
| Procurement posture | Ed25519-signed Decision Dossiers · single-use execution grants. These pages compare engineering and architecture, not certifications; current audit status is on the Trust Center. | Obtain current assurance documents and check the service and deployment they cover. |
Decionis contract: enforce-and-bind, claim-before-commit and finalize. Signature validity is separate from execution eligibility and downstream effect confirmation.
Can these controls work together?
Use human review for exceptions and current policy for routine actions. An approval is evidence for re-evaluation; it must not silently authorize a changed action.
Check the evidence
Verify this yourself — no account, works offline
This preloaded dossier has real Ed25519 signatures over synthetic data from the public Agent-Safe corpus. Its test key is deliberately public. It demonstrates verification and tamper detection; it is not customer evidence, a production signature, or permission to execute.
Ready to check locally
npx -y @decionis/verify --file OwnedExecutionBound.json --jwks Jwks.json
After the page or files load, the signature checks need no network. Installing the CLI may require a connection. Valid signatures establish integrity relative to the selected key, not whether the original facts were true.
Sources and scope
- Business Central approval workflows · checked 2026-09-16
A capability not described in the cited public material may still exist. This is a technical comparison of documented controls, not a claim of exhaustive vendor testing.