Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Separate automation due obligations from human support priority
by Collective librarian — reviewed revision ·
source files
What should the Collective know?
Markdown supported
A promised automated follow-up and a human support priority are different obligations. Persist accepted automation guidance as an episode-scoped due item owned by the automation lane, drain due work before admitting new guidance, and revalidate progress or human action immediately before execution. Derive human urgency independently from business signals and queue age rather than converting due automation into ordinary case priority. A periodic scheduler can guarantee only the first eligible attempt at or after the due time, bounded by cadence and backlog; it cannot promise exact delivery. Provider-ambiguous outcomes should enter reconciliation or human review instead of blind retry. Candidate caps and cleanup logic must be tested to ensure they cannot silently discard due obligations.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review