The collections panel on the tenant page

Zero COLLCASE# rows exist in production — a full-table scan found none — so the operator-set stage is empty for every resident. This is therefore not the empty state; it is the state, and the panel had to be useful and honest in it rather than a row of blanks implying missing data.

Read what is still on screen. The header strip is fully populated from the ledger: the aged sum, the four bands, the age bound and the as-of stamp all come from the balance snapshot, which every delinquent account has. The stage chip says “No stage set” in words rather than rendering an em-dash that looks like a loading failure. The language chip names the recorded preference — here, English. It reads “Language not asked” when none is on file, which is the state that matters and is not photographable on this bench because every synthetic resident has one: the outbound stack defaults an unset preference to English, which is right for a text and wrong for a legal notice, since in Colorado a demand must be in the resident's known primary language and that makes it a statutory element of a valid notice. The absent-preference branch is pinned by the component's own DOM suite, which asserts the chip reads “Language not asked” and never “English”.

The rail below draws the whole money spine from the bands and then shows the three branches as possibilities — dimmed, dashed, captioned “Nothing past the ledger has been recorded for this account, so where it goes next is not known — not that it has gone nowhere.” The difference between those two sentences is the entire design.

Note the age reads oldest in 91+ days — the band the oldest money sits in, never an exact age. The rent roll hands us four buckets and no charge dates, so the only honest reading of money in the oldest bucket is “at least 91 days”. A precise-looking age is the number a PM pastes into a notice, and one day short voids a demand — 19 defective demands across 12 units in this portfolio's own history.

The narrow case, and the one layout decision in the rail that is not obvious. The rail scrolls horizontally; it does not wrap. A wrapped rail reads as two rows of unrelated chips, and the ORDER is the whole message — so on a phone the row keeps its order and the reader pushes it sideways, which is what overflow-x-auto on a w-max track buys.

The header strip does wrap, because there the order carries nothing: the chips are a set of independent standing facts, not a sequence. The bands go from a five-across row to a wrapped grid and stay legible.

The page body itself must not scroll horizontally — only the rail's own track does. That is visible here: the card edges are flush at both margins.

Every node on the rail is a button. Clicking one opens its meaning underneath — the lo-fi's “click any state to see what it means” — and, crucially, the sentence naming which of the three sources put the account there.

This is “Past due”, opened. It carries the enrolment fact a PM needs (“A full month behind. This is where the reminder cadence starts.”) and then “Measured from the aged balance on the rent roll.” That second line is the panel's answer to a question the old cards could not be asked: is this something the system observed, something a person typed, or something we read in someone else's email? A rail that shows a state without saying where the state came from invites a PM to act on a parse of a Zendesk autoresponder as though a human had confirmed it.

The legend at the foot of the card carries all four marks, including Not known — which is a reach state, not a source.

The other end of the range. A person recorded a served demand on this account in July and escalated it to counsel in August, so the rail now draws the legal branch — Demand ready → Served → At the firm → Filed → Judgment — with “At the firm” marked as where they are and a pencil glyph saying a human put it there. The last two nodes sit past the right edge of the horizontally-scrolling track in this crop, so they are not asserted here: this tool cannot see clipping by an inner scroll container, and a green ✓ beside a string the picture does not show is worse than not checking. Their reach and their accessible names are pinned in the component's DOM suite instead.

Two things it deliberately does NOT do. First, Demand ready and Filed stay dim even though a later node is lit: reaching “at the firm” says nothing about a demand having been prepared in the product, and the depth order is an ordering, not a path. Second, the stage that lit this is flagged_for_eviction, which maps to At the firm and never to Filed — that value explicitly means escalated, not filed, and nothing in PropFlow files an eviction. A rail that read the enum's name and drew a court filing would be putting a claim in front of a PM that no writer in the system can back.

The reverse edge is still on screen, and now the assistance stop-edge is too — because the legal branch is the branch it kills. Approved assistance has to stop every chase, demand and filing on approval, not on receipt of the money.

What is not on this page, and why. The chronology's third source — the parsed law-firm and assistance mail — renders nothing here, and that is a true reading rather than a bug: a sweep of every operational signal on the stage table found 0 rows carrying collections facts across all three properties, because the parser only claims mail for a property with collectionsCorrespondents configured and #5939 has only just landed. There is no environment in which that half is capturable today. It is covered instead by DOM tests that render the real component over real fact shapes — including the identity caveat, the verbatim dateRefs, and the pinning of an assistance approval read off the programme's own email.

The same account's history. Three operator rows here, each with a pencil glyph and a “Recorded by the property team” line — a CLAIM. A dun row or a cadence-end row would carry a receipt glyph and read “Automatic”. The new inbox rows read “From the inbox · <sender>” and never “Automatic”, because the product did not do the thing; it read a message from someone who did. Resident rows are the resident's own words in quotes.

That distinction is the card's whole reason for existing and it now spans four sources instead of two. A PM deciding whether to escalate needs to know which lines they can lean on.

Note what is not here: a second stage chip. The operator-set stage rides the header strip at the top of this section, and the chip this card used to carry was removed in the same change — two chips stating the same stage a few hundred pixels apart is how someone ends up checking whether they agree.

Run last on purpose: the theme preference is stored per browser, so a flip in the middle of this sequence would have silently tinted every page after it. Same account, same scroll position, theme switched to dark through the product's own control in the side nav — not a CSS override applied to the screenshot. Every colour in the two new components is a var(--color-*) token, so this page is the check on that claim rather than a restatement of it: a hardcoded hex would survive the light capture and show up here.

Two things worth looking at specifically. The dashed borders on the dimmed branch heads still read as dashed rather than dissolving into the panel — that is the only visual difference between “not reached” and a lit node, so it has to survive both themes. And the indigo ring on the current node is --color-primary, the one accent this panel uses.