Historical documentation. Public archive withdrawn on 15 October 2026. Source-bearing R50 and R60 archives are retained privately. A binary-only replacement is not yet published. Current download status.

R50 v24 · autonomous runtime package

Governed operations for self-hosted infrastructure.

R50 packages the usable GuardLattice runtime surface for enterprise evaluation: policy receipts, programmable effect envelopes, GL-DDBS local transaction evidence, recovery controls and local verification in one autonomous handoff.

Download status See what is included

No public-site runtime dependency Local install and smoke checks Bounded claims, exact hashes

Operation admission path policy -> constraint -> effect -> recovery

v24 verified package

01Identity

Authenticated principal, tenant and delegated authority context.

02Mandate

Scope, target, time window and allowed operation class.

03Limit

Shared budget, unique effect identity or restore floor.

04Receipt

Decision and admitted envelope bound to local evidence.

05Effect

Durable state path or external instruction under control.

For software agentsR50 is shaped around effects, not only decisions: a permitted actor still needs a governed target, cost and recovery context.

For operatorsThe package is verifiable without guardlatice.com. Your deployment controls origin, keys, policies, data and operation.

archive 2f966295948424c9456d206de8c66687977ee2fd28e74cf746ba4d1250b24102

Runtime surfaceR50

Autonomous package for evaluating GuardLattice without a hosted control-plane dependency.

Package versionv24

Hash-bound public candidate with local verification scripts and retained authority file.

GL-DDBS scopeLocal

Selected transaction, MVCC and recovery evidence. Multi-machine superiority remains unclaimed.

Production statusNo

R50 is an evaluation candidate, not a production admission or universal replacement claim.

Use Cases

Where R50 is useful now.

R50 is for teams that need to test GuardLattice as a programmable control layer around sensitive operations before committing to a production deployment.

Delegated software actions

Evaluate how a service or automation runner can be limited by mandate, target, cost and effect identity.

Financial operations

Prototype shared budgets, duplicate-effect rejection and approval-to-effect binding around payment-like workflows.

Administrative control

Model high-impact changes such as grants, revocations, exports and restoration boundaries with explicit evidence.

Database evaluation

Inspect the GL-DDBS local profile, transaction receipts and boundaries before any distributed database claim is made.

Programmable Control

One operation contract, from decision to recovery.

The product direction is not to stack manual checks. R50 packages the first usable surfaces for expressing the operation envelope once, then verifying the path from authority to effect.

Bind identity and mandate

The acting principal, tenant, authority scope and expiration must be represented before the effect path begins.

Bind target and payload

The policy decision should cover the concrete route, target and operation payload, not only a high-level action name.

Reserve shared limits

Budgets, usage caps and uniqueness constraints need a shared authority when several services can act concurrently.

Commit with receipt

The durable effect should be tied to the admitted envelope so retries, crashes and replays do not create a second business effect.

Recover without stale power

Restore paths must preserve revocations and recovery floors instead of reactivating old authority after rollback.

Package Contents

What is inside the R50 handoff.

The page stays product-first, but the package remains evidence-first. Everything below is meant to be installed, checked and inspected locally.

Included in the candidate

Runtime binaries for GL-C, GL-DDBS administration, PGWire adapter material and FFI evaluation.
Source slices for policy, GL-DDBS, GL-T pre-effect, PDP, FHE and related runtime surfaces.
Local package verification, documentation contract checks, C FFI smoke and autonomous smoke scripts.
Authority files, SHA-256 sidecars and retained receipts for reproducible evaluation.

Kept outside the claim

No production admission is claimed by this package.
No universal O(1), universal database replacement or full industrial superiority claim is made.
Distributed atomicity, multi-machine consensus, global recovery and external audit still require separate qualification.
The public website is only a reference and download surface, not a product dependency.

Download

R50 public archive withdrawn.

The source-bearing archive is retained privately. The hashes and instructions below describe the historical release only, not a currently available download.

Download status Open authority

Withdrawn archive	guardlatice-r50-autonomous-package-20261014-v24.tar.gz
SHA-256	`2f966295948424c9456d206de8c66687977ee2fd28e74cf746ba4d1250b24102`
Size	17,323,915 bytes
Sidecar	archive SHA-256 sidecar
Authority	versioned · current alias

$ sha256sum -c guardlatice-r50-autonomous-package-20261014-v24.tar.gz.sha256

guardlatice-r50-autonomous-package-20261014-v24.tar.gz: OK

$ tar -xzf guardlatice-r50-autonomous-package-20261014-v24.tar.gz

$ cd guardlatice-r50-autonomous-package-20261014-v24

$ ./scripts/verify-package.sh

R50 autonomous package hashes and boundaries verified

$ ./scripts/run-r50-autonomous-smoke.sh

R50 autonomous smoke passed

Release Boundary

Clear claims. No hidden marketing leap.

R50 is deliberately presented as an evaluation package. That keeps the public product credible while giving buyers and engineers a concrete path to qualification.

Autonomous by designThe package can be installed, programmed, verified and operated without depending on the public site.

Programmable, not manualOperation contracts are represented as package surfaces so new scenarios do not require a handcrafted page or one-off script.

Next industrial qualificationsMulti-machine budgets, global idempotence, anti-rollback restore, derived data control and distributed database comparison remain the next proof targets.