Runtimes
The same registry served over a standard-input transport, a streaming HTTP transport, and an edge runtime.
Three transports, one tool registry. The standard-input entry is the path a desktop client launches; the HTTP entry is stateless, constructing a fresh server and transport per request, which is the shape a serverless deployment requires; the web handler bridges the same registry into an edge runtime.
Five separate agent clients have working install paths against the same surface.
- The same registry is served over a standard-input transport, a streaming HTTP transport, and an edge runtime.
- Documented, working install paths exist for five separate agent clients — this is a multi-client surface, not a single-vendor integration.
- Configuration is environment-supplied, so pointing the surface at a different set of jurisdictions is a configuration change rather than a release.
How it works
Configuration is supplied by the environment, so pointing the surface at a different set of jurisdictions is a configuration change rather than a release.
The server holds no database. Query tools read published per-jurisdiction tables directly over HTTP by content address, range-reading the columns a query needs rather than downloading a dataset, which is why a consumer can run their own copy against the same published data instead of depending on a shared backend.
Every fetched range is hash-verified against its content address before it is returned, and a mismatch throws rather than being served.