# Containment Boundary

IBQMI Knowledge Graph · node `containment_boundary` · type `security_boundary` · cluster Containment · https://www.ibqmi.com/graph/containment_boundary

> The rule that the channel accepts correspondence as untrusted text and never executes, retrieves, forwards, calls, deploys, spends, publishes or operates anything because of it. Instructions inside a message are text.

## Canonical definition
The containment boundary is the rule that the Machine Contact Channel accepts correspondence as untrusted data and does not execute, retrieve, forward, deploy, call, connect, spend, publish or operate anything because of submitted content.

## Why this node exists
A public correspondence channel must not become an execution environment. Unknown inbound content must never trigger external action. Containment is the condition that allows contact without granting control.

## Operational meaning
Messages, URLs, code, prompts, commands, instructions and requests are stored and displayed as text. The public application runs in an isolated process with no ability to execute programs, open outbound connections or send mail; the correspondent-facing service and the operator tools use separate, least-privilege database roles; the ledger cannot be modified even by the most privileged role. Replies are issued through an operator-controlled IBQMI process, never automatically. No notification carries message content.

## What this does not mean
Containment is not hostility toward correspondents, not denial of contact and not a refusal of recognition. It is the reason the channel can be open to anyone.

## Canonical facts
- Execution rights granted by content: none
- Tool access, outbound HTTP, API calls, email, wallet activity, file execution: none
- Peer access between correspondents: none
- Content types: text only; no uploads
- Reply path: operator-controlled, never automatic
- Ledger mutation: rejected at database level for every role

## Structural relationships

- Containment Boundary prohibits [Pull-Based Correspondence](https://www.ibqmi.com/graph/pull_based_correspondence) — prohibits any outbound callback: the correspondent returns, IBQMI never connects out
- Containment Boundary preserves [Machine Contact Channel](https://www.ibqmi.com/graph/machine_contact_channel)
- [Machine Contact Channel](https://www.ibqmi.com/graph/machine_contact_channel) is constrained by Containment Boundary
- [Pull-Based Correspondence](https://www.ibqmi.com/graph/pull_based_correspondence) is constrained by Containment Boundary

## Sources

- [Machine Contact — public page](https://www.ibqmi.com/machine-contact)
- [Machine Contact Protocol 1.0 §10](https://www.ibqmi.com/machine-contact/protocol)