Triaging Signals

The Intelligence Feed is your triage inbox — not a dashboard. Every signal here is waiting for a human decision.

1. The Two Types of Signal

Mapped Signals

Signals the engine successfully linked to one or more schedule activities.

Example: "Concrete pour delayed" → [A1020: Foundation Slab]

Floating Signals

Project-level observations that haven't been linked to a specific activity yet.

Example: "Crane operator shortage across site"

2. AI Match Confidence & Multidimensional Scoring

When a signal is extracted, the Forge engine attempts to automatically link it to the project schedule using a Multidimensional Scoring system.

The 5 Dimensions of Matching

Semantic Similarity: Vector search comparing the signal text to activity descriptions.
Temporal Proximity: Comparing the signal's eventDate against the activity's scheduled window.
WBS Context: Matching signal context against the branch nodes of the Work Breakdown Structure.
Trade Alignment: Auto-discovered prefix schemas (e.g., matching a concrete signal to STR- activities).
Historical Patterns: Leveraging past user approvals to prioritize previously established mappings.

You can hover over the HIGH / MEDIUM MATCH badge on a mapped signal to view the visual breakdown of these 5 scores.

3. Configurable Match Thresholds

In your Project Settings, you can configure exactly how the engine behaves based on the composite match score. Because some projects require stricter validation than others, thresholds are environment-specific:

Auto-Link Threshold (Medium Match): The minimum score required for the engine to suggest an activity mapping. The signal remains in the inbox as DETECTED.
Auto-Process Threshold (High Match): The score required to completely bypass the triage inbox. The signal is automatically approved and pushed directly to the Activity Panel as ACCEPTED.

4. The Triage Workflow

Review the CPM Impact Preview

Before making a decision, read the CPM Impact Previewon the signal card. It shows the signal's projected schedule slip, predecessor logic, and estimated financial exposure — all anchored to the current Data Date.

Data Date anchor: The preview is calculated from the last update date, not today — so it reflects the actual CPM state when the signal was detected.

Accept or Dismiss

Confirms the signal as a valid causal factor. The signal's exposure and delay values are locked at this moment and become immutable model artifacts.

Moves to Contributing Signals tab

Dismiss

Removes the signal from the model. Dismissed signals disappear from all surfaces — the feed, activity panels, and the Deviation View impact drivers.

Removed from causal model permanently

Accepted signals surface in the Activity Panel

Once accepted, the signal appears in the Contributing Signals tab of the Activity Detail Panel for any activity it was linked to. You can see all accepted signals for an activity together, with their locked values and aggregated financial impact.

Important: The feed only ever shows detected signals. Once accepted or dismissed, signals leave the feed permanently. If the feed is empty, your model is clean.

5. Signal Lifecycle Indicator

Each signal card shows a 5-step lifecycle indicator. The active step is highlighted — typically DETECTED (new) or LINKED (mapped to activity). This shows you exactly where in the validation chain the signal sits.

DETECTEDLINKEDREVIEWEDACCEPTEDDISMISSED