Template Registry
The Template Registry is accessible from the main sidebar and serves as the central catalog for governance templates. Templates are reusable governance configurations (boundaries, connectors, flows, examples, certifications) that can be forked into new projects.
Browsing Templates
Section titled “Browsing Templates”The registry opens to a catalog view showing available templates. Starter templates (maintained by VB-OS) appear first, followed by organization templates.
Each template card shows the template name, domain badge, description, and fork count.
Filtering and Sorting
Section titled “Filtering and Sorting”- Search: filter templates by name or description
- Domain: filter by governance domain (Healthcare, Finance, Cybersecurity, AI/ML, DevOps, E-Commerce, Insurance, Identity, Legal, Autonomous, General)
- Category: filter within a domain (e.g., Healthcare has Patient Safety, Diagnostic Imaging, Pharmacy)
- Sort: by newest, name, or most forked
Template Detail
Section titled “Template Detail”Click a template to view its full detail page, which includes:
- Description and outcome statement: what the template governs and the governance outcome it achieves
- Domain and category badges
- Boundary definitions: the VBL source code for each boundary in the template, with syntax highlighting
- Connectors: evidence source connectors included in the template
- Flows: post-evaluation flows included in the template
- Examples: sample workloads showing expected evaluation outcomes
- Integration guidance: SDK and CLI snippets for using the template’s boundaries
- Certification models: certification configurations included in the template
- Version history: previous versions of the template with version numbers and timestamps
Forking a Template
Section titled “Forking a Template”Click Fork on any template to create a new project from it. The fork dialog asks for:
- Workspace: which workspace the new project belongs to
- Project name: the name for the new project
Forking copies all of the template’s governance artifacts (boundaries, connectors, flows, examples, certifications) into a new project. The forked project is independent: changes to the template do not affect forked projects, and changes to the project do not affect the template.
Creating Templates
Section titled “Creating Templates”Organization Admins can create new templates from the Registry > Manage section. The creation wizard has eight steps:
- Basics: name, slug, domain, category, description, and outcome statement
- Boundaries: define one or more boundaries with VBL source code
- Connectors: configure evidence source connectors
- Flows: define post-evaluation flows
- Examples: add sample workloads with expected outcomes
- Integration: provide SDK and CLI usage guidance
- Certification: configure certification models
- Review & Create: review all configuration before creating
Publishing a Boundary as a Template
Section titled “Publishing a Boundary as a Template”From a project’s boundary detail view, you can publish an existing boundary as a new template. This pre-fills the template with the boundary’s current VBL source and opens a dialog where you provide the template name, slug, domain, category, and description.
Managing Templates
Section titled “Managing Templates”The Registry > Manage section lists your organization’s templates. From here you can:
- Edit a template: update any of the eight configuration sections
- View versions: see the version history of each template
- Create new templates: start the creation wizard
What’s Next
Section titled “What’s Next”- Projects : create projects from templates or from scratch
- Boundaries : manage boundaries within a project
- Start Here : get started with your first project