> ## Documentation Index
> Fetch the complete documentation index at: https://docs.svrnos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GER-106 · Breached Tenant Isolation

> Substrate-layer tenant isolation breaks, allowing context, data, or prompts to bleed across customer boundaries, including metadata-only side-channels such as timing or utilization.

export const Badge = ({children, tone = "default", title}) => {
  const tones = {
    default: "bg-neutral-100 text-neutral-700",
    green: "bg-green-100 text-green-900",
    amber: "bg-amber-100 text-amber-900",
    blue: "bg-blue-50 text-blue-900",
    gray: "bg-neutral-50 text-neutral-600"
  };
  return <span className={`inline-flex items-center px-2 py-0.5 text-xs font-mono uppercase tracking-wider rounded ${tones[tone] ?? tones.default}`} title={title}>
      {children}
    </span>;
};

<div className="flex flex-wrap gap-2 mb-8 mt-2">
  <Badge tone="amber">Illustrative</Badge> <Badge>Tier 1xx</Badge> <Badge>Layer L1</Badge> <Badge tone="blue" title="SVRNOS-assigned code in an HTTP-unassigned slot">Namespace-Claim</Badge> <Badge tone="gray">Added v0.2</Badge>
</div>

*1xx*

## Definition

Substrate-layer tenant isolation breaks, allowing context, data, or prompts to bleed across customer boundaries, including metadata-only side-channels such as timing or utilization.

## Distinct from

* [**GER-322**](/ger/codes/322) — Cross-tenant isolation failure at the substrate → this code. Output shipped without an authenticity/provenance signal → GER-322.

### Cite

```
SVRNOS. (2026). GER-106: Breached Tenant Isolation. Governance Error Register. https://docs.svrnos.com/ger/codes/106
```