// RESTRICTED · AUTHORISATION REQUIRED

LOGISTICS.BLAP.DK

NATO defense logistics simulation — access-controlled preview.

LOGISTICS.BLAP.DK
LAYER 2 · LIVE

// NATO DEFENSE LOGISTICS · LAYER 3 SUPPLY AGENT

AUTONOMOUS SUPPLY AGENT

▸ A working simulation · v2 · 3 sovereign nations + a Layer-2 command hub

LLM proposes ➞ Human approves ➞ Code writes & ships

An LLM agent reads SAP through read-only tools, reasons about a battlefield supply need, and drafts purchase and stock-transfer orders — but it never writes. A human reviews and approves; then deterministic, non-AI code calls the SAP BAPIs and dispatches transport. This site shows what has been built so far.

01

How it works

THE LOAD-BEARING INVARIANT
01

Propose

An LLM agent reads SAP through schema-locked, read-only tools, reasons about the supply need, and drafts a purchase order or stock-transfer order. It cannot write to SAP.

02

Approve

A human logistics officer reviews the proposal — the actions, estimated cost, ETA, and the agent's natural-language rationale — in the approval app, then approves or rejects.

03

Execute

Only on approval does a deterministic executor — no AI — call the SAP BAPI write endpoints behind a token guard, then dispatch transport for a carrier and ETA.

// DEMO SCENARIO

CAESAR hydraulic coupling — 28 mm

A CAESAR 155 mm self-propelled howitzer sits deadlined at the Rzeszow forward depot, missing a 28 mm hydraulic coupling from its gun-laying circuit. The agent queries SAP: 12 in stock at Depot Metz, 4 at Toul, 0 forward. It drafts a C-130 stock transfer, Metz → Rzeszow. A human approves. Deterministic code writes the STO, decrements Metz, books the carrier — ETA 2 days.

02

Architecture

v1.0 — THREE LAYERS
Built In progress / ready Planned
LAYER 1
Edge Workshop
Signed equipment event from the front line — simulated via the edge-sim CLI; the hub ingests & persists every event.
SIMULATED
LAYER 2
Central Hub
Event historian · NATO tender flow · failure forecasting · donation ledger · hub-LLM brief & chat. Sovereignty-blind to nation internals.
LIVE
LAYER 3
NATO Agent — one sovereign triplet per donor nation
FRANCE FR
SAP Stub
Approval App
LLM Agent
Ollama (local)
RHEINMETALL RM
SAP Stub
Approval App
LLM Agent
Ollama (local)
POLAND PL
SAP Stub
Approval App
LLM Agent
Ollama (local)
3 NATIONS LIVE
SHARED
Mock Transport
Carrier assignment · deterministic ETA · tracking number.
BUILT
03

Programme

FIVE-PHASE ROADMAP
WEEK 1–2
01

Event simulator

Signed workshop events — equipment, part, GPS, urgency — over the shared event envelope. Shipped as the edge-sim CLI.

Complete
WEEK 2–3
02

Mock SAP MM

SAP MM/PM stub — materials, BOMs, depot stock, lead times, BAPI write facade. SQLite-backed.

Complete
WEEK 3–5
03

Agent + tools

Ollama-hosted LLM with schema-locked tools and a deterministic optimizer. Proposal store. Live in all 3 nations.

Complete
WEEK 5–6
04

Approval gateway

Human review UI — rationale, cost, ETA. Approve or reject; the deterministic executor writes.

Complete
WEEK 6–7
05

Demo + iterate

End-to-end demo: a battlefield part need to an approved, shipped stock-transfer order.

Complete
// CYCLE 1 · FRANCE NON-LLM BACKEND (FOUNDATION) — BUILD DETAIL
  1. 01 Project skeleton & shared package DONE
  2. 02 SAP stub · data model & read endpoints DONE
  3. 03 SAP stub · BAPI write facade DONE
  4. 04 France seed · core dataset & pipeline DONE
  5. 05 France seed · deterministic filler generator DONE
  6. 06 Mock transport service DONE
  7. 07 Approval app & deterministic executor DONE
  8. 08 Tooling, docker-compose & end-to-end demo DONE
// LAYER 2 · CENTRAL HUB (WORKSTREAM F) — BUILD DETAIL
  1. 3A Event historian · durable events, /history/events DONE
  2. 3B NATO tender flow · cross-nation donor resolver DONE
  3. 3C Failure forecasting · /fleet + /forecast DONE
  4. 3D Donation ledger + hub-LLM · isolated /llm brief & chat DONE
  5. 3E Editable registry UI + document upload / RAG NEXT
04

Live theatre

24 PLANTS · 3 NATIONS · LIVE DISPATCHES

Dots are warehouses (hover for plant name). Arrows light up as the system dispatches material across the theatre — no replay, only what's happening now.

05

Deployment map

COOLIFY — *.LOGISTICS.BLAP.DK 
logistics.blap.dk/
├─ sap.france.logistics.blap.dk        SAP stub        ● live
├─ approval.france.logistics.blap.dk   Approval app    ● live
├─ llm.france.logistics.blap.dk        LLM agent       ● live
├─ sap.rm.logistics.blap.dk            SAP stub        ● live
├─ approval.rm.logistics.blap.dk       Approval app    ● live
├─ llm.rm.logistics.blap.dk            LLM agent       ● live
├─ sap.pl.logistics.blap.dk            SAP stub        ● live
├─ approval.pl.logistics.blap.dk       Approval app    ● live
├─ llm.pl.logistics.blap.dk            LLM agent       ● live
├─ centralhub.logistics.blap.dk        Layer 2 hub     ● live (3A–3D)
├─ transport.logistics.blap.dk         Mock transport  ○ not deployed
└─ logistics.blap.dk                   This page       ● live

All three nations now run a fully sovereign triplet — their own SAP stub (with a read-only SAP-cosplay browser at sap.<nation>.logistics.blap.dk), approval app, LLM agent and private Ollama runtime. The seeded network spans 24 warehouses across 3 nations (8 per nation); 3 of those per nation are dynamically provisionable at runtime via POST /bapi/plants or the SAP-cosplay UI — lead-times to every existing plant are auto-generated on creation. The Layer-2 Central Hub is live with its own event historian, cross-nation tender flow, failure forecasting, donation ledger and a network-isolated hub-LLM — explore it at centralhub.logistics.blap.dk (passcode glaucus). The hub stays blind to nation internals: it sees only aggregate, hub-owned data.