Skip to content

ADR 0075: UI Subject Index (docs/adr/UI/) and MFD Page Conventions

Status: Proposed
Date: 2026-04-20

ADR Role
0076 Center for UI/UX Principles; coherent introductory text
0021 secondary circuit / MFD
0068 payload vs projection
0060 keyboard-first, Command Melody
0074 density and location in MFD
0013 palette
0030 command_id
0096 index of topics in Intercom, summary on card
0077 TECH - the center of principles (connected text from the canon)

Outside ADR

Document Role
TECH/README.md index of TECH principles

Context

Discussions of visual presentation (list vs table, scroll, tooltips) without a fixed standard in the repository give friction: restoration “as it was” from memory, different interpretations of terms (including product vs ADR), dispute about priorities pointer vs keyboard.

At the same time, the repo already has the payload vs presentation standard (0068) and keyboard-first inputs (0060).

1. Solution: folder docs/adr/UI/

  1. Enter thematic index docs/adr/UI/README.md: a table of links to existing ADRs on the topic UI/MFD/chromium/palette.
  2. Do not introduce separate numbering and do not duplicate the text of regulatory ADRs inside UI/ - the canon is still the files docs/adr/NNNN-*.md and the main index. Navigation map of principles (where to look for the full text) - UI/principles.md.
  3. Subfolder UI/ - not classification by ADR status (see agreements in README § “Agreements”); only convenient navigation on the topic.

2. Secondary Flow Page Conventions (MFD)

Normatively rely on:

Principle Source
One payload of lines (order, command_id/DTO) changes in the VM/service; projection (cards, table, density) - in View without changing row semantics 0068
Keyboard-first: The meaning of the command is available through the /Melody(c:)/Chords palette with the same command_id; hover-only do not count as the only channel for mandatory meaning 0060, 0072 where appropriate
Narrow MFD—width/height limitation; scroll / compact / fallback strategies - coordinate with the direction 0074 for forms and similarly for “long” lists

Example (illustration, not a separate canon): page “environment readiness” - collection AnnunciatorLampItem; switching "compact / wide" - only layout (EnvironmentReadinessPresentationResolver), line order - payload.

3. Consequences

  • Agents and people can refer “see. ADR/UI" as in docs/adr/UI/README.md, without mixing with flat index cancellation.
  • Controversial UI decisions on a product are still documented as a separate numbered ADR or editing an existing one, and not just a note in UI/.

4. Rejected alternatives

  • Wiki only / chat only - without a link from the repo, reproducibility is lost.
  • All UI-ADRs only in the UI/ subfolder - breaks the current NNNN-*.md naming convention in one directory and makes it more difficult to search by number.