Capability-aware action surface
One protocol. Honest engine-specific controls.
Every adapter implements submit_task and advertises only the additional controls it can execute safely. The dashboard gates actions from the connected adapter's capabilities instead of pretending broker-specific operations are universal.
The related dashboard view, captured with sample project data. Open the live demo to try it.
Ships with
- Single Protocol method (submit_task) implemented by every adapter
- Retry and destructive controls require an advertised engine capability
- Dashboard hides or refuses controls the connected engine cannot honor
- A new engine advertises only the actions it can honor and refuses the rest
Highlights
- submit_task is the universal primitive
- Retries never replay the redacted argument copy stored by the brain
- DLQ replay stays engine-specific because consume/ack semantics differ
- Dead letters are read live from the engine's own store where the adapter can list it (RQ's failed registry, Dramatiq's .XQ queues)
Related