trie-trunk

Data Lifecycle

Ingest events once. Replay object changes, investigate collected data locally, and query compact summaries without loading every event.

ServerBrowser
Select a StageData Shapes Are Schematic
Server / Ingress

Accept the Change

Data seeds are Trie-Trunk’s implementation of PIL. Each seed arrives under a negotiated Definition. The seed journal supports recovery; recent seeds stay in native memory for live search and replay.

Rejected data seeds go to Lost Events with their original content.

Data Seed ViewExample Data
payment / transactionsData Seed
event_idUUIDv7
idTransaction UUID
revision_id17
stateauthorized
Append to .seedAvailable in Memory

Platform Taxonomy

Caches in the trunk.
Services branch out.

The Trie-Trunk Taxonomy Caches are hollows within the trunk. The prod cache branches into payments and identity services. Payments branches into transactions and refunds resources. Transactions branches into info and error levels. The info level branches into read and write access. A test cache has a separate preview service. The expanded path is Trunk, prod, payments, transactions, info, write. Trunk prod test payments identity preview transactions refunds sessions info error read write
Example paths · One cache expanded

Select a Tier to Highlight

Separate working spaces, such as prod, test, and sand. Each has its own hollow in the trunk.

An Event’s PlaceTrunk › prod › payments › transactions › info › write

Analytics

Pre-Computed
Columnar Aggregates

Query the aggregate, not every event. Counts, errors, and numeric statistics are computed ahead of the view and collected independently of event detail.

Monthly ViewIllustrative Aggregate Views
JanDec
5-Minute Base Granularity

Combine stored aggregates for broader time views. Collect individual events when the investigation needs their detail.

Retention

Give Each Branch
Its Own Budget

Keep the depth where it matters. Explore different storage allocations for services, resources, levels, and access.

Hollow = QuotaLarger Quota → Larger Hollow
Selected Access Branch

prod / payments / transactions
debug / read

192 GiB
32 GiB256 GiB

192 GiB Storage Quota

Explore a storage budget for the selected scope.Explore Cache Quotas in Snoot ↗

Query Paths

Time, object identity, and text each have
a useful way into the journal.

Time & Text

Bound a search by time, then refine by fields or text. Collect matching seed packs for local investigation.

Time Trie + Tantivy

Object Replay

Follow one object’s revisions. The optional collection index supports history and replay without rebuilding the full object.

collection.idx → Writes

Analytics

Render counts, errors, and duration distributions from summaries. Daily totals also feed weekly, monthly, and yearly rollups.

.sum → Analytic Columns

Retention is configured per resource and branch. Completeness and lost events remain visible. Scheduled reports and external alert delivery are still planned.

Data Seeds / Shared Schema

Data Definitions

Define field positions, types, and dictionaries once. Data seeds share that definition and can carry complete state or a single changed field.

Trie-Trunk data definitions are an implementation of PIL Definitions.

A Data DefinitionJSON View of CBOR
{
  "definition": "payment/transactions",
  "pil": 0,
  "version": 0,
  "fields": [
    { "name": "id",           "type": "UUID" },
    { "name": "revision_id",  "type": "U16"  },
    { "name": "state", "type": "STRING",
      "values": ["pending", "authorized", "captured"] }
  ]
}
A Changestate: authorizedOmitted fields remain omitted.

Storage Measurements

1,000,000 synthetic events. 30 days. Five resources.
Indexes, journals, and metadata included.

168.41 MB

Total logical storage

Read the Benchmark
Pods
44.78 MB
Tantivy
80.16 MB
Tries
3.57 MB
Indexes
28.53 MB
Summaries
4.88 MB
Journals & Other
6.49 MB

153.6 KB median daily summary transfer across the fixture’s resources.

168.4 bytes/event including optional collection indexing and Tantivy in this fixture.

Expanded JSONL: 428.60 MB. Gzip-6 JSONL: 25.44 MB, without equivalent search indexes.

These are development measurements, not production guarantees. The linked report includes allocation, coverage, and format tradeoffs.

Front-Facing Snoot Anteater
Snoot

Search & Investigation

Search the journal, inspect a change, and look at the pattern. Snoot brings the detail and the summaries into the same research session.

Open Snoot About Snoot