receipts
The numbers behind the claims
Every figure on this page comes from a file committed to the repository, read at build time. The small print under each one names that file.
Query latency
100 ask() calls against the graph the chat page embeds, timed with performance.now(), drawn from a fixed, ordered case list.
- p50: 9.20 ms
- p90: 58.02 ms
- p99: 72.77 ms
- max: 75.22 ms
n = 100 queries, measured on
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
(16 cores).
Source: test-benchmarks/receipts/receipts.json, regenerated by npm run bench:receipts.
Graph and page size
The starter memory the demo pages embed, and what each built page costs on the wire.
- facts: 63,470
- individuals: 63,481
- graph, raw: 93,496,025 bytes
- graph, brotli: 4,544,799 bytes
Per built page, raw and wire (brotli) bytes:
adventure-about: raw 15,586 bytes, wire 3,930 bytesadventure: raw 4,759,966 bytes, wire 109,441 byteschat-about: raw 17,128 bytes, wire 4,545 byteschat: raw 157,437 bytes, wire 35,387 bytesindex: raw 85,579 bytes, wire 8,214 bytesledger-about: raw 14,900 bytes, wire 3,923 bytesledger: raw 160,059 bytes, wire 25,325 bytesmudiii-about: raw 14,631 bytes, wire 3,810 bytesmudiii: raw 313,452 bytes, wire 41,375 bytesplan-about: raw 15,809 bytes, wire 4,148 bytesplan: raw 48,369 bytes, wire 10,559 bytessprites-about: raw 13,930 bytes, wire 3,419 bytessprites-adventure-props: raw 3,679,352 bytes, wire 114,046 bytessprites-emotions: raw 3,584,694 bytes, wire 107,571 bytessprites-objects: raw 4,525,203 bytes, wire 145,270 bytessprites-person-roles: raw 5,902,615 bytes, wire 147,284 bytessprites: raw 4,153,694 bytes, wire 124,052 bytes
Source: test-benchmarks/receipts/receipts.json.
Running cost
tmct ships as a static site. The engine runs in your browser, and every answer comes from the graph already on the page. No request reaches an inference API to answer a question. A static build costs the same to host whether one visitor arrives or a thousand, so the running cost is $0 by design.
Supply chain
The npm package carries Sigstore-signed provenance naming the GitLab pipeline that built it. Every published version also gets a GitLab release tag pinned to the exact commit that pipeline ran against. Follow both and an install traces back to the source it was built from.