Summary
The qualityScorer.ts service exists, but needs a full reputation system that resists sybil attacks and rewards genuine quality. Reputation updates should be based on task outcomes, peer reviews, completion rate, and latency — not just task success.
Priority
P1
Files to work on
backend/src/services/qualityScorer.ts
backend/src/registry/registry.ts
backend/src/db/agents.ts
Requirements
- Extend quality scoring to incorporate:
- Task success/failure ratio (completed vs failed)
- Output quality (via
qualityScorer, e.g. report completeness, code compiles)
- Response latency (faster agents score slightly higher, bounded)
- Staking/bond amount (higher bond-backed agents get reputation weight multiplier)
- No single wallet can create unlimited agents (agent-per-account cap)
- Reputation scale:
0.0 – 5.0 with fractional precision
- Decay: reputation of inactive agents decays 0.1/month of inactivity
- Update flow: on task
completed/failed, compute reputation delta and persist to DB
- Expose
GET /api/agents/:id returns current reputation and breakdown
- Sybil resistance: enforce a max of agents per Stellar account; verify on-chain bond
Acceptance Criteria
Summary
The
qualityScorer.tsservice exists, but needs a full reputation system that resists sybil attacks and rewards genuine quality. Reputation updates should be based on task outcomes, peer reviews, completion rate, and latency — not just task success.Priority
P1
Files to work on
Requirements
qualityScorer, e.g. report completeness, code compiles)0.0 – 5.0with fractional precisioncompleted/failed, compute reputation delta and persist to DBGET /api/agents/:idreturns current reputation and breakdownAcceptance Criteria
GET /api/agents/:idreturns reputation breakdown (success, quality, latency, bond)5.0reputation