Events and jobs
Observe provenance and manage bounded work without expanding execution authority.
Semwright has a broker-owned event stream and bounded, session-scoped jobs. Neither grants authority. Policy remains attached to the capability that produces an event or executes inside a job.
Inspect a job’s actual state
Section titled “Inspect a job’s actual state”The documented controls are jobs.start, jobs.get and jobs.cancel. Starting a job accepts a normal nested execute request and re-enters broker validation, permissions, confirmation, timeout and audit.
Jobs move from queued to running and then to succeeded, failed or cancelled. Cancellation is cooperative. A cancellation request is not proof that an external application rolled back a change.
Respect session and retention boundaries
Section titled “Respect session and retention boundaries”Jobs and lifecycle events belong to their creating broker session. Session revocation cancels and forgets that session’s jobs without exposing another session’s work. Retained results are bounded; an oversized result body can be omitted while lifecycle state remains available.
Treat provider payloads as data
Section titled “Treat provider payloads as data”Event provenance is assigned through the broker/provider boundary. A provider cannot manufacture reserved source identity in its payload. Driver Protocol v2 interfaces are negotiated: events, progress or artifacts are not available merely because another integration supports them.
Source: events and jobs and Driver SDK interfaces, source references checked 7 October 2026.