Things easier to show than to describe. Three of these are the real Go tool compiled to WebAssembly and running in your browser — not a reimplementation of it. The ranger demo is different: it is a report the Go tool generated, with the incident data embedded. Nothing is uploaded.
CLAUDE.md, .cursorrules
or any instruction file and watch the characters your font refuses to draw
appear: zero-width spaces, bidi overrides that reorder text on screen, and
Cyrillic letters wearing Latin faces. It runs
paladin itself, compiled to
WebAssembly — not a reimplementation.gen_ai.* schema with what the translation cost recorded on the
result. Then two pages that go further: the
inspector takes one
attribute at a time and says which source key produced it, what evidence the
reading turned on, and what it could not carry; and
what translation costs
draws the measurements across all six dialects — the scoring race that picks
a dialect, and where 105 attributes with no home in the conventions end up.
Where it goes in your
pipeline draws the three places it can run, including the one where it
emits config for a Collector that has never heard of it.
How it works, in
pseudocode.A public, live view of LLM gateway traffic: which team, which model, what was redacted, and what it cost. The normalization underneath it exists; the view does not.