Logistics Hub

Purpose

Logistics Hub organizes receiving, putaway, internal movement, replenishment, staging, loading, quality, dock, and recovery work. New hub task records priority, responsible operator, and operational context instead of relying on informal chat instructions.

Work control

Claim, assign, pause, resume, advance, or escalate work only when the physical state supports it. A quality hold is independent from a checkout or transit record and must be resolved explicitly.

Bulk assignment lists the current scoped Hub queue by task reference, type, priority, and status. Operators select one or more named tasks and an eligible named operator/team; immutable task and user IDs stay internal. A row action preselects that exact task. Drafts preserve every selected task, and an unavailable authorized queue or assignee list fails closed instead of falling back to pasted IDs. Apply sends one bounded transaction for 1–100 unique tasks: the Worker locks and validates the complete set first, then assigns all tasks with individual history events or rolls the entire command back.

Operational filters

The task queue has server-authoritative controls for task type, status, priority, zone, assignee, and due state. Search, filters, page size, and cursor history persist in the route URL so an operator can safely restore the same queue after refresh or navigation. Due state accepts only Overdue, Due today, Upcoming, or Unscheduled; zone matches either the task source or destination location. Clearing filters returns to the complete task queue. These controls apply to Hub tasks; the quality, dock, replenishment, and continuity flow views retain their own typed registers.

The eight flow cells are real register switches, not decorative counters:

• Receiving, Putaway, Picking, and Packing load the task register with an authoritative task-type filter.
• Replenishment loads governed minimum/target rules.
• Quality loads placed holds and their current disposition state.
• Docks loads scheduled dock appointments.
• Continuity loads continuity and recovery runs.

The selected companion register is persisted as hubView in the page URL. Search, status, page size, cursor window, refresh, and Previous/Next navigation stay tied to that view. The Worker returns exact totals and stable timestamp-plus-ID cursors; invalid or cross-filter cursors fail instead of silently changing the result window.

Counts and attention signals

Open tasks, unassigned work, quality holds, dock arrivals, every flow-cell count, and the matching attention signals come from the exact Hub summary contract. They do not use the ten visible table rows as a substitute for the full queue. If the summary fails, operators must see an error/retry state rather than an authoritative-looking zero.

Keyboard and assistive technology

Each flow cell is a named button with aria-pressed state. Settings-style tab controls elsewhere in AMS use one selected tab, roving focus, and Left/Right/Home/End keyboard movement. Native dialogs keep focus inside while open, close with Escape, and restore focus to their trigger. Current local certification checks names, labels, duplicate IDs, tab state, dialog focus, mobile overflow, and axe WCAG A/AA rules across all ten routes. Manual screen-reader and hosted role testing remain release gates.

Human-safe operations

Use work data to coordinate capacity and safety. Do not use it to silently rank volunteers or substitute suggested routing for an operator’s safety judgement.