BVER quick start.

Start here for platform onboarding, architecture references, and links to core strategic documents.

Build with BVER

Use BVER when your system is domain-heavy, long-lived, and requires capability composition across teams. Start with domain objects and references, define app surfaces, then compile into platform artifacts.

  1. Model domain references and aggregates in Python.
  2. Define app surfaces and contract interactions.
  3. Run compiler validation and emit `.bdam` output.
  4. Test in Sandbox, then promote with Deployment tools.

Next steps: open Download to use the `Compile → Test → Build → Deliver` workflow tools.

Runtime

Runtime Overview

BVER Runtime is the execution kernel for services, adapters, orchestration hooks, and governed EAGER subscriptions. Runtime docs and package guidance live here instead of the Download stack.

  • Service lifecycle and capability registration.
  • Adapter execution with explicit permissions.
  • Versioned runtime boundaries generated from contracts.

Runtime Packages

  • bver-runtime - core runtime execution package.
  • bver-stdlib - standard primitives and shared runtime libraries.
  • bver-eager-sdk - EAGER schema and channel integration client.

Package links remain placeholder references until publication.

Reference Pages

About

Mission and decision guidance consolidated into one page.

Open About

Roadmap

Current and upcoming platform milestones and delivery phases.

Open Roadmap