Projects
A project is the top-level container for governance work. Everything in VB-OS lives inside a project: boundaries, evaluations, deployments, environments, flows, certifications, and connectors.
Projects List
Section titled “Projects List”The Projects page shows all projects in your organization. Each project card displays the project name, slug, status, your role, boundary count, and the most recent evaluation verdict.
You can:
- Search by name or slug using the search bar (keyboard shortcut:
/) - Filter by workspace if your organization has multiple workspaces
- Switch between Active and Archived tabs
- Sort by name or creation date
- Toggle between card view and table view
Press n to create a new project from anywhere on the page.
Creating a Project
Section titled “Creating a Project”Click New Project or press n. The wizard has three steps:
1. Starting Point: Choose between starting from a template or from scratch. Templates include pre-built boundaries, sample workloads, and preconfigured evidence requirements for common domains (Healthcare, Finance, and others).
2. Configure: Enter a project name and optional description. VB-OS generates a URL-safe slug from the name automatically. If the slug is already taken, you will see a warning. Select which workspace to create the project in.
3. Review: Confirm your choices. If you chose a template, VB-OS forks it into your workspace with all boundary definitions, evidence requirements, and sample data included.
Project Overview
Section titled “Project Overview”After opening a project, you land on the Overview tab. The sub-navigation bar across the top provides access to all project sections:
| Tab | What it does |
|---|---|
| Overview | Health summary, readiness tracker, quick actions |
| Verify | Submit evidence and see evaluation results |
| Boundaries | Create and manage governance boundaries |
| Deploy | Deploy boundary versions to environments |
| Certify | Run multi-evaluation certification models |
| Monitor | View evaluation activity and trends |
| Integrate | Get API keys and connection details |
| Flows | Build post-evaluation reaction flows |
| Architect | AI governance assistant |
| Settings | Project configuration, team, environments, danger zone |
Health Summary
Section titled “Health Summary”The overview shows four stat cards: Total Evaluations, Assertions (ASSERT count), Deferrals (DEFER count), and Pass Rate (percentage of ASSERT verdicts).
Production Readiness
Section titled “Production Readiness”A checklist tracks your progress toward production. Steps include creating a boundary, running your first evaluation, deploying to an environment, and connecting a real evidence source. Each step marks as complete automatically when you finish it.
Quick Actions
Section titled “Quick Actions”Three buttons at the bottom: Open Verify (submit evidence), View Boundary (see your governance rules), and Get API Key (integrate programmatically).
Project Settings
Section titled “Project Settings”The Settings tab has five sections:
- General: Rename the project, update its description, or change its slug
- Team: Add or remove project members and assign roles (Admin, Developer, Auditor, Viewer)
- Environments: Create and manage deployment environments (Development, Staging, Production, Custom)
- Git Integration: Connect a Git repository for version-controlled boundary definitions
- Danger Zone: Archive the project (makes it read-only; reversible)
Each project member has one of four roles:
| Role | Permissions |
|---|---|
| Admin | Full access: manage boundaries, deploy, configure settings, manage team |
| Developer | Create and edit boundaries, run evaluations, deploy to non-production |
| Auditor | Read-only access plus replay and certification capabilities |
| Viewer | Read-only access to all project data |
Archiving
Section titled “Archiving”Archiving a project makes it read-only. All existing evaluations, boundaries, and deployments are preserved, but no new evaluations can be submitted and no changes can be made. Archived projects appear under the Archived tab on the Projects page.
What’s Next
Section titled “What’s Next”- Boundaries : define what VB-OS checks for each project
- Evaluations : submit evidence and review decisions
- Connectors : connect external systems as evidence sources