Build surface
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.
Praxis 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
Praxis is the canonical reference and the active build environment, in one. Author, evaluate, replay, deploy, and observe an autonomous system through a single workflow. Every command, every SDK call, every dashboard view operates on the same primitives: Sigils, Bundles, Capability Grants, Audit Envelopes — and every one of them is reachable by an agent under its own Sigil, not just by a human at a terminal. A coding agent can declare a data model in Cast, build and sign a Seal Bundle, request the capabilities it needs from Warrant, and ship to Lattice Runtime — all within its scoped authority and fully recorded in Chronicle. One mental model, whether the builder is a person or an agent. A new builder can bring up the full Lattice Runtime substrate locally in under sixty seconds — no accounts, no telemetry, no required cloud signup. The same SDKs work from laptop to production.
The problem
Building an autonomous system today is a sequence of disconnected tools. A framework SDK to write the agent. A separate library for memory. A separate observability tool. A separate eval framework. A separate deployment system. Each has its own concepts, configuration, identity model, logs. Cross-tool debugging requires correlating traces by hand. Cross-team handoff requires onboarding to a different stack entirely.
Capabilities
First hour with Visca
# Install
curl -sSf https://get.visca.ai | sh
# Bring the full Lattice substrate up locally — under 60 seconds
visca init my-workspace
# Start from a template
visca template apply task-tracker
# Declare your data model, plan, apply
visca cast plan ./model.lattice
visca cast apply
# Build and sign a Bundle (when you're ready for an agent)
visca seal build ./bundles/triage
# Watch it run
visca chronicle tail --sigil $(visca sigil current)
# Promote to Visca Cloud when ready
visca cloud deployOpen and commercial
Praxis 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 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.
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.
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.