Start Here

You’ll go from sign-in to your first governed decision in about five minutes. No code required.

What You’ll Do

1. Sign in at vbos.cloud
2. Pick a starter template that matches your domain
3. See VB-OS make an ASSERT decision (conditions satisfied)
4. Change an evidence value to trigger DEFER (conditions not satisfied)
5. Replay the original decision to prove it’s reproducible

By the end, you’ll understand what ASSERT and DEFER mean, how evidence flows through a boundary, and why replay matters.

Sign In and Get Started

After signing in, VB-OS walks you through a guided setup. You’ll see a welcome screen. Click Get Started to begin.

Pick a Starter Template

VB-OS asks what kind of work you do. Choose a domain (Healthcare, Finance, or another industry) and you’ll see pre-built starter templates with real governance logic already configured.

Each template includes:

• A boundary with evidence requirements and predicates already written
• Sample workloads you can evaluate immediately
• Pre-configured actions for ASSERT and DEFER outcomes

Select a template and click Create this starter project. VB-OS forks it into your workspace, and you now have a working governance project.

Run the ASSERT Case

Your starter project comes with sample evidence that satisfies all boundary conditions. The guided checklist walks you through submitting this evidence and seeing the ASSERT result.

ASSERT means: the declared conditions were satisfied under this boundary. Whatever action this boundary governs is authorized to proceed.

ASSERT does not mean “good” or “correct.” It means the evidence you submitted met every requirement the boundary declared. If the boundary requires account_balance >= transaction_amount and the balance is higher, that’s ASSERT, regardless of whether the transaction is a good idea.

Trigger DEFER

Next, the checklist asks you to change an evidence value so that a condition fails. You’ll see VB-OS return DEFER with a clear breakdown of exactly what failed and why.

DEFER means: the declared conditions were not satisfied. The governed action cannot proceed under this boundary.

The evaluation detail shows you:

• Which stage failed (admissibility, prohibition, or predicate)
• Which specific condition wasn’t met
• The actual evidence values that caused the failure

This is the core of VB-OS: you always know exactly why a decision was made.

Replay

Finally, replay the original ASSERT decision. VB-OS loads the original evidence and boundary from immutable storage, re-runs the evaluation, and proves the result is identical.

This matters because it means any historical decision can be audited and reproduced, months or years later, with cryptographic proof that nothing changed.

What’s Next

After the guided setup, your Home page becomes an operational dashboard showing evaluation activity, live governance status, and items needing attention.

From here:

• Make the starter project real: replace sample evidence with your actual data by connecting a real system
• Create your own boundary: write governance conditions for your specific use case in the boundary editor
• Invite your team: add colleagues and assign roles in Team & Access

For developers who want to integrate VB-OS into applications, see Build with VB-OS.