------Z --- --
102105012
All workflows

RFI Triage and Routing

An RFI arrives. The agent proposes the PIR it supports, the cell that should own it, and a draft EEI, all grounded in current holdings so duplicates are caught before they cost a collection asset.

PrewiredRFI Triage Agentv0.1.0trigger: eventwf.s2.rfi-triage
Doctrine

The single highest frequency S2 task and the clearest early win. Triage that queues behind the Collection Manager becomes a draft waiting for a confirm click. Assessment section 6, first workflow.

Human gate: The Collection Manager confirms routing. The agent proposes; it never routes on its own.

Trigger: A new RFI lands Unassigned (today: run manually against any RFI).

Recommended PIR linkRecommended owning cellDraft EEIRouting proposal
The pipeline (6 steps, Arazzo shaped)
  1. 01Select the RFIRETRIEVElistRfis

    Pull the target RFI, or the oldest one with no assigned section.

    Success criteria
    • Exactly one RFI selected
    • RFI is not already routed
    Outputs
    rfi
  2. 02Match against PIRsREASONscoreInformationNeedAgainstPirs

    Compare the information need against every active PIR by shared analytic vocabulary and recommend the strongest supporting requirement.

    Success criteria
    • A best match PIR identified or an explicit no match finding
    Outputs
    recommendedPirmatchEvidence
  3. 03Recommend the owning cellREASONrecommendOwningCell

    Weigh the discipline signature of the request against each production cell, with current cell load as the tiebreaker.

    Success criteria
    • One cell recommended with stated reasons
    • Cell load considered
    Outputs
    recommendedSectionloadPicture
  4. 04Draft the EEIREASONdraftEssentialElements

    Decompose the information need into a draft essential element of information.

    Success criteria
    • Draft EEI produced from the stated need, nothing invented
    Outputs
    draftEei
  5. 05Collection Manager confirmsHUMAN GATECollection Managerapprover: Collection Manager

    The CM reviews the proposed PIR link, cell, and EEI before anything routes.

    Success criteria
    • Human approval recorded
    Outputs
    approval
  6. 06Route the RFIACT (simulated)assignRfiSection

    Assign the RFI to the confirmed cell and open the cell task.

    Success criteria
    • RFI status becomes Assigned
    • Routing log row written
    Outputs
    routedRfi
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-apitriageAndRouteRfi

Wired mode executes assignRfiSection and createRfiTask through the platform after the gate; dry run records them as simulated writes.

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)
AIP Logic function + Automate trigger on INTEL_RFI creation

The gate becomes an approval task; the act steps become scoped ontology Actions.