The Pipeline View: Sortable, Retest-Capable, Visible

The pipeline view (/core/pipeline) is the kanban-style read of the workflow engine. Each stage is a column; each asset is a card; sortable, filterable, and the place where warehouse leads spend a lot of their time.

Sort within a stage

Default sort is by entered-stage-date (oldest first). Alternative sorts: by category, by grade, by client, by SLA-deadline-proximity. The sort persists per user — a tester who wants to work oldest-first stays oldest-first; a manager who wants to see SLA-at-risk first gets that view.

Retest

An asset in a later stage that hits a problem (a buyer’s pre-shipment check fails, a warehouse audit catches a regraded device) needs to go back to testing. The retest action sends the asset to the testing stage with the original grade preserved as a "previous grade" reference and a new audit row marking the retest reason. The original grading audit isn’t erased — the asset has a chain of "graded → retested → graded again" that an auditor can follow.

SLA badges

An asset whose contract defines an SLA gets a deadline. The pipeline card shows a badge — green if comfortable, yellow if approaching, red if missed. The SLA dashboard widget rolls these up at the warehouse level: how many assets are at risk this week, by stage, by contract.

Bulk actions

Select multiple cards in a stage and apply the same action: bulk-advance (with a check that all selected assets meet the next stage’s entry conditions), bulk-retest (with a shared retest reason), bulk-tag (apply a tenant tag for tracking). Used for processing a batch of assets that arrived together and walk through the same path.