Working patterns for proving business capabilities.
Each recipe demonstrates one focused verification technique using the canonical BRS verifier contract. Every recipe is independently executable, and approved recipes can run together and continuously under BRS-Core as part of 24/7 business capability monitoring.
Browse verifier recipes
Jump directly to a working business capability verifier recipe.
Use a recipe. Adapt the evidence.
These are not alternate verifier formats. They all use the same BRS contract. What changes is the business evidence each verifier gathers.
Verify a Remote File over SSH
Confirm that an expected business file exists and is readable on a remote system.
Verify a Scheduled File Is Fresh
Confirm that a scheduled business file exists and was produced recently enough to be trusted.
Verify a Business Result in a Database
Query an authoritative database and prove that a business condition is true—not merely that the database is reachable.
Reconcile File Contents Against Database Results
Compare a delivered report with its authoritative database source and verify that the business output agrees.
Verify a Client Can Log In
Use a real browser to prove that a client can authenticate and reach the expected business page.
One contract lets the verifiers run together.
Run any recipe directly while you build and test it. BRS-Core can then discover approved verifiers, schedule them independently, enforce their timeouts, record their results, and expose their signals for dashboards and alerting. A slow or failed verifier does not need to become a serial dependency for the others.