Families
Decide and validate
Accepting, refusing, or flagging an inconsistency, according to rules you can write down and stand behind. This is the family where determinism is not a comfort but a requirement: a decision that changes between two identical calls is not a decision, and cannot be defended to anyone.
Do I accept this, and on what grounds?
1 entry
- Validate a form server-side RecommendedN0
Roadmap
This need is missing from the catalogue. Propose it, that is how it grows.
- Apply discount rules to a cart Propose this entry
- Check a company identification number Propose this entry
- Check a configuration before deployment Propose this entry
- Check a file is really the format claimed Propose this entry
- Check a password against a policy Propose this entry
- Check a product catalogue for inconsistencies Propose this entry
- Check an invoice against its purchase order Propose this entry
- Check bank details before a transfer Propose this entry
- Check that a contract contains the required clauses Propose this entry
- Check that a postal address is deliverable Propose this entry
- Check that a translation file is complete Propose this entry
- Decide when to retry a failed operation Propose this entry
- Decide whether a change needs human review Propose this entry
- Detect conflicts in a schedule Propose this entry
- Reconcile a bank statement with a ledger Propose this entry
- Validate a phone number and its country code Propose this entry
- Validate an API payload against its contract Propose this entry
- Validate an email address without sending a message Propose this entry
- Validate an imported file against its expected schema Propose this entry