Architecture & functionality

how Germanium OS is built — and what it does, in detail

The platform — Germanium OS — is built like an operating system for a studio: a layer of surfaces on top of a shared API, on top of a data model, on top of two engines — with a layer of proof underneath it all. Each level can be replaced or grown without touching the others.

The SurfacesThe listening portal (web, mobile) · Cockpit (native macOS) · personal views with roles

The SpineOne operator API: the same commands for humans, apps and automation — CLI and tool APIs over the same core

The BackboneThe project model: material, decisions and versions as data, layered on a clean SSL 4000 base

The EnginesThe render engine (console structure, buses, pan law) + the DSP engine (analog hardware models, no DAW)

The ProofThe Flight Recorder: every run logged with hashes, snapshots and exact reproducibility

The architecture, piece by piece

The Backbone	Every project is data: pinned material (stems, reference, premix), decisions in named layers — console, mixer, plan, master, arrangement, genre — and a version history. The base is always a clean SSL 4000 configuration; everything else is a documented deviation from it. Nothing is overwritten: a new version is a new layer, never a replacement.
The Engines	Two engines with a clear division of labor. The render engine owns the structure: tracks, buses, the console's channel strips, pan law, sends and returns. The DSP engine runs the analog hardware models — preamps, EQ, compression, tape, rooms — directly in memory, with no DAW and no screen. The same chain renders exactly the same, every time.
The Spine	A single operator API over the whole core. Humans run it as commands, Cockpit runs it as an app, and the automation runs it as tools — but it is the same way in, with the same guards. No surface has private shortcuts past the rules.
The Knowledge Hub	The platform's accumulated learning as data: chains analyzed from tens of thousands of professional productions, a listening lexicon that translates words like “warm” or “present” into measurable moves, genre signatures and reference windows. The hub proposes — it never decides.
The Listening Analysis	Analysis tools that measure a mix and describe what the measurements show — masking, imbalances, deviations from the reference. The findings become proposals in the same queue as human requests. Proposals, never automatic interventions.
The Proof	The Flight Recorder logs every run: command, code version, inputs and deliveries with cryptographic hashes, snapshots of the project and console state, and a script that recreates the exact same result. See a real log →
The Health System	The platform verifies itself: a health check that measures every dependency (engines, models, storage, servers), and a test loop that regularly exercises the entire command surface — including a real render — separating true faults from empty results. Faults that can be fixed safely are fixed automatically; the rest are reported precisely.

The Backbone

Every project is data: pinned material (stems, reference, premix), decisions in named layers — console, mixer, plan, master, arrangement, genre — and a version history. The base is always a clean SSL 4000 configuration; everything else is a documented deviation from it. Nothing is overwritten: a new version is a new layer, never a replacement.

The Engines

Two engines with a clear division of labor. The render engine owns the structure: tracks, buses, the console's channel strips, pan law, sends and returns. The DSP engine runs the analog hardware models — preamps, EQ, compression, tape, rooms — directly in memory, with no DAW and no screen. The same chain renders exactly the same, every time.

The Spine

A single operator API over the whole core. Humans run it as commands, Cockpit runs it as an app, and the automation runs it as tools — but it is the same way in, with the same guards. No surface has private shortcuts past the rules.

The Knowledge Hub

The platform's accumulated learning as data: chains analyzed from tens of thousands of professional productions, a listening lexicon that translates words like “warm” or “present” into measurable moves, genre signatures and reference windows. The hub proposes — it never decides.

The Listening Analysis

Analysis tools that measure a mix and describe what the measurements show — masking, imbalances, deviations from the reference. The findings become proposals in the same queue as human requests. Proposals, never automatic interventions.

The Proof

The Flight Recorder logs every run: command, code version, inputs and deliveries with cryptographic hashes, snapshots of the project and console state, and a script that recreates the exact same result. See a real log →

The Health System

The platform verifies itself: a health check that measures every dependency (engines, models, storage, servers), and a test loop that regularly exercises the entire command surface — including a real render — separating true faults from empty results. Faults that can be fixed safely are fixed automatically; the rest are reported precisely.

The functionality, phase by phase

Source prep	Raw stems are reviewed gently: DC faults, subsonics and fake stereo are detected and reported. Report first — nothing changes without a decision, and level or tone are never touched.
Source diagnosis	Before the first decision, the material is measured: group hierarchy, internal balance, frequency collisions. After the mix, an audibility guard verifies nothing got buried. The diagnosis decides what needs doing — and what should be left alone.
The foundation mix	The SSL foundation is built: console pan law, phase alignment between sources, filter hygiene, collision-driven panning and, where needed, narrow band-limited carving between fighting parts. Genre profiles provide starting points; the ear's adjustments from the stems mixer are baked in as exact levels.
The character	On top of the clean foundation, character is added as separate decisions: tape, tubes, transformer iron, rooms. Every addition is motivated and logged. An intervention guard measures the total amount of processing so that many small moves never silently become one big one.
The master	A gate checks the premaster before heavy tools may touch it. Then loudness is built from dynamics — contrast before compression — against the reference's measured window: tone, punch, width, true peak. Every step gets a measurement receipt.
The review	Versions are published to the portal: A/B against each other and the reference, per-bus solo, the stems mixer, time-stamped comments, requests and approvals — all attributed through personal links with roles.
The seal	Six pillars must pass: source, dynamics, tone, engineering, proof — and the ear. The last one cannot be computed. Then the master is sealed with its hash and full history. See a sealed certification →

Source prep

Raw stems are reviewed gently: DC faults, subsonics and fake stereo are detected and reported. Report first — nothing changes without a decision, and level or tone are never touched.

Source diagnosis

Before the first decision, the material is measured: group hierarchy, internal balance, frequency collisions. After the mix, an audibility guard verifies nothing got buried. The diagnosis decides what needs doing — and what should be left alone.

The foundation mix

The SSL foundation is built: console pan law, phase alignment between sources, filter hygiene, collision-driven panning and, where needed, narrow band-limited carving between fighting parts. Genre profiles provide starting points; the ear's adjustments from the stems mixer are baked in as exact levels.

The character

On top of the clean foundation, character is added as separate decisions: tape, tubes, transformer iron, rooms. Every addition is motivated and logged. An intervention guard measures the total amount of processing so that many small moves never silently become one big one.

The master

A gate checks the premaster before heavy tools may touch it. Then loudness is built from dynamics — contrast before compression — against the reference's measured window: tone, punch, width, true peak. Every step gets a measurement receipt.

The review

Versions are published to the portal: A/B against each other and the reference, per-bus solo, the stems mixer, time-stamped comments, requests and approvals — all attributed through personal links with roles.

The seal

Six pillars must pass: source, dynamics, tone, engineering, proof — and the ear. The last one cannot be computed. Then the master is sealed with its hash and full history. See a sealed certification →

The design principle throughout: measure before deciding, the smallest possible intervention, humans as judges, and a trail of proof that makes every result explainable and reproducible. It is not an effects chain — it is a control room.