Get access↗
Plugins · publisher bonds

A marketplace
of signed plugins.

Plugins extend the Omega substrate — new resolvers, new audit backends, new agent tools, new image transforms. Every plugin is a signed brane manifest. Publishers post a bond against their plugin's good behaviour; the bond is slashed automatically if the plugin breaches its declared capability surface. The result is a marketplace where install is a single command and trust is on-chain.

[plugin shape]
signed brane manifest
[publisher bond]
staked · slash-on-misbehaviour
[install]
one command · capability-scoped
[discovery]
on-chain index · OAS DID resolution
At a glance

The properties
that matter.

∞
plugins, in theory

A plugin is just a brane with a declared extension manifest. Anyone can publish.

BOND
every publisher staked

Bonds are denominated in stablecoin or signed credit. Slashed automatically on a verified breach.

SIGNED
every install

You install by DID + version + content-hash. Tamper-evident from the index to the host.

< 1 min
publish to install

Submit, sign, post bond, indexed. The next ω plugin search resolves it.

In the manifest

How you
describe it.

plugin-publish.zgraph.toml
[plugin.metric-export]
did         = "did:omega:plugin:metric-export/v1.2"
publisher   = "did:omega:org:l1fe.ai"
brane       = "omega/metric-export:1.2"
substrate   = ["gaia", "biome"]   # which substrates can host
// publishing a plugin to the marketplace

// publishing a plugin to the marketplace

In operation

What it
looks like running.

$ω plugin search "metric export"
did publisher bond stars installs did:omega:plugin:metric-export/v1.2 l1fe.ai $500 ★4.7 1,242 did:omega:plugin:prom-export/v0.9 acme-metrics $200 ★4.1 512 did:omega:plugin:json-otlp/v0.4 indep $100 ★3.9 88
$ω plugin add did:omega:plugin:metric-export/v1.2
→ verified publisher signature → verified substrate signature → verified bond ($500 USDC, locked) → capability declared: net.http, fs.tmp (review) ✓ installed. attached to brane.api as edge "telemetry.metric"
shape
signed brane manifest with extension declarations
publisher
OAS-spec DID; bond required to publish
bond
stablecoin or signed credit; auto-slash on breach
breach
capability outside declared surface; misrepresented metadata
discovery
OAS resolver-backed index; signature-verified
install
capability-scoped at install time; brane review at upgrade
By design

What this
surface does.

Publishers stake bonds

A plugin without a bond does not get listed. Bond size is a market signal; consumers can filter on it.
TRUST

Slashing is mechanical

A capability breach is a witnessed event in the audit chain. The slash is automatic; the publisher doesn't have to admit anything.
AUTO

Plugins inherit capability scoping

Installing a plugin doesn't expand your brane's authority — the plugin runs under the union of declared capabilities, never beyond.
SCOPED

No vendor lock

Plugin DIDs and bonds live on-chain. Move your installs to a self-hosted Habitat substrate; the plugin keeps working — same DID, same signature.
OPEN
← ComplianceDevelopers →