Boiler Framework / Approval & controlled execution
Turn sensitive changes into policy-driven review, accountable decisions and verified application. Connect the requested change, its reviewers and its execution result in one traceable record.
Choose automatic approval, human review or denial by policy.
Combine mandatory reviewers with quorum rules.
Track approval and actual application separately.
Boiler Approval
Submit the proposed version and its immutable content reference.
Evaluate risk rules and resolve the mandatory reviewers and quorum.
Collect authorised decisions before the deadline, with a visible timeline.
Ask the application to apply the exact approved revision.
Reconcile the receipt and retain the outcome with its audit evidence.
Inside the product
Evaluate change attributes with Boiler Rule Engine. Amount, risk or environment can determine automatic approval, rejection or review. Missing or invalid policy evidence blocks the decision instead of granting permission.
Require named review responsibilities alongside a fixed number, majority or all eligible reviewers. Bind decisions to verified identities and the exact tenant, product and environment.
Freeze the policy snapshot and change reference with each request revision. A content digest ties the review to the proposed change. Later edits cannot silently inherit an earlier approval.
Find requests awaiting your review, inspect detail and timeline, then approve or reject within your authority. Withdrawal and policy-derived deadlines close obsolete requests; decisions at or after expiry are refused.
After approval, dispatch a bounded apply command to the connected application. Match its result to the exact request, revision and execution token. Show successful application, failure and uncertain outcome as distinct states.
Persist decisions, work and outgoing events together. Coordinate workers with leases, use bounded retries and reconcile uncertain results. Operators can inspect waiting, failed and parked work and replay authorised events with an audit record.
Author and validate a complete policy draft, seal an immutable version and publish against the expected current revision. Separate administration, review and application permissions instead of allowing clients to declare their own authority.
Use Java contracts or authenticated HTTP consumers to submit changes and return execution evidence. Communication-policy and Informer template/provider changes illustrate concrete integration points. RabbitMQ and Kafka adapters publish events; the receiving application still owns its business transaction.
Use dedicated screens for the review inbox, request lookup, policy catalogue, draft editing, release and audit. Consumer administration and operational views show integration bindings and capacity. Access follows the signed-in actor’s capabilities.
Approval provides one review stage with mandatory and quorum requirements. Applications integrate their own atomic commit and result reconciliation. Approval does not itself execute arbitrary business processes or guarantee the outcome of downstream operations.
