From da20475d2f6dccc455b9a9272f5e76b0b948a798 Mon Sep 17 00:00:00 2001
From: Oleh Omelchenko <ptrvtch@protonmail.com>
Date: Fri, 5 Jun 2026 14:10:56 +0300
Subject: [PATCH] Record council resolutions for Draft/Published toggle and
 status dot

---
 .../10-interaction-and-feedback.md             | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/docs/architecture/10-interaction-and-feedback.md b/docs/architecture/10-interaction-and-feedback.md
index a471cc4..15dc793 100644
--- a/docs/architecture/10-interaction-and-feedback.md
+++ b/docs/architecture/10-interaction-and-feedback.md
@@ -149,7 +149,11 @@ the Draft/Published view) is a **radio group**, never a row of `aria-pressed` to
 - `role="radio"`/`aria-checked`, a **roving tabindex** (only the selected option is a tab
   stop), and Arrow/Home/End to move-and-select (APG → Radio Group). One widget so the keyboard
   model is defined once. _(Tabs were a candidate for Draft/Published; we chose radio group for
-  consistency with the other segmented controls and to avoid tabpanel wiring to Monaco.)_
+  consistency with the other segmented controls and to avoid tabpanel wiring to Monaco. A
+  **toggle switch** was also weighed and rejected: APG defines `role="switch"` as on/off of a
+  **single** setting, but Draft/Published selects between two **named peer views** with no
+  natural "on" side — a radio group is the right semantics. Reserve the switch for genuine
+  on/off settings. Consulted via /council → APG switch / radio-group / tabs.)_
 
 **Resolved — selectable lists.** A row the user selects must be a real `<button>` (or a
 proper option), not a click handler on `<li>` (mouse-only, no keyboard, no role). It is
@@ -158,6 +162,18 @@ forbids interactive children in a listbox. Mark the active row with `aria-curren
 **only on that row** (don't emit `aria-current="false"` everywhere). Arrow-key roving
 _between_ rows is a later enhancement; button-per-row tab stops are the acceptable baseline.
 
+**Resolved — snippet-list status indicator.** The library row flags only the _exceptional_
+state: a single **accent dot** when a snippet has unpublished draft changes; a fully-published
+snippet shows **no dot** (presence = draft, absence = published). We do **not** give "published"
+its own glyph — GOV.UK's Tag guidance notes one status suffices when absence is self-evident,
+and Carbon's status-indicator pattern says not to highlight what isn't significant. Meaning
+never rests on **hue** (WCAG 1.4.1): it rides on presence/absence **plus** the dot's accessible
+label, and the colour is the neutral **accent** — not a warning hue, because unpublished work is
+a normal state, not a problem. The dot sits in the row's secondary metadata line (with the
+relative date and size), in a fixed-width leading slot so it never shifts adjacent text.
+_(Consulted via /council → GOV.UK Tag, Carbon status-indicator-pattern, APG. This bullet is the
+contract; cite it, not the external source.)_
+
 **Resolved — one live region per shared message.** When the same error feeds two surfaces
 (the §1 "one producer, two subscribers" case — render errors via `PreviewStore`), exactly
 **one** subscriber is the live region (`role="alert"` on the editor, where focus is); the