Retribution Responsibility Tracer
AI Skills

Retribution Responsibility Tracer

Skip to main content
< All Topics
Print

Retribution Responsibility Tracer

Process skill. Given a scored retribution event (from retribution-assessment-framework), attribute it to the officials in its responsibility chain — and do so under the charter’s load-bearing naming rule. This is the highest-defamation-risk step in the whole tracker; treat every name as an accusation that must survive hostile scrutiny.

The naming rule (non-negotiable)

A person’s name enters responsible[] as the actor of a role ONLY after passing the Documented evidence tier. Below Documented, store the role onlyresponsibility: "inferred", no name — and never render an inferred person as the actor anywhere.

  • The office/agency may always be named (agency) even when no individual is — institutional responsibility is not a personal accusation.
  • Marquee anchors (Comey, Letitia James, Jack Smith, targeted law firms, targeted universities) must be verified to Documented before any responsible name is committed.

Roles to trace

role Who to look for Best evidence
orderer Who directed the act EO signature block; on-record directive; named reporting
approver Who signed off / ratified Agency memo; official statement
signatory Who signed the legal instrument (DOJ subpoenas, indictments, filings) Court docket / signature block (primary_official)
notifier Who delivered the termination / notice Termination email or letter; named reporting
executor Who carried out the mechanics Agency action record
spokesperson Who publicly justified / coordinated Briefing transcript; on-record statement

Method

  1. Start from the instrument. A signed instrument (indictment, EO, subpoena, termination letter) usually contains its signatory — go to the primary record first (PACER/court docket, Federal Register, agency FOIA release). That is the fastest route to a Documented signatory.
  2. DOJ signatory tracing (prosecutions/subpoenas): identify who signed the indictment or subpoena on the docket. A signature block is primary_official and supports naming at Documented tier (e.g. the signer of the Comey indictment).
  3. Corroborate orderers/approvers with multi-outlet reporting. Reporting that names an orderer is credibly_reported — enough to name the role, but the individual stays inferred unless the naming is itself tied to a primary record or on-record admission.
  4. Assign each party evidence_tier (documented / credibly_reported / alleged), source + source_url + source_tier, confidence, and set responsibility:
  • documented → include name (+ profile_slug if a profile exists)
  • inferredomit name; record role + agency only.
  1. Default to inferred when uncertain. If you cannot tie an individual to a primary record, do not name them. A role-only row is always safe; a wrong name is a defamation exposure.

Evidence tiers (from patriot-accountability-profile-standards.mdc)

  • documented — primary record, court filing, signed order, on-record admission, or judicial finding → required to name.
  • credibly_reported — multi-outlet reputable reporting → name the role, not the person.
  • alleged — single-source / contested → tracking only, confidence: low, never named.

Output

Populate the event’s responsible[] with schema-valid parties. When a documented official has (or warrants) an accountability profile, set profile_slug and, where scored, dms_ref. Officials without a profile flow into docs/retribution-profile-backlog.md.

Composes with

retribution-assessment-framework · patriot-retribution-tracker · legal-research-specialist · judicial-decision-analytics-specialist · public-records-research-specialist · corporate-intelligence-investigator · malice-evaluator

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
Please Share Your Feedback
How Can We Improve This Article?
Table of Contents