What Can Be Verified?
W3Patterns verifies the business capabilities an organization depends on and the systems those capabilities rely on. The goal is not to replace infrastructure observability. The goal is to determine whether critical business capabilities are functioning as expected.
A framework for verifying what the business depends on.
W3Patterns is a business reliability verification framework, not simply a web monitoring tool. It verifies business capabilities and the dependencies that support them to determine whether the business can actually do what it depends on.
A business capability is something the organization needs to work: customer login, report delivery, checkout, file generation, an API-backed process, or another critical outcome. Dependencies are the systems, services, and resources behind it.
Capabilities and dependencies may be verified using the most appropriate technology for the task, including HTTP, TCP, DNS, SQL, SSH, Playwright, file system checks, SMTP, APIs, or other verification methods. The choice of verifier is an implementation detail; what matters is whether the capability or dependency is functioning as expected from a business perspective.
Business-specific logic. One predictable integration boundary.
Every BRS-Core verifier follows the same contract for identity, scheduling, execution, summary, and step results. Following that contract is required for clean, reliable operation under BRS-Core and BRS-Server.
The verifier decides what business evidence matters. BRS-Core handles discovery, scheduling, timeout enforcement, result recording, and operational output.
Want to see the contract and run a working verifier?
Start with the free Verifier Starter Kit, run a real verifier directly, inspect its structured PASS/FAIL evidence, and then learn how to turn your own business knowledge into verification.
Business capabilities and the dependencies behind them.
The same methodology applies whether the business capability happens in a browser, through an API, in a database, on a server, or during a scheduled process.
| Business capability | Supporting dependencies | Possible verification methods |
|---|---|---|
| Customer Login | Website, identity provider, database | Playwright, HTTP, SQL |
| Search Product Catalog | Website, search API, product database | Playwright, HTTP, SQL |
| Display Product Images | Website, image metadata, cloud object storage | Playwright, HTTP, API |
| Process Payment | Checkout application, payment gateway, order database | Playwright, HTTP, API, SQL |
| Send Invoice Email | Invoice service, SMTP provider, template store | SMTP, HTTP, SQL |
| Process Payroll | Payroll service, database, export file, delivery destination | SQL, SSH, file checks, SFTP |
| Import Inventory | Inbound file, import directory, inventory database | SSH, file checks, SQL |
| Generate Monthly Report | Database, report engine, output location | SQL, HTTP, file checks |
| Complete Nightly Backup | Backup service, storage destination, completion artifact | SSH, API, file checks |
| Submit Insurance Claim | Customer portal, claims API, database, document storage | Playwright, HTTP, API, SQL |
| Run Daily Reconciliation | Source systems, reconciliation job, result file, database | SSH, SQL, file checks, API |
| Publish Scheduled Content | CMS, publishing API, web server, CDN | API, HTTP, DNS, Playwright |
W3Patterns verifies business reliability—not deep infrastructure diagnostics.
W3Patterns stops at the business boundary. It verifies business capabilities and the health of their supporting dependencies. Deep infrastructure diagnostics remain the responsibility of the customer's existing observability platform.
The distinction is not determined by the technology used. The distinction is determined by the question being asked.
“Why is CPU steal time increasing?” is an infrastructure observability question.
Start with the capability that matters most.
You do not need to model every process on day one. Start with one critical business capability and the dependencies that support it.
Additional capabilities and dependencies can be verified using the same BRS-Core model.
A typical first implementation
- Identify one critical business capability
- Identify its supporting dependencies
- Choose the appropriate verifier for each check
- Report status, duration, reason, and timestamp
- Present the result in the Business Reliability System
Your business defines what should be verified.
The examples on this page are starting points, not limits. Start with the free Verifier Starter Kit to run a real verifier yourself. When you are ready for continuous operation, BRS-Core runs approved verifiers as part of 24/7 business capability monitoring.