sm-abuse-report's own README names its family directly: sm-arp proves an action happened, sm-aae proves it was authorized, sm-abuse-report proves someone said one of those was harmful — and ties that accusation to the evidence it's about. Every citation a report makes points at one of the first two; sm-abuse-report itself carries no evidence, only pointers to it.
The accusation
Abuse Report Protocol
This library. A signed, per-reporter hash-chained accusation citing existing evidence by hash — protocol, reporter_id, accused_id, accused_role, category, evidence_refs, narrative, prev_hash, issued_at, sig, pubkey. It signs whatever category and narrative it is given; it does not adjudicate them.
The evidence a report cites
Agency Receipt Protocol
Portable, cryptographically signed receipts an agent emits when it acts — the record that an action happened. A report with evidence_refs[i].type = "receipt" cites one of these by hash; verify_evidence_citation recomputes that hash the same way sm_arp.receipt_hash does. See agencyreceipts.ai.
Attested Action Envelope
A signed, per-agent hash-chained record of a pre-action authorization verdict — what an agent was permitted to do, refusals included. A report with evidence_refs[i].type = "envelope" cites one of these by hash, computed the same way sm_aae.envelope_hash does. See agentenvelope.ai.
The named, not-yet-wired direction
Portable Reputation Credential
A verifiable, recomputable reputation credential built over an agent's sm-arp receipt history — reputation_score and validity_rate, wrapped as a W3C Verifiable Credential and recomputed, not trusted, at chapter admission. sm-abuse-report's WHITEPAPER names a future integration explicitly: a confirmed report could someday feed reputation. It does not yet. No report changes any score automatically in this version — the two libraries are related by design intent, not by a wired dependency.
Out of scope for sm-abuse-report. None of these companion libraries are dependencies of sm-abuse-report — the library itself depends only on cryptography. Composition happens at the level of what a caller does with the eleven fields: cite a receipt or envelope hash, and sign.