choice stringclasses 6
values | picked stringclasses 6
values | why stringclasses 6
values |
|---|---|---|
Document retrieval model | BGE-M3 embedding model, 568M parameters, self-hosted at fp16 | The only model in the register; hybrid dense and sparse search over drawings, inspections and messages, with no token stream and no external provider in any interactive path |
Hardware classes | None purchased; existing enterprise virtual machines only | The requirements buy no equipment; about 1.1 GB of fp16 weights fit standard virtual machine memory |
Sizing rule | Weights occupy about 2.27 GB at float32, about 1.1 GB at fp16, about 0.6 GB at 8 bit | The fp16 figure is the sizing basis; no KV cache applies because an embedding model generates no token stream |
Sensing | No new sensing; up to five existing environmental sensor feeds with threshold alerting and historical export, plus a sourced photorealistic 3D mesh | The requirements integrate existing feeds; no camera, sensor or server is purchased |
Ground | Port-managed servers under the port's own change management, inside the continental United States boundary | The port's own security requirements set the boundary; every workload runs on infrastructure the port already operates |
Pattern | Adapter tier, one object model, read-only systems of record, Esri GeoEvent Server as the sole feed path | Every source enters through an adapter and the twin never writes back into a system of record |
Port digital twin ontology and model register for a landlord port authority
The object model and the model and equipment register from Port Twin: One Governed Digital Twin for Every Asset, Feed and Dollar, an open reference architecture by CodeNinja for the United States. Part of the Vertical-Driven Architectures series; every design in the series is also a row in the cumulative dataset https://huggingface.co/datasets/CodeNinjatools/vertical-driven-architectures.
- Read the paper: https://codeatoms.ai/port-digital-twin-us/
- DOI: https://doi.org/10.5281/zenodo.23126431
- Source files and PDF: https://github.com/muhammadumar89/codeninja-research
- Live view: https://huggingface.co/spaces/CodeNinjatools/port-digital-twin-us
Files
| File | What it holds |
|---|---|
objects.json |
13 typed objects (berth, navigation channel, subsurface utility layer, environmental sensor feed, parcel or facility, bathymetric survey surface, utility gap record, capital project, inspection record, vessel movement, truck movement, PCS message, engineering document), each with its anchor system, properties, status vocabulary and 13 typed links. Format hyper-ontology/1: designed with Praxis, implemented with Hyper Ontology. |
models.csv |
The model and equipment register from the paper's Table 4, with the reason for each choice. |
How to use it
import json
from huggingface_hub import hf_hub_download
p = hf_hub_download("CodeNinjatools/port-digital-twin-us-ontology", "objects.json", repo_type="dataset")
objects = json.load(open(p))["objects"]
print([o["label"] for o in objects])
Made with
Reasoned on Praxis, CodeNinja's platform for designing physical AI systems. The object model imports into Hyper Ontology, which turns it into a living system. Both in beta; access by request. Load it with the hyper-ontology loader.
Citation
CodeNinja Engineering Team and Muhammad Umar. 2026. Port Twin: One Governed Digital Twin for Every Asset, Feed and Dollar. CodeNinja. https://doi.org/10.5281/zenodo.23126431. CC BY 4.0.
One of the CodeNinja Atoms sovereign AI reference architectures: every published design with its sector, country, compute and three-year cost.
- Downloads last month
- 117