@lotics/ui 27.13.0 → 27.13.1

package/docs/composition.md

@@ -494,7 +494,7 @@ All view controls are 40px tall (`CONTROL_HEIGHT`), `sm` labels, in ONE wrapping
   (colored `Text`), not the buttons.
 - **Create buttons carry NO `+` icon** — "Add fee", not "+ Add fee". A create is `primary` and
   rides its section's HEADING row at the right edge — see § The add-placement law for why, and
-  for the one-verb-one-weight rule that keeps it primary in the `EmptyState` too. (The
+  for the one-verb-one-weight rule that keeps it `primary` wherever it renders. (The
   icon-only `+` `IconButton` — a composer's attach — is a different thing and keeps its glyph.)
 
 ## The action-gating law — disabled + the reason as a co-located Callout
@@ -600,11 +600,13 @@ gate's SCOPE, once** — never prose beside the button, never revealed only on p
 
   The ADD is the one verb this law does NOT place next to its effect, and the add-placement law
   says why: a position that never moves beats a position that is adjacent, because "below the
-  last row" is a different place on every list and no place at all on an empty one.
-  **An add is `primary`, in the `EmptyState` too.** It is the act its section offers, so it
-  carries that section's weight; a lone `secondary` button reads as though the real action were
-  somewhere else. The rule that matters is that ONE VERB KEEPS ONE WEIGHT — the same add must
-  not be primary on an empty list and secondary on a full one.
+  last row" is a different place on every list and no place at all on an empty one. The heading
+  row therefore carries identity + meta + view controls + the section's ADD, and no other content
+  verb. **An add is `primary` wherever it renders** — on that heading row, or inside an
+  `EmptyState` in the one case § Empty states allows, where there is no heading to carry it. It
+  is the act its section offers, so it carries that section's weight; a lone `secondary` button
+  reads as though the real action were somewhere else. The rule that matters is that ONE VERB
+  KEEPS ONE WEIGHT — the same add must not be primary on an empty list and secondary on a full one.
   A record surface therefore carries several primaries, one per section, and that is correct:
   "one primary per SCREEN" governs the page BAND, not a stack of independent sections each with
   its own single act. The cost is real and worth knowing — the more sections offer an act, the

package/docs/templates.md

@@ -53,6 +53,22 @@ the package index is [../AGENTS.md](../AGENTS.md).
 | AI ranks answers — look-up-and-explain | `tpl_lookup` |
 | AI over a record's documents (extract / cross-check / generate) | `tpl_record` — its Documents + Document set sections |
 
+### Register + drawer, or a navigated page?
+
+The register is the DEFAULT, and its row press opens the workspace `Drawer`. A record earns
+its own navigated route only when one of these holds:
+
+- **It is a destination.** Someone arrives cold from outside the register — a link in an
+  email, a notification, a handoff from another desk — and must land on the record without
+  the list to open it from.
+- **The work needs the canvas.** A docked comments gutter, a document read beside the fields,
+  an outline rail worth navigating — width the drawer's single column cannot give.
+
+The volume of DATA is not the test. A record with forty fields still closes in the drawer if
+the operator opens it from the list, works it, and goes back to the list. What an app without
+a destination skips is the ROUTE, never the template: the drawer renders `tpl_record` either
+way, so "no record page" must never become a hand-built detail surface.
+
 ## Composition rules — how a record surface is assembled
 
 Laws for any screen where a record's data is edited and a primary action produces its output
@@ -268,7 +284,10 @@ billing, and quick-capture templates. Top → bottom:
   ATTENTION state as a co-located `Callout` (e.g. overdue — record-scoped state reads here;
   field-scoped state stays on its field), then a quiet `SummaryLine` (desk, documents
  , to collect).
-- **GENERAL — the MAIN details, FIRST in the rail**; every later section is supplementary.
+- **GENERAL — the MAIN details, first in THIS record's rail** because its work starts at the
+  details; rule 1 orders sections by work flow, so a surface whose work starts at a DOCUMENT
+  (an invoice desk, a claims desk) leads with Documents and General follows. Every later
+  section is supplementary.
   A `SubsectionStack` (space-only beat) of a headingless LEAD group (the key facts) plus
   named groups (e.g. Order / Fulfilment / System — system identifiers get a HOME, not a
   per-row badge). Every group's `DetailTable` repeats the same `labelWidth` so the grid

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/ui",
-  "version": "27.13.0",
+  "version": "27.13.1",
   "type": "module",
   "exports": {
     "./vite": {