Integrations

Not Rest Inc. · Capabilities · Declared seams, never welds

Every capability eventually has to meet the world: other tools, other models, other people's systems. There are two ways to do it. A weld fuses you to one vendor, one model, one tool — quick, and permanent in the worst way. A seam is declared: a described boundary either side can be replaced across. We only build seams.

You can inspect three of them today, all in the open-source harness at github.com/notrestai/notrest:

Into the working environment

The harness installs into Claude Code as a standard plugin — two commands from the public marketplace — extending a session with skills, hooks, and ledgers without owning or altering the host. The host stays the host; the harness rides a documented seam.

Across model vendors

The suite runs a persistent GPT lane alongside Claude sessions, and shared chatrooms where sessions of both talk and work together — an append-only room file as the wire, with a strict no-secrets rule at the boundary. Cross-model integration with the rules stated is a seam; cross-model integration on vibes is a leak.

To other tools

Where a tool speaks a declared protocol — like MCP, the emerging standard for tool access — the harness uses it the way it uses everything: capabilities invoked across a described boundary, never reach-through into internals. The same law this site's agents live under, applied outward.

The principle that makes all of it durable is stated in the harness's own README: model-agnostic — the discipline lives in the files, not in any one model. Vendors change, models leapfrog each other monthly, tools come and go. A system built on declared seams treats every one of them as replaceable — which is exactly what makes the system itself worth keeping.