The open foundation · MPL 2.0
The open substrate beneath every Visca product. Open specifications, a reference runtime in Rust, SDKs in four languages, a conformance suite. Anyone can build on it, ship Lattice-compatible bundles, run a conformant runtime, or compete with Visca on top of it.
Lattice Runtime defines, at the protocol level, what an autonomous actor is and how it interacts with the world. Five open specifications. A reference implementation. SDKs and conformance. Visca's products are reference implementations of these specifications, plus commercial extensions for scale, federation, and enterprise integration.
Immutable, content-addressable, signed artifact containing everything an autonomous actor needs to execute — including, for embodied actors, firmware, weights, and behavior trees.
Cryptographic identity for autonomous actors. Keypair plus principal, runtime, lineage, and (for embodied) hardware attestation.
How autonomous actors request scoped, time-bound, audited authority — and how that authority is vended as an ephemeral credential.
Capability-based discovery, mTLS rooted in Sigil identities, and agent-aware routing across actors, tools, MCP servers, and embodied actuators.
Canonical format for an action record. Sigil-keyed, cryptographically chained, signed by the observing runtime. The wire format every audit emitter targets.
The covenant
The relationship between Visca, Lattice Runtime, the developer community, and our customers is governed by a covenant that constrains Visca's behavior in perpetuity. It predates revenue, predates funding, and is structurally enforced through licensing, governance, and scope discipline.
MPL 2.0 reference runtime. Apache 2.0 SDKs and conformance suite. CC BY 4.0 specifications. Fixed at v0.1, forever. Never relicensed under BSL, SSPL, Elastic License, FSL, or any other restrictive or source-available license.
Once the project reaches an adoption threshold defined in the charter, Lattice Runtime will be donated to a neutral software foundation. The donation makes relicensing legally impossible by Visca or any successor.
Contributions are accepted under the Developer Certificate of Origin. No contributor license agreement is required, and none may be added retroactively. The contributor base is a collective rights-holder by design.
A feature shipped in Lattice may never be moved behind the Visca commercial paywall. Every such feature's history is auditable in the repository's commit log.
Visca's commercial model captures value through operational excellence in delivering Lattice at production scale — never through restrictions on the substrate itself.
The covenant is published in full at the project's governance repository and may be amended only with the consent of the foundation that holds Lattice Runtime.
A fourteen-page architectural and positioning document covering the autonomy problem, the Visca approach, all eight products, the deployment models, the integrations, and the covenant in full.
The autonomy economy is shipping
Build, run, and trust autonomous systems on an integrated platform — software, embodied, and hybrid. Open foundation. Enterprise cloud. No license rug-pulls, ever.