2 posts tagged with "visualization"

Loom started as a knowledge graph of documents. Then the reference adopter said, more or less: that's a beautiful picture of my paperwork, but my daily question is "where are we?" against the system — the components, the layers, what's built and what's still owed. So Loom grew a second surface: the architecture as a building, authored once and rendered as both a 2D plan and a 3D exploded model, with a status overlay that lights components up. The overlay for technical debt came up empty on the first run. There was plenty of debt. The overlay just had no idea which components carried it — and getting that right took three tries, two of which looked finished.

The walking skeleton shipped fast and looked great: a force-directed graph of every StrayMark document, colored by type, rebuilding in the browser within a second of saving a file. Then we pointed it at a real corpus — Sentinel, 395 references — and 330 of them dangled. Not because the documents were broken. Because they referenced each other the way humans write, not the way a naive graph builder matches. The render was a weekend. Making the edges land took the rest of Loom M1's follow-ups, and it changed what a "broken link" even means.