The platform speaks one language, to one place: the Interchange. The Collector is the way in. It takes any form an outside system sends (an event, a reading, a PDF, a spreadsheet, a video), keeps the original, and names what it is with MissionSight's event types. The Interchange then sends each event down the paths its rules choose.
will also need our own ingestion intermediary to get ALL types of data: some weird system might send a PDF, some might send an event."
State, 7 November 2026: first slice, local only. Everything runs on one machine. The Jira desk, the i3 CMMS and the alert channels are stubs. Nothing at SFB is connected, and no outside service is called. This repo has no remote.
The shape
Outside systems Collector (POST /collect) Interchange Products
BHS PLCs, KONE, BMS, i3, --> store the original (sha256) --> rule path selection --> the twin's asset JSON,
drones, phones, cameras, verify the signature log, history, actions the Exploders,
"a weird system that classify by data rules alert (role, route, escalation) Airfieldpath, Causeway
sends a PDF" check against the catalogue ticket (Jira adapter, stub)
| de-duplicate, order work order (i3 adapter, stub,
| bind the sensor to its target after a person confirms)
local relay unit trap: triggers name events analysis (predictions)
(read, buffer, sign, forward) |
MissionSight: the event-type and sensor-type catalogue
See the Fleet World (stellarview/walkthroughs/fleet-3d) for the same path on the real infrastructure: the fleet's own ingestion Lambda and its S3 lake, and MissionSight's Kinesis stream. docs/architecture.md maps each local part to its AWS design.
Run it
npm install
npm test # 77 tests
npm run demo # BHS, KONE, a policy PDF, an interval trend and the Jira round trip
npm start # the Collector on 127.0.0.1:4720
npm run demo prints each stage of five runs and writes one evidence line per stage to evidence/: