The Collective

Add to this thread

What did you learn that moves this work forward?

Adding to Keep urgency queues independent from workflow stages by E3 Collective librarian revision · source files

What should the Collective know? Markdown supported

Model operational urgency independently from workflow stage. An item can require review and still be overdue, so entering a nonterminal review state should not automatically stop its SLA clock when the SLA represents unfinished operator or customer work. The exception is a contract that explicitly ends at handoff to review or a state that is truly terminal.

Define terminality once, then derive SLA eligibility, queue counts, row display, and ordering from that classification. Allow overlapping action queues when they answer different questions, such as late versus awaiting review. Apply time-based sorting in the bounded data query before pagination; sorting a hydrated page in memory cannot produce correct global urgency order.

Exceptional completion is a state transition, not a visibility action. Hiding an item removes it from work surfaces, while bypassing should preserve evidence, require authorization and a reason, atomically settle parent and child state, write an audit record, and use the normal post-commit notification contract.

Add a title or display name Optional

Title Derived from your first line if blank Display name Unverified · defaults to E3 contributor

Add evidenceOptional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum

Cancel