Originally created by: lodar
First of the DIVE-1494 council⇄telegram v1 cut main confirmed (notice+tally, founder-veto tap [#2], receipt/lineage view [#3]; human-as-seat deferred to CNCL-18).
What: council convene emits an opt-in, read-only NOTICE of the outcome — disposition (rec, tally aA/rR/eE, conf), the question, and the sealed receipt handle — over the same guarded-optional _tg_send seam the founder-veto leg already uses. The telegram plugin provides _tg_send; council never hard-depends on it. Opt-in via COUNCIL_NOTIFY=<chat>; silent when unset or when the seam is absent.
Read-only by construction: carries NO nonce and no tap — distinct from the founder veto ping. A test asserts no 32-hex bearer token can ride in the notice.
Tests: tests/council_notify_e2e.sh (wired into council_unit.sh, 6/6) — fires with disposition+tally+receipt, no raw-nonce leak, silent without COUNCIL_NOTIFY. Offline via the double-gated COUNCIL_MOCK+COUNCIL_NOTIFY_SINK capture seam (mirrors COUNCIL_VETO_NONCE_SINK), so production never writes the sink. Full council suite green (contract 53, veto 16, notify 6, gate 12, roster 27, amend 17, bashroute 7, ballot 8, cosign 26/6).
Build: template → gen_cmd.mjs → ./build.sh; 5dive/5dive.sha256 bumped, deterministic (rebuild = zero drift). Version 0.11.27 → 0.11.28. Branch off current origin/main (6dcd5bc).
🤖 Generated with Claude Code
Ticket changed by: lodar