GuardLatice
GuardLatice platform

GuardLatice - Policy, Crypto, and Assurance Runtime

GuardLatice is a local-first runtime for policy decisions, cryptographic distribution, signed delivery, and machine-readable assurance.

capability_grid

What the platform controls

Authorization decisions: policy and access decisions stay tied to runtime evidence. Release verification: artifacts, manifests, and hashes remain inspectable. Local install paths: operators can verify the exact lane before promotion. Trust evidence: claims stay bound to proofs. Dashboard authority: roles, plans, packs, and approvals control what can happen. Artifact delivery: downloads and aliases remain governed.

01

Authorization decisions

Authorization decisions: policy and access decisions stay tied to runtime evidence

02

Release verification

Release verification: artifacts, manifests, and hashes remain inspectable

03

Local install paths

Local install paths: operators can verify the exact lane before promotion

04

Trust evidence

Trust evidence: claims stay bound to proofs

05

Dashboard authority

Dashboard authority: roles, plans, packs, and approvals control what can happen

06

Artifact delivery

Artifact delivery: downloads and aliases remain governed

proof_strip

Proof before claims

Route checks prove the public surface resolves. Hashes bind pages and artifacts to exact bytes. Manifests bind source state to rendered output. Rollback ledgers keep recovery inspectable. Service probes verify runtime availability. Claim boundaries prevent unearned CBDC, GLAT, PQX, AST, CRB, CSV, custody, or regulated-money claims.

01

Route checks prove the public surface

Route checks prove the public surface resolves

02

Hashes bind pages and artifacts to

Hashes bind pages and artifacts to exact bytes

03

Manifests bind source state to rendered

Manifests bind source state to rendered output

04

Rollback ledgers keep recovery inspectable

Rollback ledgers keep recovery inspectable