A signal for review
How a weekly anomaly becomes a signal for review by competent authorities, never a public warning.
End to end on the longest path: about 12.3 d of proposed target service levels, before the jobs that run with no fixed end. Gates wait for the people named; bars with a fading end have no fixed length.
- Anomaly detectedDetect · Pulse nowcast · weeklyStandardised anomaly vs own historyPulse nowcast
- Sources verified matrix · per streamVerify · Data stewards · 1 dayEach stream checked · Licence admits useLicence registerProvenance (W3C PROV)
- Analyst review approvalAssess · Analysts · 2 daysContext, couplings, confidencePostgreSQL ledger (row-level security)
- Information for competent authoritiesHand off · Secretariat · 1 dayShared for review, not a warningNXS-GRX (canonical data, provenance and risk) gateway
- Logged and watchedHand off · Pulse nowcast · ongoingOutcome tracked for verificationPostgreSQL ledger (row-level security)Pulse nowcast
| Artifact | Job | Who | Stage |
|---|---|---|---|
| Signal candidate | Anomaly detected | Pulse nowcast | Detect |
| Source check | Sources verified | Data stewards | Verify |
| Assessment | Analyst review | Analysts | Assess |
| Handoff record | Information for competent authorities | Secretariat | Hand off |
| Verification record | Logged and watched | Pulse nowcast | Hand off |
Solutions that use this journey
5 components
Each job names the component it runs on; open a job on the canvas for its steps, checks and artifacts.