Run protected work
Use jobs alone for authenticated scheduled or operator-triggered work with durable run state.
Packages: @gj-kit/nest-operations-jobs
Run operations work and notifications
Use protected operations jobs and durable notifications together when one application-owned workflow needs both. Each package still works without the other.
Choose the smallest fit
Section titled “Choose the smallest fit”Deliver durable notifications
Use notifications alone for outbox, relay, quiet-hours, and dispatch policy.
Packages: @gj-kit/nest-notifications
Compose at the application boundary
After a job result, application code may enqueue a notification. Neither package imports, schedules, or authorizes the other.
Packages: @gj-kit/nest-operations-jobs, @gj-kit/nest-notifications
Composition boundary
Section titled “Composition boundary”This guide explains @gj-kit/nest-operations-jobs, @gj-kit/nest-notifications together, but it does not create an installation dependency unless the package relationship table says so.
1. Implement both host stores independently
Section titled “1. Implement both host stores independently”Keep run persistence and notification persistence in the application database boundary.
2. Schedule only the work you own
Section titled “2. Schedule only the work you own”A job may ask application code to dispatch due notifications, but the application owns cadence and authorization.
3. Verify each store contract
Section titled “3. Verify each store contract”Run package-provided contract cases against each host implementation before connecting workflows.