# 007 — DHT Replication and Provider Records

- Area: `pkg/dht/*`
- Priority: Medium

## Background
Current DHT layer uses simple PutValue/GetValue and single-peer announcements. For scale and resilience, use provider records and configurable replication.

## Scope / Deliverables
- Add provider record publishing for UCXL content keys; discover providers via Kademlia provider API.
- Implement basic replication policy: target replication factor, periodic reprovide, and cleanup.
- Track providers in metadata (peer IDs) and return multiple sources in `DiscoverContentPeers`.

## Acceptance Criteria / Tests
- Multiple nodes can become providers for the same UCXL key; discovery returns all.
- Reprovide job runs on schedule; metrics expose counts.

## Notes
- Coordinate with Issue 003 so UCXI resolver consumes provider results.