NATO maritime

A defence-style maritime intelligence scenario — situation brief, AIS contact log, intel fusion, commander's decision memo, after-action report.

The NATO maritime example demonstrates Scrydon deployed against a defence-style maritime intelligence workload. It ties together structured contact data, typed maritime objects, and a process-flow that drives from situation brief through to after-action report.

What it models

A maritime task group with:

A situation brief setting the operational context.
An AIS contact log (vessel tracks, contacts of interest).
An intelligence fusion product combining open-source and classified inputs.
A commander's decision memo.
An after-action report capturing the lessons learned.

Download

The NATO process pack ships as a downloadable Scrydon Pack bundle (it is not auto-installed in every tenant):

Download nato-1.0.0.scrydon-pack.tar.gz

Import into a workspace:

curl -X POST "$SCRYDON_URL/api/packs/import?organizationId=$ORG_ID" \
  -H "Cookie: $SESSION_COOKIE" \
  -F "file=@nato-1.0.0.scrydon-pack.tar.gz"

For the full step-by-step walkthrough, see the NATO OODA — end-to-end tutorial.

Setup

Download and import the pack (see above).
Upload the contact-log CSV to a managed table.
Install the NATO maritime ontology pack — typed Vessel, AISContact, Incident, Region objects.
Set the documents' clearance to SECRET (org owners only).
Open the process-flow workflow and walk through the stages.

What's interesting about it

Document clearance is genuinely restrictive here — at SECRET, only org owners read the documents. The system enforces this at every layer.
Air-gapped deployment is the realistic deployment model. The example works as a fully offline scenario; the air-gapped deployment docs cover the install.
Self-hosted AI is the default for this scenario — no cloud LLM calls. Self-hosted vLLM or Ollama integrations resolve the agent's model.

Sample data

In public/static/nato/:

01-situation-brief.md
02-ais-contact-log.md
03-intel-fusion-product.md
04-commanders-decision-memo.md
05-after-action-report.md

Knowledge base clearance — the clearance levels the example uses.
Deployment → Air-gapped — the realistic deployment posture.
Compliance → SecNumCloud — sovereignty considerations for similar deployments.