Skip to content

P2: write analyst workflow SOP document #162

@yohei1126

Description

@yohei1126

Context

Annex A includes an "operational scenario" narrative but no formal Standard Operating Procedure (SOP) for how analysts and patrol officers use arktrace day-to-day. Cap Vista will need this for analyst onboarding.

Required

Prepare a 2–3 page SOP document covering:

  1. Alert receipt — watchlist update cadence, thresholds, notification channels (SSE, email)
  2. Review tiers — Confirmed ≥0.7, Probable 0.5–0.7, Suspect <0.5, Cleared, Inconclusive
  3. Evidence review checklist — SHAP signals, causal ATT, ownership chain, last 10 AIS positions, GDELT context
  4. Dispatch decision — sign-off authority, decision record, brief generation
  5. Feedback loop — patrol outcome recording, manual label input, model recalibration trigger

Deliver as _outputs/arktrace-sop.pdf and include in Week 7 trial report deliverables.

Acceptance criteria

  • _outputs/arktrace-sop.pdf exists (or docs/sop.md at minimum)
  • SOP is referenced in Annex A Week 7 deliverables list

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions