You already built the proof. Use it more than once.
BRS-Core is designed to continuously verify the capabilities your business depends on. But a BRS verifier is independently executable. That means the same business proof does not have to wait for continuous monitoring to be useful.
Your deployment process can run that verifier directly. It can ask whether an approved business capability works before promotion, whether it still works immediately after deployment, and then hand the same verification back to BRS-Core for continuous operation.
One verifier. Three jobs.
Release gate. Post-deployment smoke test. Continuous business verification. The verifier's business logic and result contract stay the same. Only the caller changes.
Before. After. Ongoing.
Before deployment
Release gate
Run an approved verifier against the appropriate test or staging target. A successful exit permits promotion; a failed exit stops the pipeline.
After deployment
Business smoke test
Run the verifier once against the newly deployed target. Confirm that the capability actually works after the release reached its environment.
Keep verifying
Continuous verification
Let BRS-Core schedule the same verifier repeatedly and expose its ongoing results through metrics, the JSON API, and operational logs.
The important part
You are not maintaining separate CI tests and BRS business checks for the same capability. The same approved verifier can move through the deployment lifecycle with the software it protects.
Your pipeline already understands the signal.
Direct verifier execution is intentionally simple. Run the verifier once and capture its JSON result if you want a release artifact:
node /path/to/verifiers/customer-checkout.js > verification.json verifier_status=$? jq -e . verification.json exit "$verifier_status"
Exit 0
The reported business workflow passed.
The pipeline may continue to its next approved step.
Exit 1
The verifier reported failure or could not complete reliably.
The pipeline can stop rather than promoting a release without business acceptance.
The process exit status is the gate signal. The JSON document is optional evidence that can be retained with the release record.
Infrastructure can be healthy while the business capability is broken.
A deployment tool can tell you that a build completed, containers started, or a health endpoint answered. A business capability verifier asks a different question: can the capability the business cares about actually complete?
That makes a BRS verifier useful at the moment a release decision is being made—not only minutes or hours later when monitoring notices a problem.
Example
If your verifier proves that a customer can authenticate, reach the expected experience, and sign out successfully, that same proof can be run as part of release acceptance and then continuously afterward. The pipeline and BRS-Core are asking the same business question at different times.
This bonus does not turn BRS-Core into a CI/CD system.
Your CI/CD platform still owns
- Build and deployment orchestration
- Unit and integration tests
- Secrets supplied through approved mechanisms
- Promotion and rollback policy
- A job-level timeout as final protection
The BRS verifier contributes
- Business-specific acceptance logic
- One direct execution per gate or smoke test
- Deterministic pass/fail exit status
- Machine-readable JSON evidence
- The same proof BRS-Core can run continuously
A pre-deployment verifier supplements your normal build and test process. It does not replace it. Recurring execution, process isolation, scheduling, metrics, and ongoing business reliability remain BRS-Core responsibilities.
Start with a verifier you already trust.
If you already have a BRS verifier that proves a release-sensitive capability, you already have the interesting part. Add a direct verifier run to an appropriate deployment stage, honor its exit status, and optionally retain the JSON result with your release evidence.
If you are new to verifiers, start with the free Verifier Starter Kit. It gives you a real independently executable verifier you can run before deciding whether to use it in a pipeline or operate it continuously with BRS-Core.
Get the Free Starter Kit Build Your First Verifier Read the Product Guide