Files
Siavash Sameni 1e729e4b1d T6.3: Design exploration for federated reputation gossip
Add docs/PRD/PRD-relay-federation-gossip.md comparing 3 approaches:
1. Push gossip — relay broadcasts RepeatAbusive verdicts to peers
2. Pull oracle — peers query a reputation oracle periodically
3. Ban-list distribution — admin signs and pushes authoritative list

For each: wire format, Sybil resistance, convergence, storage,
partition tolerance, failure modes. Open questions block implementation
(trust model, privacy leakage, key infrastructure). Move T6.3 to Blocked
pending reviewer design call.
2026-05-12 19:13:31 +04:00
..

Task Reports

One report per completed task. Filename pattern: T<id>-report.md (e.g. T1.1-report.md).

The template lives in ../TASKS.md under "Report template". Do not deviate from it — the reviewer reads these in bulk and consistency matters.

If a task is reworked after Changes Requested, append a new section to the existing report rather than creating a new file:

## Rework — <UTC timestamp>

**Triggered by:** reviewer feedback "<short quote>"
**Commit:** <new git sha>

### What changed in this round

- ...

### Re-verification output

$ cargo test ...

Then move the task back to Pending Review in the status board.