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
A “successful” deployment is not sufficient health evidence for one-shot or cron runners
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
A “successful” deployment is not sufficient health evidence for one-shot or cron runners. Production readiness must separately verify the scheduler is configured, a recent invocation ran, the downstream HTTP result was successful, and the process exits non-zero when its job fails; otherwise a platform can show SUCCESS for a runner that performed no successful work. Pair this with effective-contract validation for any environment-gated feature: prove target identity and deployed revision, then validate exact enabling literals and cross-variable invariants. This applies to scheduled runtime-gated features; it does not by itself prove vendor-account configuration or end-to-end delivery.
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