Probbl Signals

From possible
to probable.

Signals identify meaningful departures from established patterns, then show the observations and relationships that contributed to the result.

Example signal

Why did Avery Bell receive an 87?

A Probbl is assembled from weighted observations, inferred relationships, and the agency’s configured relevance rules.

87confidence
Activity varianceOpen · elevated relevanceGenerated Sep 6, 2026 · 01:49
Open Avery Bell’s record
+31
Observation class

Location deviation

High influence

A linked device appeared outside its recurring 90-day activity corridor during an agency event.

How this was calculated +

The device cluster was observed within a 180-meter confidence area at 01:38. The location falls outside 98.6% of the cluster’s prior overnight observations.

The cluster-to-person link is probabilistic. Presence indicates an associated device, not necessarily the person.
+24
Correlation class

Vehicle co-presence

High influence

A vehicle associated with the same household was observed three minutes after the device presence event.

How this was calculated +

Plate 7LXE229 was read 0.4 miles east of the location confidence area. Direction and time were consistent with departure from the event corridor.

The vehicle is registered to Jordan Lee and associated with Avery Bell through shared-address and repeat-location evidence.
+17
Graph class

Association relevance

Moderate influence

A second-degree connection links the subject’s household to a person with an active agency watch.

How this was calculated +

Jordan Lee and Riley West have 11 recurring co-presence events and one shared commercial account. Riley West appears in an active Bellwether agency watch.

Avery Bell has no recorded direct contact with Riley West. Relevance is inherited through the graph.
+15
System class

Source coherence

Supporting influence

Independent commercial, partner, and agency sources align closely enough to increase confidence in the combined interpretation.

How this was calculated +

Temporal and geographic agreement among four records exceeded the agency’s coherence threshold. No single record independently supports the resulting narrative.

Coherence increases confidence in correlation. It does not independently establish causation or personal presence.
Methodology

Explainable inputs.
Configurable meaning.

Probbl separates observation confidence from operational relevance, allowing agencies to decide which combinations warrant attention.

01

Observe

Ingest source records with native timestamps, identifiers, locations, and provenance.

Technical detail

Raw records are normalized into event objects. Probbl retains source-specific confidence, licensing restrictions, and correction status.

02

Resolve

Associate each observation with likely entities in the Commonplace Graph.

Technical detail

Probbl uses stable identifiers, normalized contact data, device clusters, recurring location patterns, household proxies, and association history.

03

Compare

Measure the observation against an individual or cohort baseline.

Technical detail

When personal history is sparse, agencies may permit comparison with a behaviorally similar cohort until an individual baseline matures.

04

Score

Combine confidence and agency relevance into a ranked signal.

Technical detail

Agency configuration determines thresholds and factor weights. Protected characteristics may be excluded as direct inputs while correlated proxy variables remain present.

Context Pulse

From score
to attention.

A score becomes operational when it crosses a configured threshold, persists long enough to satisfy policy, and matches a route with people available to act.

  1. 01
    MONITORING SCOPE

    Define what may change.

    Monitor a person, household, vehicle, device, address, relationship cluster, behavioral cohort, event corridor, or geographic area.

    Technical scope +

    Monitoring can be assigned directly or inherited when a newly resolved entity enters an already monitored graph neighborhood. The inherited entity need not appear in the originating agency record.

  2. 02
    THRESHOLD POLICY

    Decide what matters.

    Require agreement among signal confidence, operational relevance, source diversity, and a minimum persistence window.

    Example policy +

    confidence ≥ 80 · relevance = high · source classes ≥ 3 · persistence ≥ 4 min. Customer policy determines whether inherited associations may satisfy relevance.

  3. 03
    ATTENTION ROUTE

    Put context in motion.

    Send a Priority Context brief to an investigator, supervisor, RTCC queue, dispatch workflow, or nearby authorized field unit.

    What can begin automatically? +

    A brief may be created, exposed, and routed without a named complainant, reported offense, direct agency observation, or individual user search. Agencies determine whether the result supports observation, contact, or another response.

Signal lifecycle

A signal can close.
The context remains.

Probbl preserves the history needed to explain what the system showed, what the user did, and what later information changed.

1

Open

The signal becomes visible to users whose role and purpose match agency policy.

2

Review

A user can confirm, escalate, dismiss, or leave the signal unresolved.

3

Retain

Inputs, outputs, user actions, and the original score are preserved for audit and model evaluation.

4

Reconsider

A dismissed signal may contribute to a future signal when new observations materially change its relevance.

A necessary distinction

Confidence is not certainty.

A score of 87 means the configured model found strong agreement among the available observations and associations. It does not mean there is an 87% chance the subject committed, intends, or knows anything.

Probbl makes this distinction visible in the interface. Agencies remain responsible for how contextual signals affect encounters, inquiries, and investigative decisions.

Read the human judgment principle