data does not move.
inseam indexes your email, files, chats, and records where they already live. the network syncs addresses and small envelopes — never content. there is no second silo to trust or pay for.
shipping today.
all your context,
accessible anywhere.
content never moves. addresses do.
access is first-class.
an outside requester proves a property — email:you@example.com — and can discover exactly the sources carrying it. no user database anywhere; relevance and permission are the same question.
designed; the boundary is not built yet, and we say so.
plugins meant for ai to build.
everything the node does is a sandboxed plugin on a small typed seam. when a connector is missing, your own agent writes it and mounts it safely, minutes later — the first shipped plugin was written by an agent.
shipping today.
discovery is a ladder, not a dump.
query returns ranked addresses. expand and scan pull fragments from promising ones. fetch retrieves a full source only when it earns it — an agent gets progressively closer instead of twenty chunks up front.
$ inseam query "sync design decisions"
1 inseam://fs/~/ws/inseam/design/sync.md envelopes sync; content stays
2 inseam://fs/~/ws/inseam/design/plugins.md two tiers, one seam
3 inseam://gmail/thread/18f2c40a1 re: node discovery ladder
$ inseam expand 1
… addresses and their envelopes sync to every node; content stays put …
$ inseam fetch 1
design/sync.md — fetched from its hostthe shape of a real session; paths are illustrative.
open source. extend it indefinitely.
the core is small and stays small: a kernel that runs plugins, and plugins for everything else. no company roadmap caps what it reaches — the community and your own agents write the long tail, and one conformance harness gates every install. the hosted node is an ordinary node with no special powers.