Packaging
The packaging layer of the self-hosted stack.
The packaging primitive of the stack, run inside your perimeter. Immutable, content-addressed, Sigil-signed bundles — everything an autonomous actor needs to execute, packaged as a single attestable artifact and registered in your own registry.
Seal is a primitive of the Visca stack — it ships with the stack, versions with the stack, and audits with the stack. It is not separately purchasable.
What it is
A Seal Bundle contains everything required to instantiate a specific class of actor at a specific version: behavioral specifications, tool references, model references, memory schemas, and — for embodied actors — firmware, model weights, sensor calibrations, behavior trees. Every Bundle is content-addressed and signed by the issuer's Sigil — the same identity the rest of the stack trusts. Two actors with the same Bundle hash are identical in every behaviorally relevant respect. The unit of reproducible autonomy, sealed inside your perimeter and traceable through Chronicle from build to run.
The problem
Production agents today are rarely reproducible. The prompt was edited in a UI. The tool list was changed via a config push. The model version was upgraded silently. Six months later, a regression appears, and there is no way to recover the exact actor that ran in production a quarter ago. For embodied actors, the problem is sharper: firmware, model weights, and behavior tree changes flow through different channels with no unified versioning — and a stitched stack scatters those artifacts across registries you do not control.
Capabilities
A bundle definition
bundle "acme/triage" {
version = "3.2.1"
behavior {
type = "agent"
prompt = file("./prompts/triage.md")
tools = [
"mcp://zendesk@^2.0.0",
"mcp://[email protected]",
]
}
model {
primary = "anthropic/claude-sonnet-4-6"
fallback = "openai/gpt-5"
ceiling = { tokens = 50000, cost_usd = 0.50 }
}
memory {
schema = file("./schemas/triage-memory.yaml")
retention = "30d"
}
capabilities {
requires = [
"zendesk:tickets:assigned:read",
"zendesk:comments:assigned:write",
"kb:articles:public:read",
]
}
}Open and commercial
Seal has two surfaces: an open-source reference in Lattice Runtime (MPL 2.0), and a managed delivery as part of the Visca stack on Visca Cloud. Features in the open never move behind the paywall.
Open
MPL 2.0 · self-hostable · foundation-track governance
Commercial
Your tenancy · dedicated · self-managed · air-gapped
LIFECYCLE · same plane
The data-model layer of the self-hosted stack.
The data-model primitive of the stack, run inside your perimeter. Declare what should exist as versioned source; agents write it as source, humans edit it as a spreadsheet. Plan, apply, drift-detect — all against state that stays in your tenancy.
The open-source runtime layer — and the foundation the whole stack runs on.
The runtime layer of the stack, and its open-source foundation (MPL 2.0). Runs autonomous workloads across cloud, edge, on-device, and on-robot — with first-class awareness of tokens, models, memory, and embodiment, routing over open-weight models so cognition stays in your walls.
The build surface — for humans and agents.
Where humans and agents build autonomous systems. CLI, SDKs, local runtime, eval harness, replay, documentation, templates — and an agent-facing surface so agents can author, evaluate, and ship other agents.
Across the stack
The identity layer of the self-hosted stack.
The identity primitive of the stack, run inside your perimeter. Issues, verifies, and revokes the cryptographic identity every autonomous actor holds — bound to principal, runtime, and lineage from the moment of instantiation. The one identity every other primitive trusts.
The authority layer of the self-hosted stack.
The authority primitive of the stack, run inside your perimeter. Brokers every access from an autonomous actor to a consequential resource against its Sigil — identity-bound, scoped, time-limited, and recorded to Chronicle. Long-lived credentials disappear.
The fabric layer of the self-hosted stack.
The fabric primitive of the stack, run inside your perimeter. Discovery, mTLS, and routing across every autonomous actor and every resource an actor reaches — rooted in the same Sigil identities, not hardcoded URLs, and never crossing your boundary.
The record layer of the self-hosted stack.
The record primitive of the stack, run inside your perimeter. The one audit trail every other primitive writes to — a queryable knowledge graph of every actor, plus the append-only, cryptographically chained log of every action, keyed to Sigil and Capability Grant.
The whole stack. Self-hosted. One ecosystem.
Models, identity, tools, voice, payments, runtime, and audit — as one integrated ecosystem, self-hosted, sovereign, air-gapped. Nothing stitched from vendors. Nothing leaves your perimeter. Open at the core. No license rug-pulls, ever.