DOCUMENTATION
Use AI to need less AI.
Coldworks reads the traces your agents already produce, finds the judgments they keep re-buying, and compiles the repeats into deterministic code you own and you run. These docs cover the part you touch: getting your traces in, running the audit, and reading what it finds.
Quickstart
One command, no signup, no install step. See a full audit on sample data in
under a minute.
START HERE →
Connect your traces
Langfuse, LangSmith, or OpenTelemetry. A batch export is a file transfer, not
an integration.
THREE STEPS →
The audit CLI
Every command, flag, and file the audit reads or writes — and what never leaves
your machine.
REFERENCE →
The shape of it
Everything below runs on your machine. Coldworks hosts one thing: a read-only registry page for figures you choose to publish. It cannot receive your traces, your documents, or your code — by architecture, not by policy.
your trace store ──export──▶ a file on your disk ──coldworks-audit──▶ a report on your disk nothing crosses the boundary. the report is yours to forward, or not.
What is real right now
These docs hold themselves to the same rule as the audit: states are answers.
| Claim | State |
|---|---|
| The connection flow in these docs is the front-door design under review. | DESIGNED |
| The recovery engine behind the audit exists and is deterministic. | BUILT · UNRELEASED |
coldworks-audit is installable. | NOT YET |
| Validated against a real Langfuse / LangSmith export. | GATED · NEXT STEP |
| Anything in these docs uploads your data. | NO — BY DESIGN |