The one crossing, and the five things it forbids
foreign bytes · the Nautilus edge · Nautilus profiles · what is forbidden after them
Mission foundation / System overview
One import boundary for outside assets
Nautilus decodes source formats such as GLB, PNG, JPEG, and FBX into MerTek mesh, texture, rig, animation, and point-data profiles. Render code reads only those profiles.
Inside the system
Each plate preserves the internal layout, paths, boundaries, and highlighted decisions. Use the short label first, then follow the lines through the system.
foreign bytes · the Nautilus edge · Nautilus profiles · what is forbidden after them
five containers · fixed header · declared streams · what each decode refuses
front end · Trident verb · the one part record · the untrusted sidecar
path → import → encode → reopen → pose and draw · plus the persistence leg
foreign names · the mapping edge · Nautilus names · the two halves of one gate
Key parts
These are the main boundaries, inputs, outputs, and failure rules. The examples show a specific use of each part.
Outside files are decoded and checked in one place. Downstream systems receive a known MerTek asset, not the original vendor format.
A vehicle model from a supplier can enter a training scene without adding that supplier format to the renderer.
Meshes, textures, rigs, animation, and point data have owned platform shapes. Each importer maps its source into those shapes.
Drone imagery and a ground model can be prepared for the same visualization pipeline.
External field names end at import. MerTek uses clear internal terms so one supplier does not define the program data model.
Different sensor vendors can map their material or image terms into one reviewed mission vocabulary.
Uses
Pilot questions
Which source formats suppliers deliver
What checks are required before an asset is accepted
Which asset terms need a shared program definition