zara-comms: fail closed on malformed message and send booleans #68

New issue

Closed

opened 2026-09-08 02:02:54 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:02:54 +00:00

Owner

Problem

CommsDomain currently truthiness-coerces backend boolean fields: normalized message read uses bool(...), and send mutation accepted uses bool(evidence.get("accepted")). Malformed provider strings such as "false" can therefore become true.

Required behavior

message read must be an exact boolean; malformed values fail structurally
only exact boolean True counts as send acceptance
malformed send evidence never yields verified success
deterministic regressions
full registry/install/Nix gate remains green

No Zara Core changes.

## Problem `CommsDomain` currently truthiness-coerces backend boolean fields: normalized message `read` uses `bool(...)`, and send mutation `accepted` uses `bool(evidence.get("accepted"))`. Malformed provider strings such as `"false"` can therefore become true. ## Required behavior - message `read` must be an exact boolean; malformed values fail structurally - only exact boolean `True` counts as send acceptance - malformed send evidence never yields verified success - deterministic regressions - full registry/install/Nix gate remains green No Zara Core changes.

nsaspy closed this issue

2026-09-08 02:02:54 +00:00

nsaspy referenced this issue from a pull request that will close it,

2026-09-08 02:20:12 +00:00

Add passive bounded zara-healthcheck service #495