Repeatability
High
Distributed locking with Redis, exponential backoff, TTL, and correlation ID logging are well-established patterns with canonical implementations. The task structure is consistent and doesn't require novel invention each time.
Ambiguity Tolerance
Medium
Core requirements are specific (30s TTL, exponential backoff, correlation IDs, lock contention tests), but success criteria around 'comprehensive' logging and test coverage depth leave room for interpretation. A human reviewer will need to judge whether the output is production-ready.
Data & Tool Availability
Medium
The agent needs access to the existing codebase, RabbitMQ consumer logic, and ideally a running Redis instance or mock for test validation. Without the actual source files, the agent must make assumptions about the worker pool structure that may not hold.
Error Cost
Medium
Buggy locking logic could worsen the race condition or introduce deadlocks, but since this is a code change requiring human review and testing before deployment, the blast radius is contained. The original problem (duplicate order processing) is already causing damage, so a bad patch is a real but manageable risk.
Human Judgment Required
Low
The implementation choices here — SET NX PX for Redis locks, UUID correlation IDs, asyncio-compatible backoff — are well-documented best practices. A senior engineer should review the output, but the judgment calls are technical, not relational or ethical.