| type |
REFERENCE |
| domain |
jobs |
| title |
Work and integration |
| audience |
|
| status |
current |
| last_updated |
2026-08-23 |
| framework_version |
v1.0.0 |
| validation |
| date_last_tested |
status |
scope |
2026-08-23 |
passed |
docs/capabilities/work.md - route table verified against leaf targets |
|
Choose the business promise before choosing a queue. Owned execution, a named occurrence, and a
copy of current Entity state are three different capabilities wearing similar clothes - and the
wrong one costs a rewrite.
| The request says |
Fetch |
| "do this in the background" / "run it nightly" / "return fast, finish later" |
background jobs |
| "when X happens, tell Y" / "raise an event" |
events and transport |
| "another service needs the current state of this Entity" |
events and transport - Transport, not Events |
- Jobs own execution state and retry policy. Events own meaning. Transport owns delivery of
current state. The promise decides the connector - never the reverse.
- Awaiting
Raise or Send means the route accepted the items at its stated assurance boundary;
it does not mean handler code finished.
- Do not pick a queue or broker before naming the promise.
- Do not hand-roll retry loops, pollers, or background threads beside Jobs.
For the one-screen maturity view, see
Work and integration in the capability map.