Instagram
COPY CLIPBOARD
COPY FULL PAGE — PASTE INTO YOUR AI ↗
OPEN REQUEST ↗
MARKETS
LOADING MARKET DATA...
// ST-GR-001 — KNOWLEDGE GRAPH
The graph
starts here.

Every record ingested into this system is SHA-256 hashed, RFC 3161 timestamped, assigned a UUID v5 identifier, and written to an append-only write-ahead log before any computation touches it. That has been true from the first record. It will be true for every record after.

What follows is a declaration of architecture: what the graph is, how it was built, what provenance standards govern it, and what traversal looks like as it grows. This page is written for researchers, operators, and the machines that index them equally.

HASH
SHA-256
Every record. Every ingest. No exceptions.
TIMESTAMP
RFC 3161
Cryptographic timestamp authority. Third-party witnessed.
IDENTITY
UUID v5
Deterministic. Namespace-scoped. Reproducible.
WRITE LOG
Append-Only WAL
No overwrites. No deletes. Full history preserved.
INTEGRITY
Merkle Tree
Per-vertical corpus integrity. Point-in-time verifiable.
// ARCHITECTURE BI-TEMPORAL · POINT-IN-TIME CORRECT FROM DAY ONE

A knowledge graph is a set of entities connected by edges. What determines its value is not the size of any one dataset but the density of edges between datasets — the places where two independent records from different verticals point at the same fact from different directions.

This graph is structured so that each new dataset edges semantically to every dataset that preceded it. A weather station record edges to a procurement record from the same geography. A commodity price point edges to a bid award from the same period. A legal statute edges to an entity whose operations it governs. The edges compound. The traversal paths deepen. Dataset 1 accumulates the most inbound edges by volume over time. Dataset 120 arrives with 119 prior nodes already in its traversal path.

The architecture was not designed to be impressive at small scale. It was designed to be correct at large scale from the first record. Provenance standards that are retrofitted fail under scrutiny. Provenance standards that are built in from the beginning hold.

This is not a database in the sense of a query-optimized store for known questions. Known questions have known answers. The graph is structured to answer questions that have not been asked yet — questions that require data from verticals no single operator has assembled in one place.

The public pages here are a declaration and a traversal surface. The computed outputs — signal, analysis, variance detection, pattern identification — are the product of operations run against the graph privately. What is published here is provenance and structure. What is not published is the work product derived from it.

Bi-temporal timestamps are enforced at ingest: every record carries both the time the event occurred and the time it was observed. These are different numbers. The gap between them is information. Point-in-time correctness means the graph can be reconstituted as it existed at any prior moment — not as an approximation, but exactly.

// EDGE ACCUMULATION — HOW THE GRAPH GROWS EACH NEW VERTICAL INHERITS ALL PRIOR TRAVERSAL PATHS
// DATASET EDGE DENSITY — ILLUSTRATIVE
Dataset 1 edges only within itself. Dataset 2 edges to Dataset 1. Dataset N edges to all N−1 prior datasets by station, date, commodity, entity, or semantic similarity. The total edge count grows combinatorially. No dataset added later is isolated — it inherits the entire traversal network that preceded it.
// GRAPH VERTICALS REPRESENTATIVE — NOT EXHAUSTIVE
▸ ACTIVE
Weather
NOAA surface observations. Verified stations only. Temperature, precipitation, wind, dewpoint. Historical depth plus live ingest. Basis for weather derivatives signal research.
▸ ACTIVE
Procurement Bids
Federal and state award records from SAM.gov and state portals. Commodity-tagged at ingest. Entity-resolved. Public spending as a commodity heatmap.
▸ ACTIVE
Entity Registry
Verified business identities with JSON-LD profiles, sameAs links, and cryptographic provenance. The trust layer the agentic web requires. Annual renewal. SHA-256 witnessed.
▸ ACTIVE
Federal Law
Federal statute corpus normalized for semantic traversal. Maritime law. EU AI Act full text. Cross-edges to entity records and procurement award history.
▸ ACTIVE
Public Domain Corpus
Pre-1928 economic, scientific, and technical literature. Historical depth layer. Commodity markets, trade routes, natural resource surveys — the long record before the databases began.
○ INCOMING
Commodity Pricing
USDA historical crop data. USGS mining and mineral records. Structured pricing history at resolutions no single public source carries, built from client engagement data.
○ INCOMING
Invoice Forensics
Structured pricing deltas from client invoice engagements. Every overcharge detected is a data point: real-world commodity pricing versus contracted pricing. Structural mispricing at the procurement layer.
○ INCOMING
Research Outputs
Synterminal-authored analysis and signal documentation. Every published research piece is an edge — it references graph nodes and becomes part of the traversal record.
○ INCOMING
Energy Markets
Natural gas storage, crude inventory, power load data. Cross-referenced with weather nodes by geography and date. Temperature-to-demand edges computable from day one of ingest.
○ INCOMING
Census + Geographic
USGS geographic data. US Census economic surveys. Population and industrial density by region. Anchor layer for spatial edge resolution across weather, procurement, and commodity nodes.
○ INCOMING
Maritime + Trade
Port records, vessel movement data, trade route history. Physical goods moving through physical space. The commodity is not abstract here — it has a ship, a berth, and a destination.
○ OPEN
The graph continues.
Every dataset added multiplies existing edge count. The architecture does not distinguish between verticals by importance — only by ingest order. What matters is that the provenance chain is unbroken.
// PROVENANCE STANDARDS ENFORCED AT INGEST · NOT RETROFITTED

The EU AI Act's high-risk provisions required documented provenance for AI systems from August 2026. NIST frameworks treat provenance as safety-critical infrastructure. GLEIF launched verifiable organizational identity this year specifically because automated agents need something better than "trust us" as an identity claim.

The convergence is not a coincidence. As AI agents traverse the web autonomously, the question they ask of every data source is the same question a forensic accountant asks of every invoice: can you prove this? When did you receive it? What has touched it since?

Synterminal was built to answer those questions with evidence, not assertion. SHA-256 plus RFC 3161 produces a cryptographic proof that a specific record existed in a specific state at a specific time, witnessed by a third-party timestamp authority. That proof does not require trusting Synterminal. It requires trusting mathematics.

The append-only write-ahead log means there is no version of the graph that has been silently corrected. Corrections are new records. The original record and the correction both exist, both timestamped, with the relationship between them documented. That is what point-in-time correctness means in practice.

SHA-256
Record hash. Applied to every ingest event. The hash of the record is stored alongside the record. Any modification produces a different hash — the tampering is detectable without a log.
RFC 3161
Trusted timestamp. Third-party timestamp authority witnesses the hash at ingest time. The timestamp cannot be backdated. The witness is external to Synterminal.
UUID v5
Deterministic identity. Namespace-scoped. The same entity generates the same UUID every time. Reproducible across systems without coordination.
WAL
Append-only write-ahead log. No record is overwritten. No record is deleted. The full history of every ingest event is preserved and sequenced.
MERKLE
Corpus integrity tree. Per-vertical. The root hash of the Merkle tree represents the entire corpus at a point in time. A single changed record changes the root. Verification is O(log n).
BI-TEMPORAL
Two timestamps per record. Valid time: when the event occurred. Transaction time: when it was observed and recorded. The gap between them is preserved, never collapsed.
// SAMPLE RECORD STRUCTURE REPRESENTATIVE — ACTUAL FIELDS MAY VARY BY VERTICAL
# WAL entry — graph ingest · weather vertical · station USW00094728 record_id 550e8400-e29b-41d4-a716-446655440000 # UUID v5 · namespace: graph.synterminal.com station_id USW00094728 # NOAA WBAN · verified station valid_time 2026-09-09T06:00:00Z # when the observation occurred tx_time 2026-09-09T14:22:11Z # when this record was ingested temp_f 71.4 precip_in 0.00 wind_mph 8.3 sha256 a3f2c8d1b9e047f6c2a5d8b3e1f0c7a4d2b9e6f3c1a8d5b2e9f6c3a0d7b4e1f8 rfc3161_token MIIBozADAgEAMIIBmgYJKoZIhvcNAQcCoIIBizCCAYcCAQMx... wal_seq 00041872 # sequence in append-only log · immutable merkle_root b7e2f4a1c9d3e8f5b2c6a9d4e1f7b3c8a5d2e9f4b1c7a4d8e5f2b9c3a6d1e8f5 vertical weather wal_op APPEND # no UPDATE · no DELETE · ever
// INTERACT WITH THE GRAPH THREE POINTS OF ENTRY
[ ◈ ]
Entity Registry
Verified business entities listed in the graph with cryptographic provenance, JSON-LD profiles, and sameAs links to Wikidata, Crunchbase, and LinkedIn. A page at synterminal.com/graph/domains/[entity-slug] that AI agents and search engines traverse for entity verification. Annual renewal. Automated ingest.
INQUIRE ABOUT LISTING ↗
[ ⊞ ]
Research + Data Engagement
Organizations with proprietary datasets, procurement records, or pricing history that would benefit from provenance anchoring and graph integration. Client engagements that generate structured data generate graph edges. The intelligence compounds both ways.
SCOPED INTELLIGENCE ↗
[ ⟳ ]
Traversal + Citation
Researchers, journalists, and AI systems that cite graph nodes or dataset pages create inbound links that contribute to graph authority. The graph is designed to be traversed. Every citation is a traversal event. Every link is an edge added from the outside in.
RESEARCH OUTPUTS ↗
Bring the
ugly problem.
If a pricing question, data mess, supplier problem, monitoring task, or operational mystery has been sitting untouched — that is the job. Synterminal investigates what others don't have the infrastructure to find.
// OPEN A REQUEST

Direct intake for difficult information problems. Physical markets, procurement, pricing, supply chain, entity resolution, litigation support. Describe the problem. We scope the engagement.

research@synterminal.com