HARBINGER / TECHNICAL NOTE

Domain-specific analysis

HARBINGER applies domain-specific terminology and rules to analysis.

01

The same data format can have different meanings.

A date or status value raises different questions in different kinds of work. Reading it requires an understanding of the subject, the relevant review criteria, and whose work a change may affect. Interpreting a format and applying domain meaning are distinct tasks.

A Domain Pack applies domain meaning, rules, workflows, and review logic to HARBINGER's common platform. It uses shared investigation and evidence-verification capabilities while defining the questions and criteria relevant to the work.

02

The platform and its domain configuration are separate layers.

HARBINGER is a platform. Its core capabilities cover investigation of facts and evidence; review of assertions, requirements, gaps, and conflicts; detection of differences between records; further investigation and reassessment; and traceability to sources and analysis steps.

Selected domain configurations and customer workflows build on that structure. The shared investigation capabilities support the vocabulary, rules, and review processes configured for the work. Equally, being a platform does not mean every domain configuration and connector is included by default.

03

Actual application adds customer and environment conditions.

Customers in the same domain may have different data, existing systems, workflows, and authority structures. Customer or mission implementation specifies those conditions. Installation environments, networks, models, and integration configurations are addressed through a Deployment Profile.

Platform explanation, domain configuration, customer implementation, and performance evidence therefore have distinct scopes. An adoption review examines the needed domain configuration, connected material, user roles, and actual installation environment.