Intelligence requirement workbench
Analysts ask questions. Requirements orchestrate collection, evidence, models, and resulting intelligence objects — not only reactive alerts.
What evidence supports or refutes POLARIS as a potential source of the 29 April 2025 marine anomaly?
- · Retain AIS correlation claims from source materials
- · Seek multi-provider AIS validation (future)
- · Seek spectral / chemistry confirmation (future)
- · Enumerate alternative vessel hypotheses
- · mod-candidate-vessel
- · nikoi-2025-04-29
- · candidate-polaris
Causal attribution must remain separate from association score.
How should competing location / EEZ claims for the Nikoi case be represented to analysts?
- · Surface Source A vs Source B claims
- · Mark SYSTEM STATUS: SOURCE CLAIMS DIFFER
- —
- · ev-eez-claim
- · ev-location-claim-a
Disagreement is provenance functioning correctly.
Which high-confidence environmental events have occurred within the SMEIR during the last seven days?
- · Requires live observation adapters
- · Phase 1 uses historical replay only
- · mod-singapore-nexus
- —
Architected; not live in Phase 1.
Which vessels in the Singapore–Bintan regional system currently show multiple deceptive-shipping indicators?
- · Requires licensed or public AIS ingest
- · Requires identity and watchlist context feeds
- · mod-rendezvous
- · mod-sts-assessment
- —
Do not invent a regional vessel list. POLARIS is a pollution-event candidate, not a shadow-fleet finding.
Which vessel rendezvous events occurred close to sensitive marine receptors?
- · AIS encounter detection
- · Overlay MPA / coral / seagrass / mangrove / tourism
- · mod-rendezvous
- —
Overlap ≠ environmental harm. No encounters sourced.
Are any vessels associated with the Nikoi pollution case also showing identity, AIS, or rendezvous anomalies?
- · Inspect POLARIS identity string in source materials
- · Do not reconstruct an AIS gap without a track
- · Keep pollution association separate from behavioural anomaly
- · mod-candidate-vessel
- · mod-sts-assessment
- · vessel-polaris-477300300
- · sts-polaris-insufficient
No identity anomaly, AIS gap, rendezvous, or watchlist record is asserted. Not a shadow-fleet case.
Which watchlisted vessels are operating within the intelligence region, and what behaviour is actually observed?
- · Ingest official lists via Worker secrets
- · Join to AIS only when both exist
- —
- —
Listing without observed behaviour is incomplete intelligence. Behaviour without a listing is not evasion.
What are the most consequential environmental changes within the EMSEA AOI this week?
- · Requires regional change products
- · Delayed SST/chlorophyll tiles are context, not a change feed
- —
- —
Architectural target. Not a Phase 1 live obligation.
Where are SST anomalies coinciding with coral or fisheries receptors?
- · SST anomaly tiles available as delayed public context
- · Coral / fisheries receptor layers not loaded
- —
- —
Coincidence requires both layers. Receptor data are SOURCE UNAVAILABLE.
Which freshwater or sediment plumes cross jurisdictional boundaries?
- · Requires discharge, ocean colour classification, and EEZ context
- · mod-freshwater-pulse
- · tp-straits-land-sea
Qualitative pathway exists. Live pulse detection is not faked.
Which environmental events outside Singapore could affect the Singapore and Straits case-study area?
- · EMSEA envelope is the collection frame
- · SMEIR is the case-study lens
- · Nikoi is the worked example of extra-Singapore relevance
- · mod-singapore-nexus
- · mod-transboundary
- · nikoi-2025-04-29
- · tra-nikoi
The product story is regional platform → EMSEA → Singapore case study → Nikoi event.
Regional architectural targets
- Where is reclamation footprint expanding?
- Which blue-carbon ecosystems show measurable extent change?
- Where are fishing pressure, habitat stress and ocean-state anomalies coincident?
- Which coastal mining or land-clearing areas show downstream sediment responses?