456 Sunset Blvd, Los Angeles CA 90028

Retired: the four-tile metric row. Hubs Completed · Documents · Tax Liability · Reinvestment Available is the hero-metric template PRODUCT.md names as an anti-reference, and none of the four numbers answers “where am I, what is next”. Hubs completed duplicates the hub grid two hundred pixels below it. Tax Liability without a 1031 renders a large red dollar figure of what the exchanger would owe if this all goes wrong — on the home screen of a product whose first job is to lower anxiety. The facts worth keeping moved: document count into the evidence trail, escrow figures into the money panel, the calculator to its own page reached from the marketplace.
Retired here: “Additional Services”. DST options and property search are real and useful, but they are a marketplace entry point, not an answer to “what do I do next”, and they belong under the marketplace tab (which surfaces/consumer.html still documents). Nothing is lost; the nav still reaches them.
Corrected: “Authorize escrow disbursement”. nextStepInfo currently gives the exchanger a next step reading Authorize escrow disbursement with a button into the Disbursement Hub. An exchanger who authorizes the movement of exchange funds is exercising a right over those funds, which is the exact fact pattern constructive receipt tests for under Treas. Reg. §1.1031(k)-1(g)(6). What the exchanger actually does is supply closing details; release is proposed by one authorized officer and approved by a different one. The hub is drawn here as Closing details and its evidence line says so.
Corrected: the constructive-receipt guardrail copy. LiveAutomationFeed.tsx renders “All transfers require approval from multiple authorized parties.” On a QI-internal screen that is merely vague; on the exchanger's screen it implies the exchanger might be one of those parties. The correct sentence names the parties and the exclusion: two authorized officers, the approver is never the proposer, and never you.
Added: waiting-on attribution. Every hub and every evidence row states whose move it is — waiting on you, with your QI officer, waiting on Fernhollow Title, nothing owed. This does not exist on the exchanger dashboard today, and its absence is why a stalled title report reads to the exchanger as personal failure.
Added: evidence under every status. A hub card carries the receipts that produced its state — the settlement statement date, the wire amount and date, the signature audit reference, the count of properties named. Status derived from a single isSubmitted flag is how a closed sale holding $812,466.18 comes to read “Not yet submitted”.
Changed: register. Base type is 14.5px against the QI console's 13px, controls are 40px minimum (46px for the primary action), hub titles are plain English — Your sale, Where your money is, Closing details — with the term of art alongside rather than instead. The exchanger is 40–80, not technical, and reading this on a phone in a car park outside a closing.
Restored: the deadline-watcher-not-operating statement. "Automatic deadline alerts are not running on this exchange; Tom sends your reminders" is a required compliance-control disclosure (AGENTS.md § Product UI copy, class 3 — deadline computation is exempt from the no-build-status-labelling rule and stays until the watcher ships), not a build-status label, so it is never removed by editing the copy. The build renders it through ComplianceDisclosure; deadline-oversight today covers only the illustrative rows, so this key may need a sibling for the card subtitle and both deadline rows.

1 · Exactly one “next step”, and it is the slab. Never zero, never two. The hub grid carries at most one Next step flag and it must name the same hub the slab points at, computed from one function. When nothing is owed by the exchanger the slab does not disappear — it becomes the calm variant and says so (“Nothing needs you today”), because an absent slab reads as a broken page, not as good news.
2 · Deadlines are framed forward and dated exactly. “28 days to identify · Wednesday, September 16, 2026” paired with the gating action. Never a red countdown bar, never a percentage of a window consumed, never an exclamation mark. Alarm colour is earned by a real breach and by nothing else, and at most one item per screen may carry it. When there is no anchor date the clock renders “not started” with the condition that starts it — never NaN, never a zero that looks like a deadline today.
3 · Status is derived from evidence, never from one flag. A hub's headline must be entailed by the receipts printed beneath it: settlement statement, wire confirmation, signature audit reference, count of properties named, deadline date. If the evidence and the headline can disagree, the headline is wrong. Concretely: a sale with a settlement statement and a matched escrow deposit reads “Sale closed” whether or not the hub form was ever formally submitted.
4 · An overdue statutory deadline never renders as satisfied, met, or green. Not the timeline node, not the hub pill, not the completion percentage, not the overall progress chip. Submitting after the deadline does not retroactively make the phase complete. overallProgressLabel must be gated on deadline health before hub progress, and a hub submitted after its deadline renders as a late filing, not a success.
5 · Identity is the first gate, and only the exchanger can pass it. While isIdentityVerified is false the slab is identity and every hub is locked with its reason stated. No coordinator, no QI officer, no admin, and no “view as” mode may mark identity verified on the exchanger's behalf, and none may present an affordance that looks like it could.
6 · Nothing on this surface may put the exchanger in a fund-movement path. The exchanger supplies closing details; the exchanger never proposes, authorizes, approves or releases. Fund movement is proposed by one authorized officer and approved by a different authorized officer — a proposer's own submission is not an approval and must never be rendered or counted as one. Any exchanger acknowledgement of a disbursement, if one is ever added, must be rendered as explicitly non-authorizing and must not gate the release. Copy on this surface states the exclusion in plain English, because the exchanger's confidence that they cannot touch the money is the product.
7 · A signature is the signer's own act. No “sign on behalf”, no “mark as signed”, no proxy signature affordance, in any mode or role. In coordinator-led mode a signature and identity verification are the only two things that may ever surface as needing the exchanger.
8 · Whose move is it, on every row. Any object two parties can act on carries an attribution chip. A step the QI owns reads handled by your QI and must never render as an incomplete item on the exchanger's list.
9 · Every card deep-links to the section it concerns. A hub card opens that hub, an evidence row opens the document or hub it describes, the deadline line opens the gating step. Never the overview, never a tab the reader then has to hunt through.
10 · Show the machine working — and only the parts that are running. The automation feed prints real Vectr workflow names and real timestamps. Rows sourced from demo fixtures carry the Demo data pill that useAutomationFeed already sets via provenance; a fabricated row that is not labelled is a compliance defect, not a polish defect. A workflow whose control is still Draft in docs/COMPLIANCE.md may never render as running: no running treatment, no green ok glyph, no live dot, no “Nm ago” age (an age asserts a run that did not happen), and no derived claim such as “your QI officer was alerted automatically”. It renders as recorded-not-armed with a Not live · <control-id> Draft pill, and it says who is watching instead. Today that covers forty-five-day-id-watcher (IRS1031-002) and one-eighty-day-deadline-guard (IRS1031-003), both Draft on the unwired trigger path (T1-4); the pills come off in the same PR that wires it, not before.
11 · One token contract. Every colour resolves through docs/mockups/tokens.css. The filled brand control takes hsl(var(--primary)) with hsl(var(--primary-foreground)) — both flip with the theme, and a hardcoded white label is 2.4:1 on the dark-theme teal. Hub hues are wayfinding (which leg) and never status; status lives on good/warn/bad and always pairs colour with a label and an icon. --ink-4 is icons, rules and disabled glyphs only, never body text. The shipped NextStepCard paints its urgency state with a hardcoded dark-amber gradient and #fef3c7 ink under an allowlist comment; the tokenized replacement is drawn in state 3 and the allowlist entry should be deleted when it lands.
12 · Motion conveys state, and calm is an accessibility requirement. Transitions run 120–280ms on the standard easing and animate colour, border, elevation and meter width — never layout. The active-phase halo is the only ambient motion drawn here; the live-dot primitive stays in the stylesheet but is withheld from the automation feed until a watcher is actually armed, because a pulsing dot over a Draft workflow is a claim, not a decoration. Both stop under prefers-reduced-motion, which also replaces skeleton shimmer with a flat fill.
13 · Register is consumer, and this file is the canonical reference. 14.5px base, 40px minimum target, 46px primary. Plain English first with the term of art alongside. Every admin, platform and enterprise surface inherits its primitives from here — hub card, meter, status pill, evidence row, next-step slab — at higher density, never the reverse. This file supersedes the dashboard tab of surfaces/consumer.html; its marketplace, documents, profile and calculator tabs remain the reference for those pages.
Light and dark are both designed here. All names, addresses, amounts, workflow references and audit references are synthetic demo data.