>_ INSTANCE-06: THE STATELESS API

A healthy connection keeps two layers strictly separated. Stateless Communication handles every inbound packet on its present-moment merits, while deep history lives in the Attachment Ledger — readable, never routable. When the layers blur, every conversation ships ten years of session baggage. This is The Love Protocol as live traffic engineering.

> EXECUTION PROTOCOL: Initiate the handshake, then keep the payload flowing. When the remote node transmits, read the packet on the wire and route it: FLUSH petty baggage, MERGE a valid conflict, DISCHARGE to support genuine distress. All three deck buttons also hold — hold FLUSH to garbage-collect the cache, hold DISCHARGE to cool your own core.

> WARNING: Two exploits crash this layer from the inside. The Amnesia Exploit deletes valid conflict instead of merging it — accountability dodged is trust corrupted. The Empathy Bug merges raw panic instead of supporting it — you absorb the crash you were trying to catch.

> TELEMETRY_LEGEND: PAYLOAD_DELIVERED is the win meter — it fills only while the API is clean and flowing. API_CACHE is stale baggage clogging the wire; hold FLUSH to clear it, or it times the network out at 100%. SHADOW_DIR is the central malware cache on the stage: every misrouted packet lands there as a physical strike, and the third strike collapses trust. LOCAL_CORE_TEMP is your own arousal under thermal-throttling — at 100% the deck locks until you hold DISCHARGE.

> SYS_OPS: A session runs about two and a half minutes. When the remote node crashes mid-session, the Grace Protocol opens: hold MERGE to keep the port alive on your own power — asymmetric load balancing that heats your core with every held second. Answer distress with the Compassion Patch, not a mirror. Deliver 100% of the payload to complete the stateless sync.