Prove and submit the overdue priority configuration
Freeze the configuration with the overdue priority rule, run ToolCustody's complete proof of every expected result and submit that exact release for independent review.
For authors
Freeze the configuration with the overdue priority rule, run ToolCustody's complete proof of every expected result and submit that exact release for independent review.
Read these instructions on any device. Watch or practise a chapter on a desktop or laptop, with a desktop or mobile application layout. Demonstrations use sample data and simulated scanners.
Proof and submission
- Load the current ToolCustody draft
Load the current ToolCustody draft
Load the configuration with the overdue priority rule and its reviewed expected results.
- Freeze the release candidate
Freeze the release candidate
Freeze the complete configuration with its reviewed expected results. The candidate holds exactly the rule saved from the plain English proposal.
- Verify every expected result
Verify every expected result
Run ToolCustody’s complete check of every expected result. ToolCustody keeps the proof with this exact candidate.
- Read the proof result
Read the proof result
Read the proof. All six examples give the expected result, and the overdue priority rule is reached by an example.
- Check the overdue results
Check the overdue results
Check the overdue examples: 119 minutes stays at normal priority by default, and 120 and 300 minutes get high priority from the new rule.
- Assemble the exact release proposal
Assemble the exact release proposal
Keep the complete configuration, its independent expected results and the proof together in one exact release proposal.
- Request independent release review
Request independent release review
Submit this exact configuration for a separate person to review. This does not activate it.
The release is saved for separate review. It has not been activated, and no tool is issued or returned.