PREDICTIVE LAW ENFORCEMENT AND BEHAVIORAL THREAT ASSESSMENT
Fourteen separated stages from collection and identity resolution through nomination, matching, downstream action, retention, redress, and successor continuity.
ANALYTICAL & SAFETY BOUNDARIES
Analytical boundary: “Pre-crime” is an analytical label for an anticipatory decision architecture, not one technology or proof that future conduct can be known. Record retrieval is not prediction; identity matching is not prediction of conduct; association is not guilt; descriptive mapping is not necessarily forecasting; a concern category is not a calibrated probability; a score, tier, list, map, or alert is not lawful authority for coercive action; formal human presence is not meaningful review without time, evidence, independence, authority, and an effective intervention path; forecast accuracy is not demonstrated crime reduction; program silence is not proof of termination; a renamed successor is not proof of functional discontinuity.
Simulation safety boundary: Neutral, non-operational education. No real-person scoring, real targeting, weapons configuration, surveillance deployment, evasion, jamming instruction, or system-defeat guidance.
Source basis: Exact watchlisting, traveler-risk, and FBI TSC AI initiative reports.
ORIENTATION
Watchlisting is a federated decision architecture. A record does not automatically impose the same consequence everywhere and is not itself a charge, warrant, probable-cause finding, or proof of wrongdoing.
WORKING BRIEF
Upstream institutions nominate and resolve identities; downstream agencies act under separate authorities and missions.
A correction is incomplete if stale identities, handling codes, cached summaries, derived features, or successor systems remain unchanged.
COMPLETE DOSSIER
No related page is required to understand this record.
Terms are defined for this site’s evidence method, not as universal legal or clinical definitions.
| Stage | Function | Governance question |
|---|---|---|
| Collection | Acquire biographical, travel, police, intelligence, sensor, or partner data. | Collection authority and purpose limits |
| Ingestion and normalization | Move records into a system and standardize fields. | Data quality, scope, and versioning |
| Identity resolution | Determine whether records refer to the same person or object. | Ambiguity and false-match handling |
| Nomination or rule eligibility | Propose an identity, case, or condition for further processing. | Source reliability and threshold |
| Federated retrieval | Find relevant records or relationships across systems. | Access control and provenance |
| Association and link analysis | Represent relationships among identities, events, places, or records. | Association is not guilt |
| Forecast or prioritization | Estimate risk, anomaly, relevance, or future concentration. | Target definition, base rate, calibration |
| Analyst interpretation | Review evidence, uncertainty, contradictions, and context. | Time, independence, and rejection authority |
| Screening match | Compare a person or object against lists, rules, or profiles. | Identity confidence and handling code |
| Downstream agency decision | Apply the receiving agency’s separate law, policy, and mission. | No universal action from one record |
| Intervention | Screen, question, visit, patrol, support, restrict, detain, or take no action. | Independent legal authority and proportionality |
| Retention and sharing | Store and distribute source, output, and outcome records. | Purpose, recipient, expiration, deletion |
| Correction and redress | Review complaints, correct identities and facts, and communicate outcomes. | Accessible process and direct acknowledgment |
| Successor continuity | Propagate correction and status across renamed, migrated, or successor systems. | Functional continuity and closure proof |
RESEARCH EDITION
This page follows the public method for provenance, confidence, source independence, alternative accounts, limitations, review state, and visible correction.
CONTINUE