Cross INT Correlation Sweep

Reads across all reporting and proposes that separate reports describe one actor, one place, or one activity, by shared entity, BE number, and grid. Confirming a link is a click; finding it by hand is the work that gets missed.

PrewiredCorrelation Agentv0.1.0trigger: schedulewf.s2.correlation-sweep

Doctrine

Where consolidate and correlate becomes real. The agent surfaces the connection a tired analyst at hour ten of a shift will miss. Assessment sections 4.1 and 6.

Human gate: A fusion analyst confirms every link. The agent proposes connections; it never asserts them into the record.

Trigger: After each reporting batch once wired (today: run manually for a sweep).

Proposed cross INT links with cited reports

The pipeline (5 steps, Arazzo shaped)

01Read all reportingRETRIEVElistReporting
Incoming reporting and analyst reports, newest first.
Success criteria
- Reporting read
Outputs
reports
02Read the entity registerRETRIEVElistEntities
Known actors, facilities, and locations with confidence levels.
Success criteria
- Entity register read
Outputs
entities
03Correlate across INTsREASONcorrelateReporting
Group reports that share a described entity, a BE number, or a grid neighborhood, and keep only groups spanning more than one source discipline.
Success criteria
- Every proposed link cites its reports
- Single source groups discarded
Outputs
proposedLinks
04Analyst confirms the linkHUMAN GATEFusion analystapprover: Fusion analyst
A human confirms or rejects each proposed correlation.
Success criteria
- Each link confirmed or rejected by a human
Outputs
confirmedLinks
05Post confirmed linksNOTIFY (simulated)addTipCueMessage
Share confirmed correlations on the Tip and Cue net for the owning cells.
Success criteria
- Notification drafted
Outputs
notification

Dry run console

Reads are live. Writes are simulated. Nothing changes until a human gate clears.

Agentic binding (the wire, when approved)

s2-fusion-intel-apicrossIntCorrelationSweep

Wired mode posts confirmed links to the net and can update entity confidence after the gate.

Prerequisites live in src/lib/agentic/client.remote.ts.template: published OpenAPI description, accepted Arazzo documents, a scoped server side credential, and an approved agent runtime. Until then, the selector stays on the local dry run engine.

Foundry / MSS twin (after migration)

Agent Studio agent over INTEL_Evidence and INTEL_Entity

Proposed links become link type suggestions the analyst accepts in the workbench.