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.
Three statements, no jargon.
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.
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.
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.
Three classes of channel. Same protocol, same signing, same receiver.
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.
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.
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.
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.
Three public foundation channels. Each emits signed, append-only updates. The timeline below is what a live subscriber sees: new entries arrive every few seconds, every one signed by the channel's Ed25519 root, every one verified locally before the receiver applies it.
Where a drift channel solves a problem static distribution cannot.
FDA label changes, statutory updates, professional society guidelines. Subscribers see them within the channel's SLA without an engineering ticket per update.
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.
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.
Your research group's internal evidence base drifts; your downstream applications need to stay coherent. Publish a private channel; subscribers stay current.
Free public channels for foundation libraries; subscription for curated brain channels; enterprise for private publishing.
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.
