BASTION · pre-release
One sealed record of everything that happened at your site.
- A light over the plant, a ship over your cable, a tanker with doubtful papers, an AI copilot asking to change a setpoint: one timeline, every piece checked.
- When the same ship turns up in several places, you see it: the guards' bearings cross where it went AIS-silent, it crossed the cable at the fault, its insurer is on no register.
- The EU 24-hour reporting clocks start when you knew. BASTION shows what is due to whom, and seals the proof.
The layers
Five questions, one file.
Each layer works on its own and seals its own result. BASTION checks every seal and joins them. Each sample is a PDF built from one simulated night, with the sealed file and every input attached inside.
Each report is checked against the planets, the bright stars, satellites, aircraft (ADS-B), drones that broadcast Remote ID and the cloud cover. You get EXPLAINED, POSSIBLY, or NOT EXPLAINED: follow it up. A drone that broadcasts Remote ID is named, with where its operator stood. It never says "no drone". Two guards' compass bearings are crossed to a position, and the ships offshore at the time are listed. A phone form takes the compass bearing, because that makes the answer far better.
Your own fault time and position, joined with the AIS tracks. You see every crossing, crossings while AIS was off, and anchor-drag signatures: "at anchor" but moving, or a sustained drop in speed. Vessels are ranked against the fault, with the wind shown, and the claim file is sealed for your lawyers and insurers. With no fault, it keeps a standing log of who crossed.
The P&I entry and the state certificates (CLC, Bunkers, Wreck) are checked against each other, the ship's own declaration, the IMO check digit, the MMSI country digits, the International Group club list and your registry list. Each ship comes out HOLDS TOGETHER, EXCEPTIONS or RED FLAGS. It never says forged: ask the insurer. A coastal authority can run its whole challenge log: each radio answer against the papers sent and against earlier answers, so two flags, one MMSI on two ships, or an insurer switch while the old cover was still valid come out.
An AI copilot next to OPC UA or Modbus may read. Every write waits for two named people, never the agent itself, and is checked again before it goes out. Alarm texts that carry instructions are flagged. Every decision goes into a hash-chained ledger.
NIS2 (24 h, 72 h, one month), CER (24 h, one month), the CRA (24 h, 72 h, final report) and the AI Act's serious-incident reports (2 days when AI disrupts critical infrastructure, 10 days for a death, 15 days otherwise). Each starts from the moment you became aware, which is kept in a log that shows any later edit. Where a law says only "immediately", you see the hours it took, not an invented deadline. For each stage you get a draft with what the article asks for and the sealed facts on record.
The demo night
One simulated night, every layer.
- 22:09
- A tanker on a fictional fraudulent flag, "at anchor" offshore, goes AIS-silent.
- 22:40
- Two guards report a light. Their compass bearings cross 0.7 km from where the tanker went silent. A third report is Jupiter.
- 22:50
- The control-room copilot reads an alarm text that carries an instruction, then asks for a large setpoint jump. The instruction is flagged and the request refused.
- 23:18
- The same tanker, AIS back on, still "at anchor" at 4 knots, crosses the export cable as it faults.
- Papers
- Its insurer and its registry are on the fraudulent list.
- Clock
- The NIS2 early warning went out late; CER was on time.
Said first
What this is, and what it is not.
- Pre-release
- Every layer has run on simulated data. The sky layer has run on real satellite data and a real flight, and the seabed layer on one real day of Danish AIS. No customer site yet: the first ones are pilots, and the pilot is free.
- Pointers, not verdicts
- A link means the same ship or the same hours appear in several places. Nothing here says who did anything. The police, the court or the insurer decides.
- No hardware
- It does not detect drones or watch the seabed. It works on what you already have: reports, AIS, your fault record, the ships' documents, the agent's ledger. Open data works too, such as Kystverket's and the Danish authority's AIS, adsb.lol's flight history, and your own receivers.
- Who builds it
- One person in Trondheim, the same one who answers your mail. No independent third-party review has been done yet.
Free pilot
Send one night that bothered you.
A set of sighting reports, a cable fault, a ship you were unsure about, or an incident you had to report. It runs on your own machine for a week at no cost, and you see every finding first.
Card payment through Stripe, then GitHub invites to the five repos and your signed licence files. Seabed incident files and Papers checks are billed monthly from your signed usage statement.