Skip to content
VB-OSVB-OSVB-OS Docs

VB-OS Verification Templates

Templates provide ready-to-use verification configurations for common domains. Each template includes a complete boundary definition, evidence schema, example workloads, and optional connector configurations and flow definitions.

What a Template Includes

Section titled “What a Template Includes”
Component Description
Boundary DSL Complete VBL source with predicates, evidence requirements, and evaluation logic
Evidence Schema Field definitions for each required evidence type
Example Workloads Sample evidence payloads with expected outcomes
Outcome Statement Plain-language description of what the boundary verifies
Certification Model Optional compliance and audit configuration
Connector Configs Optional pre-configured connectors with evidence mappings
Flow Definitions Optional post-evaluation reaction pipelines
Integration Code SDK snippets for Python, Node.js, and curl

Domains

Section titled “Domains”

Templates are organized by domain:

Domain Examples
Healthcare Clinical AI authorization, medical imaging certification, prescription verification
Finance Wire transfer authorization, adjustment completeness, payment routing
Cybersecurity Ransomware containment, access escalation
AI/ML Model deployment gates, recommendation governance
DevOps Deployment gates, incident response
E-Commerce Refund authorization
Insurance Claims verification
Identity Identity verification
Legal Contract verification
General Cross-domain verification
Autonomous Autonomous systems verification

Forking a Template

Section titled “Forking a Template”

Fork a template to create a new project with all components pre-configured:

Terminal window
curl -X POST https://api.vb-os.org/v1/templates/finance-wire-transfer-auth/fork \
  -H "Authorization: Bearer YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "project_name": "Wire Transfer Governance",
    "workspace_id": "WORKSPACE_ID"
  }'

Forking creates:

  • A project with a development environment
  • Boundary versions compiled from the template DSL
  • Connectors with evidence mappings (if configured)
  • Flows as draft versions (if configured)
  • Certification model (if configured)
  • Active deployments for each boundary

Template Visibility

Section titled “Template Visibility”
Visibility Description
PUBLIC Visible to all authenticated users
ORG_PRIVATE Visible only to the owning organization

Creating Templates

Section titled “Creating Templates”

Organizations can create their own templates from approved boundary versions:

Terminal window
curl -X POST https://api.vb-os.org/v1/org/templates/from-boundary \
  -H "Authorization: Bearer YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "boundary_version_id": "VERSION_ID",
    "name": "Internal Payment Gate",
    "slug": "internal-payment-gate",
    "domain": "FINANCE",
    "category": "Payments",
    "description": "Standard payment authorization for internal services"
  }'

Next Steps

Section titled “Next Steps”