Documentation navigation
Public documentation
Impact Boundary Labs docs
Public documentation for Impact Boundary Labs: why the boundary exists, what product surfaces exist today, how the architecture works, and where reference implementations and extension material live.
Start with the story and the architecture: why the boundary exists and how the Core decides. MCP Boundary, the current product, has its own short docs section, and GitHub Gateway, Impact Room, and adapter-building material live under labs and reference.
Start here
Architecture and security model
- Core decision layerUnderstand what Core owns: explicit inputs, observed state, decision, admitted work, and outcome.
- Open boundary contractReview the public interface and vocabulary used by the Core decision layer.
- Core how-it-works referenceUse the reference path when you need deeper detail than the narrative How it works page.
Labs and reference implementations
Build and extend
- Build your own adapterAdvanced path for teams that want to connect a narrow target system behind the same boundary split.
- What an adapter implementsSee the smallest pieces an adapter has to provide without turning adapter work into the main entry path.
- TerminologyUse the glossary only when the product-level story needs deeper reference terms.
Product: MCP Boundary
- MCP BoundaryUse the short public docs for setup, profiles, policy examples, tested paths, scoped Gmail setup, and FAQ.
- Getting startedImport an existing MCP server from the dashboard, copy the Agent Config back into your MCP client, and verify Activity.
- Policy examplesSee how visibility, allow/block, result limits, argument rules, runtime limits, and state binding are expressed.
- Current scope and limitsRead scoped evidence and explicit non-claims before evaluating a provider or downstream server path.
- GlossaryLook up product terms: profiles, dashboard and operator tokens, rule fields, scope and stale-state binding, and credentials.
- LimitationsRead the single reference for what MCP Boundary is not, does not claim, and cannot automatically see.
- MCP Boundary roadmapRead the local release focus, planned approval, email verification, setup, dashboard, packaging, compatibility, and non-claim work.