Sale & Identification

1 · Status comes from evidence, never from one flag. The shipped hub header derives its headline from hubStatus.submitted — the exchanger’s own progress through their own forms. A hub headline must instead be composed from what happened: settlement dates, escrow receipts, signature records, named-property counts, and the document manifest in config/hubDocuments.ts. The Sale hub here reads “Closed Jul 10 · $568,000.00 in qualified escrow since Jul 13 · 6 of 6 documents”, and a closed sale holding escrow may never render as “Not yet submitted”.
2 · A submission is a request for review, not a review. The Sale hub footer prints the exchanger’s submission and the QI officer’s acceptance as two separate facts with two separate timestamps, and says so in words. No surface may render or count a party’s own submission as an approval of it.
3 · Exactly one next step on the page. One element carries the .next treatment — “Split the last $160,000” — and it deep-links to the row it concerns. The signature that follows it is named as then:, not given a second emphasis. The Sale hub deliberately has none: it is complete, and its outstanding document is attributed to the title company.
4 · Waiting-on attribution on every row where two parties can act. Four chips only: Waiting on you, Waiting on someone else (always named and dated), Waiting on your QI, Settled. Never colour alone — icon plus word, always.
5 · A figure with no source renders as a dash. The shipped settlement panel computes Mortgage payoff as salePrice × 0.367 and Selling expenses as salePrice × 0.065 — two invented ratios presented to the exchanger as figures from their closing. That is not a styling issue; it is a fabricated number on a fiduciary surface. Every money line here carries its provenance, and the two lines that have none show — with “Awaiting the signed settlement statement”. Only the escrow receipt, which is bank-confirmed, is stated as fact.
6 · The completion meter must count the signature. The shipped identification percentage is four booleans — rule chosen, one property, confirmed, settlement step — so a file can read 100% with an unsigned designation notice, which is the only document that legally performs the identification. Until the denominator is fixed, the meter never stands alone: it carries “The signature is not counted in this figure” and the header evidence line states the signature status. Fixing the denominator is the real remedy.
7 · A rule you did not elect is grey, not green. IdComplianceRail currently returns status: 'pass' with the label “N/A — alternative rule elected”, which paints a green tick beside a rule the file is not being measured under. Not-elected rows render neutral and are labelled Not elected, with the live figure kept as information.
8 · An auto-generated document is not complete because it is auto-generated. DocumentChecklist.getDocStatus() returns completed: true for every auto-generate row unconditionally, before anything has been produced. Generation and signature are separate facts and are drawn as separate chips on the designation-notice row.
9 · One clock, one threshold. lib/identification/countdown.ts (urgencyTier) escalates at 10 and 20 days; ExchangeHub’s deadlineSeverity escalates at 7 and 14. The same file can be amber in one component and red in another on the same day. Pick one function, export it, delete the other.
10 · The 45th day is stated three ways and softened none of them. Running, closing tonight, and closed. A window that closed with nothing identified renders as the loudest element on the screen, says that no one can extend the date, and pairs the bad news with the two true reassurances: the money has not moved, and a human is reachable. A window that closed having been met is Locked, never Complete — the exchange is not finished, the 180-day clock is still running.
11 · Extraction is labelled for what it is. Every block fed by documentExtraction.simulateExtraction() carries the dashed Demo extraction pill. Extracted values are proposals with a confidence and an obvious way to correct them; nothing is written to the file until the exchanger confirms; and the confirmation is what the audit trail records. When the Vectr extraction workflow lands, the pill comes off and the step labels stay.
12 · Motion carries state only. Colour, border and elevation transition at --duration-fast; the completion meter animates its width at --duration-base; the extraction reveal rises once at --duration-base. Loading is a skeleton in the shape of the answer, never a spinner. prefers-reduced-motion removes all of it.

Identity is the first gate, and it is the exchanger’s own. The Sale hub is unreachable until identity clears. No coordinator, officer or admin affordance on either hub can mark identity verified by proxy, waive a screening result, or self-clear a gate.
A signature requires the signer’s own intent. There is no “sign on behalf” control anywhere on these hubs. When a coordinator is working inside the file, the shipped hook returns canSign: false with “Your client signs this”; that state is drawn as the lock strip under the designation notice. Signing records the signer’s name, the moment, and the exact document rendered to them (eSign Act / UETA).
The exchanger is never in a fund-movement path. These hubs show money as a read-only ledger: a confirmed sale price and a bank-confirmed escrow receipt. No control here initiates, authorises, approves or acknowledges a release. Release requires two authorised officers, and the approver is never the proposer — stated on the escrow card so the exchanger understands the protection rather than discovering it. Putting the exchanger anywhere in that path would be constructive receipt under Treas. Reg. §1.1031(k)-1(g)(6) and would break the exchange this product exists to protect.
A statutory date is never rendered as satisfied, met, or green once it has passed unmet. No green tick, no success wash, no soothing copy. The eligibility consequence is stated in plain English, once, without pretending to be tax advice and without pretending the situation is recoverable in software.
Deadlines are never quietly moved. Disaster relief exists, but it is recorded by the QI with its legal basis and an audit entry, and it is described to the exchanger as something their coordinator confirms — never as a control on this screen.
No tax or legal advice. Rule consequences are described mechanically (“if the total goes over, the identification fails”) and every judgement call is routed to the exchanger’s own advisor.

1 · No colour literal survives to the implementation. Every colour resolves through docs/mockups/tokens.css. Hub hue is scoped by one attribute on any container ([data-hub="sale"] / [data-hub="id"] set --hub, --hub-ink, --hub-wash, --hub-line), so no component reaches for a specific leg and adding escrow, purchase or disbursement is one attribute. .page carries a neutral fallback for the same four names: a hub-scoped component rendered outside a hub — in a state gallery, in a dashboard card — must degrade to the neutral ramp, not resolve to nothing and paint transparent.
2 · Filled controls take the flipping foreground. The primary action is hsl(var(--primary)) with hsl(var(--primary-foreground)); the affirmative is --good-ink with --good-on; the destructive is --bad-ink with --bad-on; the current step disc is --hub with --hub-on. Every one of these pairs inverts in dark, because the fill lightens there and a hardcoded white label would fail.
3 · Muted text is --ink-3. --ink-4 appears only as icon strokes, rules, the dash placeholder and disabled glyphs — never as body copy. This audience is 40–80 and reading under deadline pressure.
4 · Colour carries one meaning each. Hub hues are wayfinding — which leg of the exchange — and never say whether that leg is healthy. Status stays on good / warn / bad, always with a label and an icon. Teal is the consumer brand and the QI-custody accent; the Neela mark is its own identity and is never a status.
5 · Light and dark are both designed. Three resolutions: no attribute follows the OS, [data-theme="light"] and [data-theme="dark"] force a choice. Every state on this page was checked in both.
All names, addresses, amounts, parcel numbers and file references are synthetic demo data. Demo date: Wednesday, August 19, 2026.