Illustrative product demonstration
See how the evidence develops.
Replay incoming observations and inspect how an asset record changes. This synthetic insurance example illustrates an earlier platform design; it is not live traffic or a production capability assessment.
One application on the record, as it looks in the product.
The first use is a bounded review of the assets you already insure. The contract at the top scopes the chain to your schedule, the policy period and a knowledge cutoff. Each column is one day of one asset's record; each row is a family of evidence that sticks to it. The answer on the right keeps its basis, method, coverage and time, and the record stays maintained after the review.
MV North Reach
335 batches in window · 8 in view · identity consistent in 335 of 335 · 1 finding since 19 Aug
| whole windowOct 2025 → Aug 2026 | 12 → 19 Aug · expanded below | |||||||
|---|---|---|---|---|---|---|---|---|
| asset batchone day | 12 Aug12 to 15 Augv1 · sealed | 13 Augv1 · sealed | 14 Augv1 · sealed | 15 Augv1 · sealed | 16 Augv1 · sealedv2 · revised | 17 Augv1 · sealed | 18 Augv1 · sealed | 19 Augv1 · sealed |
| arrivalsreceived this day | 0 receivedexpected | 0 receivedexpected | 0 receivedexpected | 0 receivedexpected | 58 receivedposition · sat | 49 receivedposition | 57 receivedposition · sat | 48 receivedposition · imagery |
| movementAIS coastal · speed, course | no report | no report | no report | no report | 11.6 kn · 231°3 sensors | 12.1 kn · 228°3 sensors | 9.8 kn · 240°3 sensors | 11.2 kn · 233°3 sensors |
| satellite AISpasses | no pass | no pass | no pass | no pass | no pass02:14 · 6 poslate · stuck to 16 Aug | no pass | 03:40 · 5 pos+ 6 for 16 Aug | no pass |
| imageryscenes | none | none | none | none | none | none | none | hull scene |
| declarationsregistry · trade · insurance | ||||||||
| relationshipsin effect · validity | ||||||||
| contextsea state · region | none | none | none | none | sea state 2 | sea state 2 | sea state 2 | sea state 2 |
| associationidentity state | no report | no report | no report | no report | consistent | consistent | consistent | consistent |
| batch versionssource batches included | v1 · sealed | v1 · sealed | v1 · sealed | v1 · sealed | v1 · sealedv2 · +6 late (sat) | v1 · sealed | v1 · sealed | v1 · sealed |
| methodsfindings · basis | ||||||||
chain r3-a1 v2 › MV North Reach › query result
No finding in effect yet
Outside declared trading area
- basis
- 212 positions · 3 coastal sensors · 2 satellite passes · event 16 Aug 04:10 → 19 Aug 22:35
- coverage
- 12 → 15 Aug: no observation · coastal out of range · no satellite pass · recorded as gap, not inactivity
- declared
- schedule rev. 3 · Med and Black Sea, excl. listed areas · filed 28 Jul 2025 · valid from 01 Oct 2025
endorsement · expected · not received - witnesses
- AIS coastal · 3 sensors · independent
satellite AIS · 2 passes · independent - time
- event 16 → 19 Aug · received 16 → 18 Aug · recorded 18 Aug 06:00 · knowledge ≤ 15 Sep 2026
- versions
- v1 sealed · v2 opened 18 Aug 06:00 by 6 late satellite positions sticking to the 16 Aug batch · v1 preserved
columns = asset batches, 1 day · hollow = expected, not received · amber = declaration · blue = position · green = relationship in effect · red = conflict only
- Observations do not independently establish insurance coverage, causation, or future loss. A deviation is a prompt for review, not evidence of intent.
- Not observed is recorded as a gap, never as inactivity.
- A declaration is evidence too, kept beside the observations.
- The next question is a query on the same chain.
Where we are
Observation archive, identity resolution and activity analysis operate on the historical record today. The evidence record, revision handling and delivery integrations are being built with a small number of design partners.
How the record is kept
A store of batches, cut by a contract into a chain you compute on.
Every report sticks to the interval it describes and enters the record when it arrived. A batch is sealed once; a late arrival reopens it as a new version and the prior version is preserved. Nothing after the knowledge cutoff leaks into an earlier view. The review above is one contract over this store; the next question is another query on it.
- Source
- Trace an assessment to its supporting observations.
- Time
- Distinguish when events occurred from when they became known.
- Uncertainty
- Keep collection gaps and conflicting evidence in view.
- Revision
- Preserve earlier assessments as the record develops.
Preserving a record does not guarantee its accuracy: contradictions, collection gaps, and uncertain inferences stay in the evidence rather than disappearing into a single unexplained score.
Evidence ledger, replay 10:54 to 11:05 UTC: one-minute batches, five streams and three pinned assets, a knowledge cutoff, three late arrivals and one conflicting declaration.