92779523c0
Comprehensive multi-agent implementation addressing all issues from INDEX.md: ## Core Architecture & Validation - ✅ Issue 001: UCXL address validation at all system boundaries - ✅ Issue 002: Fixed search parsing bug in encrypted storage - ✅ Issue 003: Wired UCXI P2P announce and discover functionality - ✅ Issue 011: Aligned temporal grammar and documentation - ✅ Issue 012: SLURP idempotency, backpressure, and DLQ implementation - ✅ Issue 013: Linked SLURP events to UCXL decisions and DHT ## API Standardization & Configuration - ✅ Issue 004: Standardized UCXI payloads to UCXL codes - ✅ Issue 010: Status endpoints and configuration surface ## Infrastructure & Operations - ✅ Issue 005: Election heartbeat on admin transition - ✅ Issue 006: Active health checks for PubSub and DHT - ✅ Issue 007: DHT replication and provider records - ✅ Issue 014: SLURP leadership lifecycle and health probes - ✅ Issue 015: Comprehensive monitoring, SLOs, and alerts ## Security & Access Control - ✅ Issue 008: Key rotation and role-based access policies ## Testing & Quality Assurance - ✅ Issue 009: Integration tests for UCXI + DHT encryption + search - ✅ Issue 016: E2E tests for HMMM → SLURP → UCXL workflow ## HMMM Integration - ✅ Issue 017: HMMM adapter wiring and comprehensive testing ## Key Features Delivered: - Enterprise-grade security with automated key rotation - Comprehensive monitoring with Prometheus/Grafana stack - Role-based collaboration with HMMM integration - Complete API standardization with UCXL response formats - Full test coverage with integration and E2E testing - Production-ready infrastructure monitoring and alerting All solutions include comprehensive testing, documentation, and production-ready implementations. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
31 lines
1.6 KiB
Markdown
31 lines
1.6 KiB
Markdown
# 012 — SLURP Idempotency, Backpressure, and DLQ
|
|
|
|
- Area: `pkg/integration/slurp_client.go`, `pkg/integration/slurp_events.go`, config
|
|
- Priority: High
|
|
|
|
## Background
|
|
SLURP event delivery has retries and batching but lacks idempotency keys, circuit-breaking/backpressure, and a dead-letter queue (DLQ). Under failure/load this can produce duplicates or data loss.
|
|
|
|
## Scope / Deliverables
|
|
- Idempotency:
|
|
- Generate a stable idempotency key per event (e.g., hash of {discussion_id, event_type, timestamp bucket}).
|
|
- Send via header `Idempotency-Key` and include in body for server-side dedupe (if supported).
|
|
- Backpressure & Circuit-breaker:
|
|
- Add exponential backoff with jitter and max retry window.
|
|
- Implement a circuit-breaker that opens on consecutive failures, stops sending for a cooldown, then half-open probes.
|
|
- DLQ & Replay:
|
|
- Persist failed events (JSONL or lightweight queue) with reason and next-attempt time.
|
|
- Add a background replay worker with rate limiting and visibility into backlog.
|
|
- Metrics & Logging:
|
|
- Prometheus counters/gauges: events_generated, sent, failed, deduped, dlq_depth, circuit_state; latency histograms.
|
|
- Structured logs for failures with keys.
|
|
|
|
## Acceptance Criteria / Tests
|
|
- Under induced 5xx or timeouts, client opens breaker, stops flooding, writes to DLQ, then recovers and drains when service returns.
|
|
- Idempotent resubmissions do not create duplicates (server returns success with same id), counters reflect dedupe.
|
|
- Unit tests for backoff, breaker state transitions, DLQ persistence, and replay.
|
|
|
|
## Notes
|
|
- Keep DLQ pluggable (file-based default); allow disabling via config.
|
|
|