# Slice 3 Part B — controller v0.256.0 / v0.256.1, live evidence (2026-09-18)

**Method: endpoint-level and log-level** on demo-hp guest 9201. Nothing installed, nothing removed,
no deploy request of any kind. The credential-bearing probe **shredded itself** on exit, host and
guest, which is R-584's own fix shape applied the same day it was filed.

## The box sends the second sentence only for a non-Hungarian household

The same event (`controller_started`, which fires on every restart and needs no state change), on the
same box, 57 seconds apart:

```
15:07:28  Event pushed: controller_started (info) [hu-only]        — Controller elindult (0.256.1)
15:08:25  Event pushed: controller_started (info) [+household(en)] — Controller elindult (0.256.1)
```

**The Hungarian sentence is IDENTICAL in both.** That is the invariant the whole slice rests on:
`message` never moves, because it is what the operator is mailed and what the hub stores.

## The hub accepted it, and stored the Hungarian

```
[INFO] Event from demo-hp: controller_started (info) — Controller elindult (0.256.1)   (both times)

events table, demo-hp:
  2026-09-18 15:08:25  controller_started  info  'Controller elindult (0.256.1)'   <- the en push
  2026-09-18 15:07:28  controller_started  info  'Controller elindult (0.256.1)'   <- the hu push
  2026-09-18 14:55:38  controller_started  info  'Controller elindult (0.256.0)'
```

No 400: the new field is additive and the hub takes it. The stored message is the Hungarian one in
every case, **including the push that carried an English household copy**.

## Why the proof is a LOG LINE and not an e-mail

There is no honest way to make a converted producer send a customer e-mail on this box:
`severityNotifies` drops `info`, so the safe producers (`controller_started`, `app_deployed`,
`db_dump_completed`) mail nobody — and every converted producer at `warning` or above describes
something bad that is not true (`storage_disconnected`, `crossdrive_failed`, `app_deploy_failed`,
`disaster_recovery_started`). Triggering one would mean either a false record on a real box's
timeline or a state change the fences forbid.

**So the log line was built for this**, in v0.256.1, after finding there was nothing to look at:
the box logged only the Hungarian, the hub logs only the Hungarian, and the payload is inside TLS.
"Did the box attach a second sentence?" was unanswerable from either end — which is exactly the
question a mis-languaged mail raises.

**What that leaves unproven live:** an English household's *rendered event mail*. The hub half of
that rendering WAS proven live in Part A (a real English mail, read in the inbox); the box half is
proven here at the wire; the join between them is covered by tests on both sides. Saying that plainly
is better than manufacturing a false alarm to photograph.

## What is NOT converted, stated rather than implied

- **The 15 operator-tier types** — the operator reads Hungarian and these never reach a customer.
- **Producers whose sentence is composed in another package** and arrives finished: `backup_failed`,
  `db_dump_failed`, `backup_integrity_ok`/`_failed`, `offbox_enlarge_blocked`,
  `local_api_endpoint_drift`. They send Hungarian only, so an English household can still see one
  Hungarian line in some mails. **Filed as R-585.**
- The R-570 sentence, until that row closes.

## State at the end

Controller **0.256.1** on demo-hp, healthy. Box back on **Hungarian**. Hub **0.118.1**. No floor
change, no golden, nothing installed. Guest `/tmp` carries no probe and no credential.