Organism, and it contains another

Z4, the list

The list half of the split, and the main dashboard of the product. 54 instances across 54 screens, more than any other zone.

CLAUDE.md settles it and does not reopen it: the dashboard is the queue, with the fleet in the pane, and not the other way round. It follows from the choice of primary persona, and it is not reopened without reopening that.

Five modifiers and none of them is a variant. --log, --shift, --entry, --sys and --solo change how the children paint, not how Z4 paints: they are context, and step 2 took all five off the variant list. Z4 itself has one computed form across all nine of its zone sets, measured in the browser.

It scrolls at the desk and the document scrolls at 360. overflow-y:auto here is what makes the pane foot stick and the scope bar stay; at 360 the shell stops scrolling and the document takes over, so this releases it.

Anatomy

A diagram of the zones, not a scaled scene. Z4 has no fixed size of its own: it is flex:1 1 auto and takes whatever the split leaves it, so a scene at any width would be a picture of one screen rather than of the component. What is real below: the rule on the right edge is --rule-edge, the hairlines are --rule-hair, the grounds are --bg-page and --bg-quiet, and the pane beside it is at the real --pane-w, which is 320px at 1440 and 380px above 1560: the pane narrows before the list does, and the queue keeps the sixty pixels. The band heights are drawn, because nothing inside this zone has a height token.

• .z4flex:1 1 auto with min-width:0, a flex column, overflow-y:auto, a --rule-edge on the right and --bg-page behind. Six declarations, and four of them are structure
• min-width:0load bearing. Without it a flex item refuses to shrink below its content, and one long tenant name in one row would widen the list until the pane went off the screen
• overflow-y:autothe scroll of the desk. It is what gives the sticky things something to be sticky against, and it is released at 360 where the document takes the scroll back
• what fills itscopebar, readout, rows, qfoot on the queue; brief on the shift; doc on a log entry; outage and banner when the console is degraded

Behaviour at width

Below 1280, the system's one point (Width), the column drops its right rule and releases its scroll: overflow-y goes to visible on the box and on all three of --entry, --solo and --sys. The scrollport goes back to the document, or the sticky action inside an outage pins to this column instead of to the viewport, which is the same defect the pane foot had and the same cause. Above the point it scrolls itself, and that is what makes the pane foot stick and the scope bar stay.

Variants

None, and the three modifiers below are shown rather than skipped because they look like variants and are not. They change what the children do. Z4 itself renders one computed form on all fifty four screens.

Two of the original five left at stage 09, and they were the two that named a FILLING rather than a form of this box. .z4--log is a variant of the queue list and is .queue-list--log now; .z4--shift was the shift brief itself and is .shift-brief. What each of them carried was a selector reaching into four components Z4 does not own, which is the shape a composition has when it is written inside a component. The grey corpus keeps the old names, because it is frozen.

When to use it

As the left half of the split, on every authenticated screen that has a working column. If a screen has a list, a document or a form, it goes here. If it has one case, that is Z5.

Where she meets it. Six hours a day, and it is the surface her eyes rest on between decisions. That is the whole argument for the density rule: no decorative whitespace, keyboard before mouse, and two hundred rows going past a scope bar that does not move. The zone is what makes the scope bar not move.

Rule and anti-rule

States

It has none, and it is not interactive. A zone is not a control. What looks like a state of Z4 is always a state of what is in it: an empty queue is empty, a stale one is a banner, and a degraded console is outage.

Narrow the window past 900 and the right rule goes with the pane, and the zone hands its scroll back to the document. That is the one thing about this component a reader can produce rather than take on trust.

What it reads, and where it stands

Two roles, and that is the whole palette of the largest zone in the product. Everything else on the screen belongs to something standing inside it.

Copy this

Where it stands