Exchange queue · deadline horizons

Deadline horizon

All exchangers, coordinators and amounts shown are synthetic sample data.

Exchanger

Type

45-Day Deadline

180-Day DeadlineMay be earlier — confirm return due date

Coordinator

Escrow

Status

Actions

Status

Accepted design Forward-queue variant for #2799, accepted 2026-09-13 — independent designer critique (H1, H3), ordinary Compliance review (H2) and tower architecture acceptance (H4) — and recorded in ADR-059. Implementation is owned by O-B-13, Phase 2 wave 7; this drawing starts no phase and claims no built runtime.

Surface state Ready Loading Empty Error

“Empty” is reached honestly: it sets Coordinator = Unassigned and horizon = Past deadline, which has zero rows in this book. Loading and Error are forced.

What differs from canon

Pill labels are the shipped DEADLINE_BUCKET_LABELS strings, not new copy (settled, C-2).

Counts are disjoint, computed over the whole filtered book before paging, never cumulative (settled, C-1/C-3).

“All” is a reset, not a fifth bucket. No residual counter for day 31+ / no date. Clicking a pressed horizon pill releases it back to All, as the callout toggles; exactly one control is pressed at a time, and leaving the Forward view clears the selection before any rows are derived.

Same-day callout is “Identification clocks due today” over the running-ID set (active, identification_period, ID date = server Pacific date). Its count is a scope count; selecting it pages the exact-day set.

Row actions are navigation-only: View identification / View exchange / View communications. #2761 supplies mutating verbs later in S3.

The type filter opens on the shipped default, All types. Horizon controls and the callout appear only after the operator selects Delayed (Forward). Every other type view keeps today’s queue behaviour, including the reverse rows the canon mockup shows. The documented ?family=forward query opens on the forward selection for review captures; it is a capture aid, not a default change.

Decisions and provenance

Decision

As drawn · provenance

H-1

Designer: interactive pills vs read-only rows; selected state

Interactive pills; selected state is a saturated border plus a check glyph, tokens only (a faint decorative halo was dropped so words and pixels agree). The callout uses the same pressed border without a check. Independent designer critique, 2026-09-13: approve.

H-2

Compliance review: callout wording and membership

“Identification clocks due today”, running-ID set. Ordinary Compliance review, 2026-09-13: approve.

H-3

Product/Designer: forward-only visibility for this pass

Yes; switch type to see the shipped behaviour preserved. Independent designer critique, 2026-09-13: approve.

H-4

Architect: count contract wording

Minimal additive contract, ADR-059 Decision 4: separately named facet metadata with asOfDate is added; no residual-category counters. Tower architecture acceptance, 2026-09-13.

Action mapping (ADR-059 Decision 8)

Condition (first match)

Label

Destination

EAT-anchored variant (dates not drawn; never routed from them)

View exchange

?tab=overview

Otherwise: missed-ID evidence, or same-day ID membership, or ID-clock row in Past deadline / ≤ 7 / 8–14

View identification

?tab=identification

Any other row

View exchange

?tab=overview

Secondary, nonterminal dated forward rows

View communications

?tab=communications

Base path is the shipped exchangeWorkspaceLink: /app/org/:orgId/admin/exchanges/:exchangeId. Mockup Assign is not delivered here.

Rows worth noticing

Return-due-bound file in ≤ 7 days with a Low badge: horizon follows the shared selector (return due date); the severity badge follows the web-app clock (flat 180-day). This is divergence class 1 from the assessment; it survives #2587 and is not rewritten here.

Missed-identification file outside every horizon: Critical badge under “All” only, because identificationUnmet is an evidence overlay (#2878), intentionally not a horizon.

Exchange-period file whose period ends today: in ≤ 7 days, but not in the same-day identification count.

No-date intake file: reachable under “All” only. No “no date” pill, no inferred safe status.

Completed file with dates still on the row: the classifier excludes terminal statuses before reading any date, so it is in no horizon and no same-day set. Reachable under “All” only.

EAT-anchored variants (reverse exchange-last, reverse exchange-first, reverse improvement — deadlineAnchor: 'eat_acquisition'): both deadline columns read “EAT-anchored” with the shipped title, their stored dates are not drawn and they keep the Low severity override, exactly as isEatAnchoredExchange gates today. Improvement (build-to-suit) and leasehold improvement anchor on the relinquished close and keep their real dates and risk. Hover a type pill for the variant.

Not decided by this page

Whether Phase 2 has started (tower call; the dispatch guard’s remaining condition).

Divergence between the shared and web-app selectors: the return-due-bound case is #3354 (open, not a gate here); the no-identification-date case remains a note.

Applied state of any migration: unknown to this artifact; #2799 adds no new schema dependency.

An EAT-anchored same-day identification signal is deferred and recorded on epic #2625 (comment); no new issue, phase or dispatch.

Deferred implementation counterexample, mirrored from shipped and not changed here: an exchange-period row bound to return_due_date with that date null renders the flat 180-day date under the “your return due date” caption. No fixture draws it; the implementation batch covers it with a test rather than silently changing or entrenching it.

The exchange queue could not be loaded.