The catalog is the product
A thing is a reference, not the bytes. Originals stay in the resource they came from; things holds the reference, the extracted metadata, and the analysis.
things
one searchable index across everything you own...
Drive search only searches Drive. Gmail search only searches Gmail. things searches across all of them, with analysis attached, and can hand the bytes back as an export or a local copy.
One adapter, every vendor
A type is a dialect, and it decides how much code exists. One s3 adapter serves AWS, R2,
B2, Wasabi, MinIO and Garage — because they all speak the same one.
The endpoint is the interface
POST /mcp — eight tools, one bearer token per call. The token decides which tools exist, so
a tool outside your grant is absent rather than refused.
It survives a deploy
Every operation touching an unbounded number of things checkpoints through job-iteration, so a sync or an export resumes at its cursor rather than starting over.
Running itServices, database, two tenants, in about three commands.
The four movementsSync, analyze, search, export — everything else is access layer.
ThingsWhy a reference, and what two-valued deletion means.
ResourcesAttach class, type, capability — the three orthogonal axes.
TenancyFive layers of isolation, and the two that have traps.
MCP toolsAll eight, and the grant each one needs.