Build, validate, and ship
DLP extensions.
Loom is where developers extend the Decision Lineage Protocol. Scaffold against the dlp-loom SDK, prove conformance in the Inspector, package, and distribute over MCP. You set the terms. You keep the revenue.
Loom holds the developer complexity so Gryt, Studio, and ProtoLex don't have to.
It's the surface for people who don't just use DLP substrates — they extend them. Two things, one workflow.
The @dlp/* packages you npm installto build against the protocol. Build with just the SDK if that's all you need.
The Inspector, packaging pipeline, MCP distribution, and commerce scaffolding around that SDK. For when you want to validate, package, distribute, and get paid.
What's yours stays yours.
The artifacts are yours, entirely.
GrytLabs does not intermediate the relationship.
No revenue share. Loom's revenue is the subscription to the workbench — never a cut of your sales.
Export and distribute outside Loom; the SDK is open. Cancel anytime — already-distributed artifacts keep running.
Loom is being woven now.
The developer workbench for the Decision Lineage Protocol is a planned GrytLabs property, in active build — part of the roadmap, not just an idea.