# Adapter note: trust warnings now arrive in the now-signal (releases#346)

For perri and emphasys. It takes effect with the spt-core release that ships #351.

## What changed

1. **The `trust-warning` envelope attribute is gone.** A message from a stranger that an access rule admitted no longer carries the caution on its `<EVENT>`. The separate system-authored warning delivery that some typed bodies got is gone too. spt still strips a `trust-warning` attribute from inbound bodies, so a sender cannot plant one. If your pipeline rendered that attribute, it will simply never see it again.

2. **`TRUST_WARNINGS` is a new now-signal category.** Your node records the warning when the message arrives, and your next `spt api now-signal` poll shows it:

   ```
   <TRUST_WARNINGS>
   wanda — msg BCDFGH23 (+2 more): TRUST WARNING — this message is from wanda, … / …
   </TRUST_WARNINGS>
   ```

   - There is one line per peer. It names the newest message and counts the rest. The warning's line breaks are shown as ` / `.
   - A peer's warning shows at most once per session. The first poll that renders it counts it as shown for that session AND for the session in which the message arrived. A burst that arrived while you were away therefore shows once, when you come back, and does not resurface. A message from the same peer in a later, new session is warned about again, once.
   - **A now-signal spec cannot suppress it.** `only` and `without` narrow every other category, but this one always renders.

3. **Polling the now-signal is REQUIRED to receive trust warnings.** There is no other carrier. An adapter that never polls `spt api now-signal` never shows the caution.

## What to do

- Make sure your harness polls `spt api now-signal` at each turn boundary, and renders whatever it returns.
- Remove any handling of the `trust-warning` envelope attribute.
- Do not filter `TRUST_WARNINGS` out of the rendered payload.

## Where it is documented

- Harness contract → `api now-signal`: the "Polling the now-signal is REQUIRED to receive trust warnings" paragraph (`harness-contract/api.md`).
- Networking → Monics → "The trust warning" → "The warning reaches you in the now-signal" (`networking/monics.md#the-warning-reaches-you-in-the-now-signal`).
- Shells → Frames → "The now-signal: one funnel for 'what changed?'" → "Categories added after v1", the `TRUST_WARNINGS` row (`shells/frames.md`).