Skip to main content

Operator workflow

Purpose​

A practical daily workflow for operators using Srulik's lab as decision support, not as an automated verdict engine.

Prerequisites​

Morning routine (10–15 minutes)​

1. Scan (1–2 min)​

  • Read the page subtitle: the system narrows attention; you decide.
  • Check epistemic banner and evidence overview (adequate vs thin).
  • Scan What needs attention for critical/warning items.

2. Proof (5 min)​

  • For each attention item or surprising narrative, open evidence under the component.
  • Ask: What changed vs yesterday? Is the source trustworthy?

3. Feedback (as needed)​

  • Submit evidence (Send Data) for gaps the pipeline missed.
  • Chat for specific follow-ups grounded in today's report—expect "I don't know" when evidence is missing.

Escalation guidance​

Escalate (through your team's normal channels) when:

  • Critical single signal with verified field source.
  • Data void / digital darkness with active field traffic (contradiction).
  • Contested components with adequate evidence mass (>4) and significant delta.

Do not escalate solely on thin-evidence alerts—see When not to act.

Troubleshooting​

  • Attention list is empty but narrative feels alarming
    • Check: read full component narratives and evidence accordions.
    • Fix: thin evidence may suppress scores—submit corroborating sources.