Build and run your first business capability verifier.
Download a real W3Patterns business capability verifier, run it yourself, inspect the evidence, and use the included AI guidance and canonical skeleton to build a verifier around something your own business depends on.
Infrastructure can be healthy while the business is not.
A server can be up while customers cannot log in. An application can be running while payments fail. A scheduled job can complete while the expected file never arrives. Business verification asks whether the capability people depend on actually produced the expected outcome.
Run a real verifier
The included Public API verifier is a working BRS reference verifier. It checks the published Customer Care capability—not merely whether an HTTP server answered.
- Runs independently from the command line
- Produces structured PASS/FAIL evidence
- Uses Node.js built-in capabilities
- No BRS-Core, Prometheus, Grafana, or systemd required
Then build one for your business
The kit includes the canonical verifier skeleton plus practical AI prompts for turning a business requirement into observable evidence and verification steps.
- Start with what must be true for the business
- Identify evidence that proves the outcome
- Use AI to implement the verifier
- Review and test the proof before trusting it
A small kit with everything needed to understand the pattern.
Verifier Starter Guide
A concise introduction to business verification, standalone execution, structured evidence, the canonical verifier contract, AI-assisted verifier creation, review, and CI/CD use.
Working Public API verifier
Run a real reference verifier immediately against the public W3Patterns reference endpoint.
Canonical skeleton
Use the same independently executable pattern BRS verifiers follow when creating your own business checks.
AI creation and review guidance
Turn business knowledge into executable verification without making AI the authority on what your business outcome means.
Built a verifier worth keeping?
The verifier you build does not require BRS-Core. Run it manually, from shell scripts, in CI/CD, or as a deployment smoke test.
BRS-Core becomes useful when you want to operate approved verifiers continuously.
What BRS-Core adds
- Discovers approved verifier entry files
- Schedules and isolates verifier executions
- Stores the latest structured result
- Exports results through Prometheus metrics and a read-only JSON API
The same verifier can travel with your deployment process.
When its target is available, an independently executable verifier can serve as a release gate, post-deployment business smoke test, or manual diagnostic. BRS-Core then keeps the appropriate verification running continuously.
What are you verifying?
Run the sample. Then use the skeleton and AI guidance to build a verifier around something your own business depends on.