One model, any record
Records can be rewritten.Memory cannot.
Palynth is the memory layer for everything on record. A capsule proves the document; a ledger proves its history. Contracts, ledgers, claims, buildings: every decision, every cause, verifiable in your browser.
A legal agreement, a journal entry, an insurance claim, a door opening: the same six beats on the same model
17
historical events
simulated · real engine
10
source records
simulated · real engine
8
downstream impacts
simulated · real engine
17/17
events verified
recomputed at build
76
chained events
real production · anonymized
Adversarial by design
Prove the history. Protect the record.
This is the production kernel running in your browser. Tamper with any event and watch the chain break where you touched it.
76 events · sha256 each · chained in order
76 events · 1 project root · awaiting verification.
Outcomes, not features
Ask the record anything.
01 · Trace why
01 / 04Ask why, get the decision chain.
Follow any condition backward through every decision that produced it, each step carrying the record that caused it. A question that took a week of archaeology becomes a query.
8 causal events · 1 explanation
02 · Blast radius
02 / 04See what a change touches, before it does.
Propagate a change through the graph and get every dependent record back, with the engine's reasoning attached to each hop.
1 change · 8 impacts · 1 conflict
03 · Time travel
03 / 04Return to any state the record has ever held.
State is reconstructed from the event history at every revision, not from saved snapshots. The identity never moves; the answers stay honest.
5 revisions · 1 permanent identity
04 · The passport
04 / 04Everything known about one thing, in one place.
Identity, current state, relationships, approvals, dependencies, verification: the same eleven sections for a door, an air handler, or a contract.
11 sections · any record type
Palynth in action · simulated project, real engine
Not version history. Memory.
One kernel, many worlds
Any industry that runs on records.
The kernel stores records, events, causes and proofs. It does not know what a clause, a journal entry or a door is. Change the nouns and nothing else changes.
01
Legal
Future · same kernel
The clause that changed between draft 14 and signature.
Every redline an event, every version hash-chained. Who altered the indemnity cap, when, and which email caused it: a query, not a discovery motion.
02
Accounting & audit
Future · same kernel
The reversal that explains itself.
A journal entry points to the invoice that caused it. An auditor verifies the ledger's history without having to trust whoever keeps the ledger.
03
Insurance
Future · same kernel
The estimate that stopped matching itself.
Photos, adjuster reports and payouts connected to one claim. Alter a record after the fact and every event built on it stops verifying.
04
Construction
Running today · real engine
The order that no longer matched the design.
Hardware set HW-17 became HW-21 while PO-1847 still pointed at the old spec. The graph flagged the conflict and named the RFI that caused it. This exact scenario runs live in the demo.
05
Clinical & lab
Future · same kernel
The amendment that cannot hide.
A record changed after database lock is not a footnote. It is a visible event with a timestamp, an author and a cause.
06
Manufacturing
Future · same kernel
The recall scoped in one query.
One suspect batch of fasteners. Every assembly that depends on it, every unit that shipped, in seconds instead of weeks.
07
Energy & infrastructure
Future · same kernel
The weld record that outlives the contractor.
Commissioning data, inspections and repairs bound to the asset for its forty year life, not to a vendor's server.
08
Government & public records
Future · same kernel
The permit that cannot be backdated.
Approvals, variances and inspections in one provable sequence. Nobody edits yesterday, and everybody can check.
Construction runs on the engine today. The rest is the same kernel pointed at different records, labelled future because it is.
From the engine · real production output · anonymized
No testimonials. Engineering proof.
Public-safety station · U.S.
2026-08-06- 49
- openings
- 18
- sets
- 9
- RFIs
- 76
- events
Municipal fire station · 51 openings
2026-08-26- 51
- openings
- 30
- sets
- 19
- RFIs
- 100
- events
canonical.ts · quoted from the engine
One deterministic byte form. Keys sorted, undefined dropped, numbers exact. The only place bytes are decided.
export function canonicalize(value: unknown): string {
if (value === null) return "null";
switch (typeof value) {
case "string":
return JSON.stringify(value);
case "number":
if (!Number.isFinite(value))
throw new Error("non-finite number in canonical form");
return JSON.stringify(value);One event missing
First the built world. Then everything that runs on records.
Your records already hold the history. Palynth makes it provable.
1007 / 1008 events verified · one missing · sha-256