Every level OpenCAGE could open used to be one that shipped with the game. File → Create Level, the first item on the script editor's File menu (shown below), makes a new one from scratch: it builds the level folder, seeds it with the scripts and data every level needs, optionally brings composites (and everything they use) across from other levels, registers the level with the game, and opens it in the editor.

A new level is a real level as far as the game is concerned. It lives in DATA/ENV/<NAME> beside the shipped ones, it appears in the Launch Game level list and the Backup Manager, and it goes through Save and Build like any other.
Open File → Create Level. The dialog, shown below, has three parts:

The Create Level dialog with a name entered and a pick from BSP_TORRENS queued for import: one composite ticked, and the seven it instances counted with it.
BSP_TORRENS, from PRODUCTION/BSP_TORRENS), a name with a DATA/ENV/<NAME> folder left over from a failed create, or one that already has backups.The picker is the same Import from Level dialog described under Composite Porting, minus the Overwrite composites already here option — a level that doesn't exist yet has no composites to overwrite — and with OK in place of Import, since nothing is ported until the level is created. Overwrite existing assets is still offered, for when picks from several levels bring same-named models or textures. Open composite after import is shown too, but has no effect here: the new level is loaded as soon as it's created, and opens on its root composite. Ticking it only sets the default for the Import Composites windows. Composites you've saved as .ocp packages can be brought in once the level exists — even before it's opened.

The picker with BSP_TORRENS chosen and Android_Impact_Generators ticked. The line beside OK counts the seven composites it instances as well — they're ticked and greyed in the tree (out of view here), since they come along regardless.
Tick Make playable test room to start with a level you can play straight away. Two composites join the import list, under their source levels and marked (for the test room), so you can see what's coming in:

DisplayModel:RIPLEY_FP from FRONTEND — the player's first-person body.Archetypes\Script\Mission\SpawnPositionSelect from SCI_HUB — the player and its spawn logic, with the three composites it places. FRONTEND doesn't have it, so it comes from SCI_HUB.Untick the option and they leave the list again, unless you'd added them yourself, in which case they stay. If you untick either of them in the picker, the option turns off, since the room can't be made without them.
Once the level is created and opens, OpenCAGE builds the room in its root composite:
Room_Floor, Room_Ceiling, Room_Wall_North and so on), half a metre thick, in the grey grid material, with a line every metre that meets at the corners. The floor and walls have solid collision you can walk on, and they sound like a metal floor underfoot. The ceiling's collision is ballistic only: shots and the torch stop at it, but nothing walks on it, so the navmesh stays off the roof. They're ordinary brushes, so you can resize them with the viewport handles or retexture them in the Brush Editor.Room size is the space inside the walls: width (X) × length (Z) × height. It's 16 × 16 × 5 m by default, and can be 2 to 128 m across and 2.5 to 32 m high. The whole room is one undo step, Build test room. The level is then saved and built, ready for Launch Game.
The level is built from FRONTEND, the menu level nothing else edits. A handful of a level's files can't be generated from nothing — sound lookups, galaxy data, soundbank tables, material mappings and the collision and physics scaffolds — and those are copied from it (its list of behaviour trees is copied too, then regenerated from the character configs when the level is saved), along with the engine's own materials that head every level's material table (the fallback and post-processing materials, the fog, water and light materials and so on — without them the game draws its HUD over a black frame), the block of required models the engine builds lights, particles and fog from, and the twelve movers that draw them. Everything else starts empty: no geometry, navmesh, lighting or sound network of your own until you add models and build.
On the script side you get:
The level is also written into the game's package list straight away, so the game can find it without waiting for the next launch. It gets its own block in DATA/LEVEL_TEXT_DATABASES.XML too, naming the standard subtitle and bark databases plus the shared ones the levels you imported from load, so subtitles, barks and imported strings show as text rather than string ids. If that block can't be written, the Complete message warns you: open Level Text DBs and use Add Standard Set on the new level.
.ocp package).