The builder surface

UAB^™

UAB is where a builder composes a governed multi-agent system. You describe the roles and the authority each may delegate; UAB validates that against a governed-system contract and provisions a root that already carries its own cryptographic identity, with every child's authority bounded by its parent's.

What it isThe composer for governed multi-agent systems

You composeRoles + a permitted-delegation envelope

It provisionsAn identity-governed root, carrying your envelope

StageSign-up open · provisioning arranged on request, not self-serve

The outcome

Before

Composing a governed multi-agent system means wiring identity, delegation and least-privilege authority by hand, per agent, and hoping the wiring is right before anything runs.

After

You compose roles and a permitted-delegation envelope on one surface; UAB validates it against a governed-system contract and provisions a root that already carries its own cryptographic identity, with every child's authority bounded by its parent's.

UAB is the builder's on-ramp to the whole stack, the fastest way to stand up agents that already speak VAID and answer to the SYNTHERA foundation.

How it works

UAB turns a governed system from something you assemble by hand into something you compose and provision. Three steps, one surface.

STEP 01

Compose

Describe the roles in your system and the permitted-delegation envelope between them, who may act on whose behalf, and how far that authority reaches.

STEP 02

Validate

The spec is checked live against a governed-system contract as you build it, so an unsound composition is caught before anything is provisioned, not after it misbehaves.

STEP 03

Provision

UAB hands the validated spec to a provisioning engine, which mints the system's root identity and deploys it carrying the delegation envelope you composed. The rest of the tree is authority the root may pass on, each child minted, and attenuated, at the moment it is spawned.

What's wired today, and what's maturing Cryptographic identity, delegation lineage and least-privilege attenuation are what UAB composes and validates today. Sign-up is open; provisioning itself is arranged on request, not self-serve. Action-level policy enforcement and a durable audit-of-record come from the SYNTHERA foundation as it hardens toward pilot, UAB composes against them as they land. We'd rather say that plainly than imply a finished control plane. Two more things we would rather say than let you discover: the identity a root receives is real and minted on the foundation, but UAB itself verifies nothing in your browser, everything on screen before you provision is your own input. And the protocols and instructions you attach to a role are recorded with your design; they do not yet change what the deployed agent runs.

Proof

The point of a governed surface is that the guardrail is real. What is governed is delegation: which roles may spawn which children, and how far the child's authority may reach. A composition that lets a child escape its parent's scope is refused.

Example · least privilege, enforced at the spawn

compose → validate → mint

role: planner    scope → acme/
role: researcher may be spawned by planner

# the composition gives the child a scope its parent does not hold
planner → spawn researcher, scope acme-secrets/ ... DENIED
  reason: child scope is not a subset of the parent's

Refused twice, independently: by the schema in the browser before anything is provisioned, and by the foundation itself when the root tries to mint that child at runtime. The foundation-side denial is proven in the engine's own test harnesses, not from the browser.

What this example is not It is not an action being blocked. Scope is a resource prefix, and action-level policy is still to come, so an agent is bounded in what it may hold and pass on, not yet policed per call. The earlier version of this panel showed a write being denied for exceeding a capability set. Nothing in the deployed system does that.

Demo

A guided walk through this page, pausing on the example above. Nothing on it is mocked or live-called; it is the static markup already on this page.

SYNTHERA is the trust layer for multi-agent systems: every agent gets a verifiable identity, scoped authority and a tamper-evident record, so software from different teams, vendors and frameworks can act on each other’s behalf without custom glue between every pair.

Discuss a technical evaluation.

Discuss an evaluation