Dequeue as a policy decision
Most queues ask a worker which jobs it wants. Headgate asks what the fleet's current policy permits it to run. That shift brings rate limits, fairness, concurrency, and poison-pill handling into one atomic admission path instead of scattering them across workers.
Correctness belongs at the store boundary
A claim and its lease are written together, with fencing on every per-job operation. Admission is evaluated atomically inside the store across the PostgreSQL, MySQL, and Redis backends. Policy-rejected jobs remain visible, while lease loss is explicit and actionable.
A system for operators too
The project includes a control API, CLI, embedded web console, OpenTelemetry hooks, payload redaction, and a conformance register that ties capabilities to named evidence. The goal is a queue that is inspectable when the interesting failures happen.