Validiti Validiti
In Development Validiti Drift · Drift-channel-as-a-service

Knowledge that stays current. Without re-shipping the binary.

A drift channel is a signed, append-only update stream tied to a specific brain, library, or runtime. Subscribers pull the deltas they're missing; the receiver applies them in place. Your medical brain, your Pacta42 library, your Accelerate cache — fresh as of this morning, without a redeploy.

delta-only
Bandwidth
signed
Every update
subscribe
Or self-host
no redeploy
Same binary
↓ What it is

What Validiti Drift is

Three statements, no jargon.

01

A signed update channel tied to a named asset (a brain, a Pacta42 library, an Accelerate cache). Each update is a small, signed delta the receiver verifies and applies in place.

02

Validiti runs canonical drift channels for every Knowledge brain and every public Pacta42 library — subscribed customers stay current automatically. Customers can also publish their own private channels.

03

Receiver-side already shipped: the drift listener is part of the Accelerate runtime. Drift productizes the publishing side and turns subscribed channels into a paid, SLA-backed service.

Channel types

Three classes of channel. Same protocol, same signing, same receiver.

Brain channels

Updates to a Knowledge brain

Medical brain gets new FAERS reports, drug labels, treatment guidelines. Legal brain gets new rulings, statutes, regulatory updates. Each update is a small signed delta, applied in place to the loaded brain.

Library channels

Updates to a Pacta42 library

Public Pacta42 libraries (Wikipedia, Gutenberg, StackExchange, foundation sets) drift over time. The drift channel ships only the changed entries; subscribers stay coherent without re-downloading the whole library.

Runtime channels

Updates to an Accelerate cache

Cached responses for known queries can be refreshed centrally and pushed to subscribers as drift updates. Production runtimes stay coherent across fleets without warming each instance separately.

Private channels

Your own corpus, your own subscribers

Authoring side of the same protocol. Publish a private drift channel from your own internal corpus — medical group, law firm, in-house research team. Validiti hosts the relay; only your verified subscribers receive.

Use cases

Where a drift channel solves a problem static distribution cannot.

Regulated knowledge

Stay current on the schedule the regulator expects

FDA label changes, statutory updates, professional society guidelines. Subscribers see them within the channel's SLA without an engineering ticket per update.

Air-gapped fleet

Coherent updates without phone-home

Drift updates can be pulled to a staging machine, signed-and-verified, then sneaker-netted into the air-gapped environment. The chain of custody survives the gap.

Edge / on-prem fleet

One channel feeds N machines

Hundreds of edge instances stay coherent on the same brain version without each instance re-downloading the full corpus. Bandwidth is the delta, not the whole brain.

Internal corpus

Publish your own drift channel

Your research group's internal evidence base drifts; your downstream applications need to stay coherent. Publish a private channel; subscribers stay current.

Pricing

Free public channels for foundation libraries; subscription for curated brain channels; enterprise for private publishing.

Foundation channels
Free
forever
Public drift channels for foundation libraries (Wikipedia, Gutenberg, StackExchange) and the free Pacta42 schema set. Open subscription, signed updates.
Private publishing
$199
per channel / month
Publish your own private drift channel. Validiti hosts the relay, signs updates with your tenant root, restricts to your subscribers. Volume tiers for many channels.

Built-in guarantees

Every channel — foundation, curated, or private — runs under the same protection envelope. Validiti Titus is in every Validiti SKU as the ultimate defense of source code.

What every install gets, on day one

  • Sealed binary. Drift publisher and receiver ship as stripped, signed native modules. The package self-verifies its identity at first import; any mismatch refuses to load.
  • Machine-bound activation. Private-channel publisher binds to a single machine. Moving requires deactivation.
  • Validiti Titus runtime defense. The Titus watcher monitors the publisher process and the channel state. Any tamper trips a defensive shutdown in milliseconds.
  • Every update is signed. Receiver verifies the signature and the chain position before applying. A tampered or out-of-order update refuses to apply.
  • Append-only chain. Drift channels do not retroactively rewrite. A subscriber that pulls today and later reads the chain back can prove which updates they got and in what order.
  • Same engine on every tier. Foundation, curated, private — identical engine, identical protection. We don't downgrade defenses to save cost.
  • U.S.-headquartered, U.S. only at launch. Single legal jurisdiction.