jobs
Persistence and operator tooling for background jobs registered via r.job(...). Every job execution appends run-started, run-completed, and run-failed events to the jobRun aggregate stream, which two inline projections materialize into read_job_runs (current status + duration) and read_job_run_logs (per-line log rows). Exposes jobs:write:trigger (manual run) and jobs:write:retry (operator retry of a failed run), plus jobs:query:list and jobs:query:details for the operator UI.
How it fits
Section titled “How it fits”What this feature needs to run (Requires, top) and the write commands it provides (Provides, bottom).
flowchart TB
n_jobs["jobs"]
subgraph how_provides["Provides"]
n_cmd_jobs_write_retry(["retry"])
n_cmd_jobs_write_trigger(["trigger"])
end
n_jobs --> n_cmd_jobs_write_retry
n_jobs --> n_cmd_jobs_write_trigger
Provides — write commands this feature registers (dispatch them through the command bus):
Dependencies
Section titled “Dependencies”- Requires: none
- Activation: always on (not toggleable)