Target Domain

Overview#

A counter-narcotics analyst opens a new case after a port authority seizure. Within minutes, she has registered the vessel captain as a target, classified him at High threat, linked his profile to a previously dormant Person record, and flagged the cargo company as a second target at Medium threat. That ordered starting point, distinct from unstructured notes or a generic contact list, is what the Target domain provides.

Targets are the named subjects of interest within active investigations. They can represent persons, organisations, assets, or other entities relevant to a case. Each target carries threat level classification, secrecy controls, status tracking, and links to detailed profile records stored in PostgreSQL. Multi-tenant organisation isolation ensures targets from one investigation team are never visible to another.

Key Features#

Target Registration: Create and manage investigation targets with names, descriptions, types, and association to specific investigations for organised case tracking.
Threat Level Classification: Assign threat levels to targets (Critical, High, Medium, Low, None) to indicate assessed risk and priority for investigative attention.
Secrecy Controls: Apply secrecy level classifications to targets to control visibility and access based on personnel clearance and need-to-know requirements.
Profile Linking: Link targets to detailed profile records (persons, organisations, assets) for comprehensive intelligence about each subject of interest.
Status Management: Track target status through the investigation lifecycle, including active monitoring, completed analysis, and archived records.
Soft Deletion: Hide targets without permanently removing them, preserving data integrity while removing them from active views when they are no longer relevant.
Tag-Based Organisation: Apply tags to targets for flexible categorisation and filtering across investigations and analytical workflows.
Country Association: Associate targets with geographic locations to support jurisdictional analysis and international coordination.

Mermaid Diagram#

Use Cases#

Law Enforcement: Maintain a structured list of all subjects of interest within a criminal investigation, with threat assessments and status tracking that update as the case develops.
Defence Intelligence: Register persons, organisations, and assets as targets in multi-national operations where secrecy controls and POLE model linkage are essential for information sharing.
Financial Crime: Cross-reference targets appearing in multiple investigations through profile linking to surface previously unknown connections between fraud networks and their associates.
Organised Crime Units: Organise target information with tags, descriptions, and profile links to build comprehensive intelligence packages that can be handed off between analyst teams.

Integration#

The Target domain connects with investigative workflows across the platform:

Investigation Management: Targets are associated with their parent investigations.
Profile Management: Targets link to detailed person, organisation, and asset profiles using the POLE model (Person, Organisation, Location, Object, Event).
Threat Intelligence: Target threat levels inform broader threat assessments.
Evidence Management: Evidence items can be associated with specific targets.

Open Standards#

POLE Model (Person, Organisation, Location, Event/Object): Targets link to detailed profile records structured according to the POLE intelligence model, enabling investigators to associate each subject of interest with persons, organisations, assets, and events.
Traffic Light Protocol (TLP), FIRST Standard: Secrecy controls on targets map directly to TLP:WHITE, TLP:GREEN, TLP:AMBER, and TLP:RED, governing information-sharing boundaries for law enforcement and intelligence communities.
NATO and EU Security Classification Levels: The secrecy classification system extends to NATO RESTRICTED/CONFIDENTIAL/SECRET/TOP SECRET (COSMIC) and EU RESTRICTED/CONFIDENTIAL/SECRET/TOP SECRET, supporting multi-national operations and multi-level security enforcement.
ISO 3166-1 (Alpha-2 and Alpha-3 Country Codes): Country association on each target uses ISO 3166-1 two- and three-letter codes, enabling jurisdictional filtering and international coordination access controls.
GraphQL (June 2018 Specification): All target queries and mutations, creation, retrieval, metadata update, soft deletion, are exposed via a typed GraphQL API with camelCase field conventions and permission-guarded resolvers.
OAuth 2.0 / JSON Web Tokens, RFC 6749 / RFC 7519: Target endpoints require RS256-signed JWT bearer tokens issued by the platform identity service; all access control decisions are made against claims in the verified token.
RFC 4122 (Universally Unique Identifiers, UUID): Every target record is assigned a UUID v4 identifier at creation, conforming to RFC 4122, ensuring globally unique and collision-resistant record references across tenants.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14