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

Gap to Collection Loop

Standing watch over the gap register and PIR coverage. Raises open gaps that have no collection request working them and drafts the request for the CM to validate.

PrewiredCollection Gap Watcherv0.1.0trigger: schedulewf.s2.gap-collection
Doctrine

The consolidate and correlate to drive collection loop, automated up to the human decision. A gap that opens at 0200 should not wait for a human to notice it. Assessment sections 2.4 and 6.

Human gate: The CM validates before tasking. The watcher raises and drafts; it never tasks a sensor.

Trigger: Continuous watch after wiring (today: run manually for a sweep).

Raised gap listDraft collection requestsTip and Cue notification
The pipeline (6 steps, Arazzo shaped)
  1. 01Read the gap registerRETRIEVElistGaps

    Every gap, with priority, status, progress, and assisting shops.

    Success criteria
    • Gap register read
    Outputs
    gaps
  2. 02Read PIR coverage and active collectionRETRIEVElistPirCoverage + listCollectionRequests

    Coverage math per PIR and every collection request already in flight.

    Success criteria
    • Coverage and collection pictures read
    Outputs
    coveragerequests
  3. 03Find unworked gapsREASONcorrelateGapsToCollection

    Identify open, low progress gaps whose PIR has no active collection request, ranked by gap priority and PIR coverage weakness.

    Success criteria
    • Each raised gap traces to a register record
    • No request duplicated
    Outputs
    raisedGaps
  4. 04Draft collection requestsACT (simulated)createCollectionRequest

    Draft one request per raised gap, discipline taken from the assisting shops.

    Success criteria
    • Draft request prepared per raised gap
    Outputs
    draftRequests
  5. 05Collection Manager validatesHUMAN GATECollection Managerapprover: Collection Manager

    The CM validates weighting and tasking before any request submits.

    Success criteria
    • Human approval recorded
    Outputs
    approval
  6. 06Notify the Tip and Cue netNOTIFY (simulated)addTipCueMessage

    Post the raised gaps to the net so the cells see what is being worked.

    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-apigapToCollectionLoop

Wired mode runs on a schedule trigger and submits requests after the gate; dry run simulates the creates and the net post.

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)
Automate scheduled agent + AIP Logic

The standing watch becomes a Foundry Automate schedule over the INTEL_Gap object set.