Human-State Session Protocol v0.1 — Structural Declaration: Consent-Based Session Structure for Human-State-Aware AI Mediation

Human-State Session Protocol v0.1 — Structural Declaration defines the session structure for research-stage Human-State-Aware AI Mediation and Dyadic Human-State Mediation Benchmark operation. The protocol does not define a clinical intervention, therapy, counseling, legal mediation, conflict-resolution service, surveillance system, emotion-recognition system, CAIS conformance document, or Sal-Meter validation document. It defines how a bounded, consent-based, session-limited interaction opens, proceeds, evaluates, terminates, closes, and records itself. The protocol fixes the operational sequence: Session Creation → Consent Confirmation → Packet Availability Check → Baseline State Summary → AI Output → Post-Output State Summary → Human-State Delta → Recovery Gate → Termination Gate → Session Closure → Audit Log. A valid Human-State Session does not begin silently. It begins with consent, runs only inside session scope and packet permission, uses only valid Human-State Packets and Human-State Summaries, and closes through a recovery gate or termination gate. The protocol distinguishes private cue, shared mediation output, pre-output state summary, post-output state summary, Human-State Delta, recovery gate, termination gate, session closure, audit log, and deviation record. It prohibits raw human data exposure, diagnostic claims, therapeutic claims, emotion-reading claims, human scoring, relationship verdicts, blame assignment, clinical recovery language, CAIS compliance claims, Sal-Meter designation claims, and silent continuation after closure. This document is subordinate to the Human-State Mediation Boundary Standard v0.1, the Human-State Packet Minimal Data-Sharing Standard v0.1, and the Dyadic Human-State Mediation Benchmark Charter v0.1. It fixes how the boundary, packet, and benchmark layers become auditable inside an actual session. A session is not valid because the AI speaks. A session is valid only if it can open with consent, operate inside permission, close through gates, and leave an audit trail.