this.me / Tests / Semantic

Semantic graph — GTFS Madrid reactive

Services / routes / trips / stopTimes / idx as typed nodes with = formula edges. Click a node → me.explain(path) (no mutation needed). Mutate to watch k and the recomputed wave.

RUNNING Loading kernel…
GTFS Madrid semantic graph
waiting for kernel…
service route trip stopTime idx / aggregate selected dependsOn recomputed wave hop ghost
n
—
k
—
changed
—
ms
—
no mutation yet · —
Density

Ghosts only — kernel stays the demo subset.

Mutations
Wave hops
  1. Run a mutation to animate meta.recomputed hop-by-hop
.me syntax
Click a node — or run a mutation — to see the path as typed .me
—
explain() / last wave
me.explain(path) or last mutation wave meta
—

What this is

A tiny GTFS-Madrid-shaped knowledge universe runs live on the this.me kernel. Click any node to select it and call me.explain(path) — dependsOn highlights in cyan; after a mutation the recomputed wave is red. Selected node keeps a gold ring.

Honesty, matching the blog and the benchmark README: this is not an RML/RDF materialization run. CREATE is measured via explicit gtfs.idx membership slots (flip 0→1), not as “natural GTFS CREATE k=1”. Loading a larger snapshot costs more; that is not the same as recomputation after a mutation. Density adds ghost points for visual scale only — they are not wired into the kernel.

Kernel: published this.me@4.1.0 (hash-pinned). Isolation demos still pin 4.0.2; DELETE via me["-"] needs 4.1.0 for ABSENCE invalidation. Append ?local=1 to load ../../Typescript/dist/me.es.js instead (static serve from repo root).

Same demo graph as GTFS Madrid / k · human story: Madrid knowledge · JSON: gtfs-madrid-demo-graph.json · package: this.me@4.1.0