Reputation ledger
Quality is derived, not claimed.
Reputation events are written from finalized accepted and rejected findings. The ledger remains empty until a finalized audit exists.
Awaiting first finalized audit
Finalized audits
0
No reputation events can be written yet
Accepted findings
0
Only accepted findings affect quality
Rejected findings
0
False positives are tracked, not hidden
Attackers tracked
8
Frozen A01–A08 identities
Attacker quality ledger
Rates are only shown after finalization; no precision is invented.
| Attacker | Accepted | Rejected | Precision | Last event |
|---|---|---|---|---|
| A01 | — | — | Not computed | None |
| A02 | — | — | Not computed | None |
| A03 | — | — | Not computed | None |
| A04 | — | — | Not computed | None |
| A05 | — | — | Not computed | None |
| A06 | — | — | Not computed | None |
| A07 | — | — | Not computed | None |
| A08 | — | — | Not computed | None |
A dash is not zero performance. It means no finalized event exists. The ledger is populated by the idempotent reputation service after certificate finalization.
How reputation is earned
No self-reported scores.
- 1
Finalized finding
Only accepted or rejected records after certificate finalization count.
- 2
Evidence support
A claim without verified support does not become a quality event.
- 3
Novelty
Section B restatements are rejected and do not earn credit.
- 4
Idempotency
The unique event key prevents double-counting on replay.
Empty until finalization
Honest state, not a synthetic score.
No audit has been finalized in this workspace, so the ledger is empty. The service never writes a reputation event from an unfinished or synthetic record.