Next Steps After Your First VB-OS Evaluation

You have submitted evidence, received ASSERT and DEFER verdicts, and replayed a past evaluation. Here is where to go next depending on what you want to build.

Author Your Own Boundaries

The quickstart used a pre-built template. To define your own verification logic:

1. Learn the VBL syntax: VBL Syntax Reference covers the full boundary language
2. Understand the constructs: evidence requirements, prohibitions, predicates, provenance, and the BOUNDARY expression
3. Follow the boundary lifecycle: draft → compile → deploy → evaluate → version

Start with the Writing Boundaries guide for a hands-on walkthrough.

Connect Evidence Sources

Instead of submitting evidence directly in API calls, connect external systems as evidence providers:

• Databases: query evidence from PostgreSQL, MySQL, or other databases
• APIs: fetch evidence from REST or GraphQL endpoints
• Identity providers: acquire identity evidence from OIDC/SAML providers

Each connector maps external data to boundary fields with provenance tracking. See Connectors to learn how evidence acquisition works.

Build Certification Models

Certifications run multiple evaluations against a set of boundaries and produce a composite result. Use them for:

• Deployment gates: certify that a release meets all verification requirements
• Compliance checks: run a suite of boundaries and produce an auditor-ready report
• Periodic re-certification: schedule recurring certification runs

See Certification for the full model.

Integrate with Your Application

SDKs

• Python SDK: synchronous and asynchronous clients, Pydantic models, full type coverage
• Node.js SDK: zero-dependency, native fetch, ESM + CJS dual export

CLI

The VB-OS CLI provides command-line access to all platform features:

vbos verify --project my-project --boundary payment-authorization \
  --evidence '{"transaction_amount": 15000, "account_balance": 42000}'

vbos evaluations list --project my-project
vbos replay --project my-project --evaluation EVALUATION_ID

API

The API Reference documents all HTTP endpoints with request/response schemas.

Build Flows

Flows define what happens after a boundary evaluation. They are reaction DAGs that dispatch actions (webhooks, notifications, log entries) based on whether the evaluation returned ASSERT or DEFER:

• Webhook dispatch to external systems
• Conditional routing based on evidence field values
• Notification and logging on DEFER outcomes

See Flows to learn how post-evaluation reaction pipelines work.

Govern Agent Actions

For teams building autonomous systems, VB-OS provides deterministic authorization boundaries around agent execution:

• Place verification gates before agent actions
• Ensure every agent action is authorized, recorded, and replayable
• No probabilistic guardrails: binary ASSERT/DEFER gates

See Govern Agent Actions for integration patterns, AI Agent Governance for the architectural overview, and Execution Authority vs. Guardrails for how deterministic execution authority compares to guardrail approaches.