From 596c4c1393f3c3511ad7c8c1d3dd9c5985ac1384 Mon Sep 17 00:00:00 2001 From: ZeroPoint95 <329227198+ZeroPoint95@users.noreply.github.com> Date: Mon, 21 Sep 2026 14:35:29 -0400 Subject: [PATCH 1/5] Separate proposed message-box standing rules for owner review --- CLAUDE.md | 1 + docs/DESIGN-LANGUAGE.md | 22 +++++++++++++++++++ .../1071-proposed-message-box-rules.md | 12 ++++++++++ 3 files changed, 35 insertions(+) create mode 100644 docs/changes/unreleased/1071-proposed-message-box-rules.md diff --git a/CLAUDE.md b/CLAUDE.md index 6db996f7d9..7806eae7fd 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -396,6 +396,7 @@ recipe for driving the surface and killing the link on purpose. ## Learned User Preferences +- For every requested change to the home-screen message box, assess whether it also applies to the conversation message box. When it does, implement the natural analogue in the same change without asking separately. Maintain parity in shared behavior and presentation while preserving context-specific differences; the two message boxes need not be literally identical. - Keep designs and local verification robust without wasting laptop time or CPU: prefer deterministic clocks and focused/`pr-ready` paths over real sleeps or unconstrained full `internal/tui3` / `internal/session` suites on a shared box. ## Learned Workspace Facts diff --git a/docs/DESIGN-LANGUAGE.md b/docs/DESIGN-LANGUAGE.md index 242e548346..be25416552 100644 --- a/docs/DESIGN-LANGUAGE.md +++ b/docs/DESIGN-LANGUAGE.md @@ -72,6 +72,15 @@ hover moves the card and never the mark. `dim` — THE ACCENT BUDGET below forbids lighting them, and a lit heading is the same defect arriving from the other side. The ground alone carries the fact. +**A heading that is a door underlines under the pointer, and that is all the +pointer does to a heading.** Home's headings open the place they name, and a +person holding a mouse over one is asking whether it will; the answer is the +underline — no ink, no ground, the one attribute a terminal has always used to +say "this opens somewhere" — on the word alone, and only on a heading that +opens somewhere. It is an affordance and not a step of the ladder: it marks +nothing about where the cursor is, so the marked heading above still follows +the keyboard only (added 2026-09-17). + ### THE EMPHASIS LAW > **A row is emphasized by raising its ground and turning its leading text @@ -486,6 +495,19 @@ colour is a row that shouts, and a screen of shouting rows is a screen with no priority at all. The grounds in THE GROUND LADDER are the sole exception, and they are exactly as quiet as the table above says. +### The current model on the message-box seam + +Owner ruling, 2026-09-17: the current model is always **bold in the data hue** on +home and conversation seams. It must be easy to find without hovering or first +changing it. The provider beside it and the surrounding telemetry keep their +existing weight; the emphasis is confined to the model name. +The effort follows a colon without a space or badge: `model (provider):effort`. Its +styling stays separate from the model. The conversation seam carries no git branch. Home starts +with those controls and puts `project: ` at the far right. Project paths on +home preserve their absolute root (or `~/` under the home directory) and truncate +at the right end, never at the left. + + ## ONE MARK PER TOKEN > **One token wears one visible mark.** diff --git a/docs/changes/unreleased/1071-proposed-message-box-rules.md b/docs/changes/unreleased/1071-proposed-message-box-rules.md new file mode 100644 index 0000000000..80dccaf81f --- /dev/null +++ b/docs/changes/unreleased/1071-proposed-message-box-rules.md @@ -0,0 +1,12 @@ +--- +kind: changed +title: Proposed message-box parity and visual rules +pr: 1071 +surface: [docs] +invalidates: + - "These proposed standing preferences and visual rules are reviewed separately from the UX implementation in PR 1071; their owner attribution requires confirmation before merging." +--- + +Separated at the reviewer's request: message-box parity, clickable-heading +hover feedback, and model and project presentation on the seam. This draft is +for confirmation of the proposed standing rules and their attribution. From 1852f2cdce64f8b7c897c325122b0ef25b43e026 Mon Sep 17 00:00:00 2001 From: ZeroPoint95 <329227198+ZeroPoint95@users.noreply.github.com> Date: Mon, 21 Sep 2026 14:38:57 -0400 Subject: [PATCH 2/5] Associate the proposed rules entry with PR 1334 --- ...ed-message-box-rules.md => 1334-proposed-message-box-rules.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/changes/unreleased/{1071-proposed-message-box-rules.md => 1334-proposed-message-box-rules.md} (100%) diff --git a/docs/changes/unreleased/1071-proposed-message-box-rules.md b/docs/changes/unreleased/1334-proposed-message-box-rules.md similarity index 100% rename from docs/changes/unreleased/1071-proposed-message-box-rules.md rename to docs/changes/unreleased/1334-proposed-message-box-rules.md From ced6338cba834eb839c0714ea7679a0a7cb70f91 Mon Sep 17 00:00:00 2001 From: ZeroPoint95 <329227198+ZeroPoint95@users.noreply.github.com> Date: Mon, 21 Sep 2026 14:39:17 -0400 Subject: [PATCH 3/5] Set the separate change entry PR number --- docs/changes/unreleased/1334-proposed-message-box-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/changes/unreleased/1334-proposed-message-box-rules.md b/docs/changes/unreleased/1334-proposed-message-box-rules.md index 80dccaf81f..9a30cf68e6 100644 --- a/docs/changes/unreleased/1334-proposed-message-box-rules.md +++ b/docs/changes/unreleased/1334-proposed-message-box-rules.md @@ -1,7 +1,7 @@ --- kind: changed title: Proposed message-box parity and visual rules -pr: 1071 +pr: 1334 surface: [docs] invalidates: - "These proposed standing preferences and visual rules are reviewed separately from the UX implementation in PR 1071; their owner attribution requires confirmation before merging." From af17cce6e61c8072410eaffd431523f3d6eb7fe1 Mon Sep 17 00:00:00 2001 From: Abir Abbas Date: Thu, 24 Sep 2026 11:25:02 -0400 Subject: [PATCH 4/5] docs: credit the seam rules to #1071, and publish an entry that is true The model-on-the-seam rule named an owner ruling nobody can point to; the behaviour it describes is what #1071 shipped and its tests pin, so it is credited to that pull request instead. The change entry carried a note for reviewers in `invalidates`, which the changelog publishes as a claim; nothing anybody believed changed here, so the list is empty and the body says what lands. Co-Authored-By: Claude Opus 5.5 (1M context) --- docs/DESIGN-LANGUAGE.md | 2 +- .../unreleased/1334-proposed-message-box-rules.md | 14 ++++++++------ 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/DESIGN-LANGUAGE.md b/docs/DESIGN-LANGUAGE.md index be25416552..0de6da83a8 100644 --- a/docs/DESIGN-LANGUAGE.md +++ b/docs/DESIGN-LANGUAGE.md @@ -497,7 +497,7 @@ they are exactly as quiet as the table above says. ### The current model on the message-box seam -Owner ruling, 2026-09-17: the current model is always **bold in the data hue** on +Adopted with #1071 (merged 2026-09-21): the current model is always **bold in the data hue** on home and conversation seams. It must be easy to find without hovering or first changing it. The provider beside it and the surrounding telemetry keep their existing weight; the emphasis is confined to the model name. diff --git a/docs/changes/unreleased/1334-proposed-message-box-rules.md b/docs/changes/unreleased/1334-proposed-message-box-rules.md index 9a30cf68e6..e42e5d4a3e 100644 --- a/docs/changes/unreleased/1334-proposed-message-box-rules.md +++ b/docs/changes/unreleased/1334-proposed-message-box-rules.md @@ -1,12 +1,14 @@ --- kind: changed -title: Proposed message-box parity and visual rules +title: The message-box rules #1071 shipped are written down pr: 1334 surface: [docs] -invalidates: - - "These proposed standing preferences and visual rules are reviewed separately from the UX implementation in PR 1071; their owner attribution requires confirmation before merging." +invalidates: [] --- -Separated at the reviewer's request: message-box parity, clickable-heading -hover feedback, and model and project presentation on the seam. This draft is -for confirmation of the proposed standing rules and their attribution. +`docs/DESIGN-LANGUAGE.md` now records what #1071 shipped: a Home heading that +opens a place underlines under the pointer, and the message-box seam draws the +current model bold in the data hue, spells the effort `model (provider):effort`, +carries no git branch in a conversation, and keeps home's `project: ` at +the far right, cut on the right. `CLAUDE.md` gains a standing preference: a +change to Home's message box is weighed for the conversation's in the same change. From 0e17c48c15d3258ba3c433b1dc4e4184071fa79a Mon Sep 17 00:00:00 2001 From: Abir Abbas Date: Thu, 24 Sep 2026 16:18:57 -0400 Subject: [PATCH 5/5] docs: the message-box parity preference stays out of CLAUDE.md Abir's ruling on #1334: the Home-to-conversation message-box parity line was a preference from one session, not a rule every agent in this repo should carry, so it leaves Learned User Preferences and the change entry no longer announces it. The design rules in DESIGN-LANGUAGE.md stay as written. Co-Authored-By: Claude Opus 5.5 (1M context) --- CLAUDE.md | 1 - docs/changes/unreleased/1334-proposed-message-box-rules.md | 3 +-- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 7806eae7fd..6db996f7d9 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -396,7 +396,6 @@ recipe for driving the surface and killing the link on purpose. ## Learned User Preferences -- For every requested change to the home-screen message box, assess whether it also applies to the conversation message box. When it does, implement the natural analogue in the same change without asking separately. Maintain parity in shared behavior and presentation while preserving context-specific differences; the two message boxes need not be literally identical. - Keep designs and local verification robust without wasting laptop time or CPU: prefer deterministic clocks and focused/`pr-ready` paths over real sleeps or unconstrained full `internal/tui3` / `internal/session` suites on a shared box. ## Learned Workspace Facts diff --git a/docs/changes/unreleased/1334-proposed-message-box-rules.md b/docs/changes/unreleased/1334-proposed-message-box-rules.md index e42e5d4a3e..d24ed6935b 100644 --- a/docs/changes/unreleased/1334-proposed-message-box-rules.md +++ b/docs/changes/unreleased/1334-proposed-message-box-rules.md @@ -10,5 +10,4 @@ invalidates: [] opens a place underlines under the pointer, and the message-box seam draws the current model bold in the data hue, spells the effort `model (provider):effort`, carries no git branch in a conversation, and keeps home's `project: ` at -the far right, cut on the right. `CLAUDE.md` gains a standing preference: a -change to Home's message box is weighed for the conversation's in the same change. +the far right, cut on the right.