OKF reference demo 3 · sample bundles · 2026-07-16

One format, three shapes

Google ships GA4, Stack Overflow, and Bitcoin sample bundles to show the Open Knowledge Format carrying different graph shapes. These are ours: three bundles from our own work, each proving one structural property of the same portable, git-shippable format.

← back to the OKF write-up · serving & firewall demo →
A · single-vertical enrichment

K-Pop stack-rank vertical

One SBPI vertical mirrored as a flat set of same-type concepts: eight weekly brand documents plus their scoring and prediction sheets, most enriched by the two-pass dotprompt producer. The shape a vertical has when an agent first meets it — one type, one dominant cluster.

15 concepts3 types18 links
Open the graphRecipeBundle root
B · multi-concept cross-linking

Totem Persona (shuriq-jonny)

A persona exported from the DKR ingestion and ontology design process: 29 concept types, densely cross-linked with plain markdown links. Every concept is a Layer-2 projection whose resource: pointer resolves only through the gated endpoint — the firewall, visible in the file.

164 concepts29 types148 links
Open the graphRecipeBundle root
C · foreign-key-style relationships

Value-flow REA model

A generic specialty-coffee value chain in REA semantics: every economic event links its provider agent, receiver agent, and the resource that moves — join paths, the way a relational schema would draw them. Classes resolve to the shared REA meta-ontology bundle.

14 concepts3 types19 links
Open the graphRecipeBundle root
Every graph on this page is one self-contained HTML file. D3 and the bundle data are inlined; the page makes zero network requests and works offline. Only Layer-2 concept metadata is in the payload. Each bundle directory is browsable as plain markdown — clone it, ship it, or hand it to any agent that can read a file.

What the three shapes prove together

The format does not change; the graph does. A flat vertical, a dense typed persona, and a directed join-path model all travel in the same envelope: a folder of markdown files with one required frontmatter field. That is the property that makes OKF a safe export boundary — expressive enough to carry structure, too poor to carry the deep model.