Branes are
signed manifests, addressable.
Borrowed from string theory — a brane is a manifold the substrate inflates into a running thing. Each brane carries its own identity (Ed25519 keypair, OAS DID), its own capability surface, its own lifecycle, its own audit log. Compose branes through typed event edges; the substrate handles delivery.
oas:did:omega:brane:<id>
typed events · per-edge queues
capability-scoped
atomic · zero in-flight loss
The properties
that matter.
< 1 ms
edge dispatch latency
In-substrate event fanout. Cross-substrate adds your network RTT.
∞
edges per brane
Per-edge bounded queue, per-edge priority, per-edge back-pressure.
0
shared state by default
Branes do not share memory. State crosses on signed event payloads.
CRDT
when state must be shared
Opt-in CRDTs (RGA, OR-set) replicate per-brane state across replicas.
How you
describe it.
[brane.intake] substrate = "gaia" capability = "standard" image = "omega/intake:1.2" replicas = "auto"
// fan-in / fan-out across three branes via typed edges
What it
looks like running.
$ω branes inspect score
brane.score
did oas:did:omega:brane:score
pubkey ed25519:RJ4P...
replicas 8 / 8 ready
edges in: doc.batch (q=8/1024)
…
$ω branes diff score@v0.9 score@v1.0
image 0.9 → 1.0
capability net.http → unchanged
edges doc.scored → +doc.scored.metrics
deadline 8s → 6s
manifest name within a workspace
Ed25519 keypair per brane · OAS DID
typed names · per-edge queues · per-edge priority
queue full → upstream sees not-ready
atomic · drain-and-cutover · zero loss
instance-level · signed · resumable
What this
surface does.
Each brane has its own DID
OAS-spec did:omega:brane addresses with Ed25519 keys derived from the workspace owner. No central name service — the substrate honors the manifest signature.
Composable through typed events
No service mesh, no pubsub broker. Just typed edges with bounded queues. Back-pressure is first-class — pipelines stay stable under load.
Stateless by default, CRDT when needed
A brane is a function over its inputs. When you must share state across replicas, opt into a CRDT in the manifest — the substrate does the replication.
Atomic upgrades, zero in-flight loss
ω branes upgrade drains the old version's queues, cuts over, and only then tears it down. Roll back the same way. The manifest is the source of truth.