LoomSignal
Docs← Back to site
Overview

How LoomSignal works

LoomSignal turns the scattered output of your tools into one governed context layer, and serves it to every AI over MCP — so each agent acts from the same trusted reality. It runs entirely on your own infrastructure.

Your tools
NotionJiraGitHubFigmaPlaywrightGitLab CI
connectors push raw signals over MCP — on your infrastructure
One governed substrate
BRONZEEvery signal, captured as an append-only observation. Nothing is thrown away.
SILVERThe many names for one real thing are reconciled into a single entity.
GOLDGoverned, trustworthy context — promoted only through the gate.
Governance gate · provenance-checked · nothing silently overwritten
served through the trusted read-gate
Every AI acts from the same context
READ-GATEServes governed context; withholds or flags anything contested — never blends conflicting claims.
MCPOne open interface: query, search, fetch, and cite — with full provenance.
YOUR AGENTS
Claude CodeCodexSlackCI/CDDashboards

One substrate, three tiers

Every signal your tools produce is captured as an append-only observation (bronze) — nothing is overwritten or lost. Those observations are reconciled so the many names for one real thing become a single entity (silver). Only what passes the governance gate is promoted to governed context (gold).

Governed, not guessed

Promotion runs through a single gate that records a verifiable provenance chain and never silently overwrites a prior fact. When two sources disagree, the conflict is kept as an explicit signal — and the read-gate withholds or clearly flags contested context rather than blending it. Everything is traceable back to its source.

Served over MCP, on your infrastructure

Agents don’t query a private API — they read through MCP, the open interface, and get cited, governed answers. The whole substrate lives inside your own environment: sources, credentials, and knowledge never leave. Search keeps working even fully offline.

Architecture Installation Operation