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.
Mockup of the dashboard view for this feature. Live-reloading and themed to match your dashboard.
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
- Adding a new engine drops from ~15 methods to ~6
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