Visca
The Stack/Trust plane

Identity

Sigil

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.

Sigil 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

The role Sigil plays in the stack.

Sigil is constitutive: there is no autonomous actor without one, and no other primitive functions without it. Every agent, robot, drone, and autonomous service receives a cryptographic identity at the moment it comes into being. The Sigil binds the actor to the human or system that authorized its existence, the runtime hosting it, and the lineage of spawning actors back to a human root. For embodied actors, the Sigil includes hardware attestation rooted in TPM, Secure Enclave, or vendor roots of trust — a verifier can determine, cryptographically, that a request originated from a specific physical robot, running a specific firmware, in a specific configuration. Warrant authorizes against it, Plexus routes on it, Chronicle keys every record to it — one identity across the whole stack, all of it inside your own walls.

The problem

What goes wrong without it.

Stitch the stack from a dozen projects and each layer invents its own notion of who an actor is — and most autonomous actors have no real identity at all, merely the process holding an API key. There is no shared answer to who an actor is, who authorized its existence, what its lineage is, or whether it has been revoked. Without one identity the whole estate trusts, every authorization, audit, and revocation operation is impossible.

Capabilities

What Sigil does.

Sigil structure

What Sigil looks like in code.

sigil := {
  pubkey:      Ed25519PublicKey,
  principal:   Sigil | HumanIdentityRef,
  runtime:     SigilRef,
  lineage:     [SigilRef, ...]      // chain back to root principal
  bundle:      ContentHash,         // the bundle this actor was instantiated from
  issued_at:   Timestamp,
  not_after:   Timestamp,
  attestation: HardwareAttestation? // for embodied actors
  revocation_endpoint: URL,
}

Open and commercial

Built in the open. Run in your tenancy.

Sigil 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

Lattice Runtime — open foundation

MPL 2.0 · self-hostable · foundation-track governance

  • ·Sigil identity schema
  • ·Reference issuer
  • ·Local verification primitives
  • ·Revocation protocol

Commercial

Visca Cloud — managed sovereign delivery

Your tenancy · dedicated · self-managed · air-gapped

  • ·Hosted Sigil issuance at scale
  • ·Cross-organization federation
  • ·Enterprise IdP integration (Okta, Azure AD, Ping)
  • ·Hardware HSM-backed signing keys
  • ·Compliance-grade audit of issuance

TRUST · same plane

Inside the trust plane with Sigil

Across the stack

Composing with the other planes.

The whole stack. Self-hosted. One ecosystem.

The entire agent stack, inside your own walls.

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.