The MCP layer, visualized.

Why a card reads as one block: the zone model was a placement rule with no rendering behind it. Layer 1 (blank-line separation) as shipped, layer 2 (register — quoting the sender’s narrative) as the open proposal, plus the send envelope’s three-way 👤 collision, the composition order for a whole response, and the 48-site work-list. Records the italic trap twice-confirmed: a solo-italic line renders as a display treatment, not de-emphasis.

Why a stream doesn't read like a transfer, and the grammar that fixes it. Live MCP output from Aug 12 beside v2, object by object — plus the anatomy, the six-object field map, the rich → plain → structuredContent → resource_link → ui:// ladder, and four anti-patterns each observed in production. Plan: relay-board mcp-object-envelope-display.md.

How both harness tiers render an object that has no Code, now that DEC-025 mints one only on deliberate handoff. Single object in both states, a mixed list, the moment a Code exists, and four plain-tier anti-patterns (dash, state stamp, raw glyph, internal ID). Companion to concepts/code-presence-v1.

All transfer card states — preview, confirmed, owner, pending, series. Rich + plain mode. Spec from PR #784.

Chat-rendered card formats, 25 entries under 24 tool names — captured before the surface consolidated 43 → 21 → 12. Only relay_search and relay_sessions still exist; the rest were absorbed into relay_send / relay_receive / relay_save. Card shapes still broadly representative, names and counts not.