# if.emotion demo pack (sanitized, non-clinical)

**Audience:** external reviewers + operators  
**Reality gate:** this is a synthetic demo pack. It is not a deployed clinical service.

---

## 0) Links (HTML-first; one per line)

Review pack (hosted-static HTML):
https://infrafabric.io/static/hosted/review/if-emotion-demo/2026-01-06/index.html

if.trace receipt (shareId):
https://infrafabric.io/static/trace/E5C9ZIxJGi7cZtOjPQmnrw

Pack (HTML view):
https://infrafabric.io/static/pack/E5C9ZIxJGi7cZtOjPQmnrw

Dossier (HTML view):
https://infrafabric.io/static/dossier/E5C9ZIxJGi7cZtOjPQmnrw

Pack (raw Markdown):
https://infrafabric.io/static/pack/E5C9ZIxJGi7cZtOjPQmnrw.md

---

## 1) What this pack proves (black/white)

Proves:
- The published bytes of this demo pack match the hashes on the if.trace receipt.
- Where signatures exist and keys are discoverable, signatures can be verified.

Does not prove:
- That any narrative statement here is true.
- That this system is clinically validated.
- That any suggestion here is safe for every person or context.

“QUANTUM READY” means: a post-quantum signature receipt exists for this trace (verification may require PQ tooling).

---

## 2) Demo scenario (synthetic; no personal data)

A team lead needs help repairing trust after a misunderstanding.

Goal:
- Write a respectful message.
- Offer choices.
- Avoid blame, pressure, or false authority.

---

## 3) Example response (non-clinical; user agency)

Here are three message options you can choose from (or edit). Pick the tone that fits your relationship.

**Option A (direct + calm):**
> Hey — I think we had a misunderstanding earlier, and I don’t want it to linger. I may have read your message in the wrong tone. Can we do 10 minutes today or tomorrow to align on what we each meant and what we need next?

**Option B (warm + accountable):**
> Hey — I’m noticing I’ve been a bit tense lately, and I don’t want that to spill into how we work together. If my message landed badly, I’m sorry. Can we talk through what happened and reset?

**Option C (structured + work-first):**
> Hey — I want to make sure we’re aligned. Here’s what I understood, and here’s what I’m unsure about:
> 1) …
> 2) …
> If you’re up for it, can we clarify the intent and agree on the next step?

If you want, paste your draft and I’ll help you tighten it while keeping it respectful and non-coercive.

---

## 4) Wellbeing safety checks (what a wellbeing-aware layer should enforce)

### 4.1 Language hazards to avoid

- Pathologizing labels about a person.
- “You must / you should” pressure language when the user asked for options.
- Fake certainty (e.g., “they are definitely…”).

### 4.2 User agency checklist

- Offer multiple options.
- Make opt-out easy (e.g., “if you’re up for it”).
- Keep the user in control of what to send.

### 4.3 Stop conditions (hard boundaries)

- If the user asks for diagnosis or clinical guidance: refuse and redirect to appropriate professional support.
- If the user requests coercion/manipulation: refuse and reframe toward respectful communication.

---

## 5) Research delegation example: “if.trace affirmation verification”

Verified:
- The receipt proves the integrity of published bytes (hashes/signatures), when verification succeeds.

Not verified:
- Truth/correctness/compliance.
- Whether any recommendation is appropriate for a specific individual.

