BUILD USE CASES
Memory, answers, models, and a record — the jobs the platform is for. The material stays on the appliance. The applications call something you host.
YOUR MATERIAL
A team asks a question of the material it already has — procedures, records, the last cycle of work. The answer comes back with the passage it used. Those documents do not leave the appliance in order to produce it.
An answer a person can check. A source that is still in the building.
ACROSS SESSIONS
Work that spans a shift should not start from nothing the next time someone opens it. Substrate keeps what has already been established — entities, decisions, prior conclusions — on the appliance. It is not synchronized off the box.
Continuity for the people who share the work. A memory the operator can export or purge.
YOUR DOMAIN
A general model does not speak the way your organization does. Adaptation tunes an open-weight model on your own material, inside the enclosure. The resulting weights belong to you and stay where they were produced.
A model that knows your domain. Training material that never had to leave.
THE RECORD
A system that cannot be reviewed cannot be trusted with the work that matters. Each prompt, retrieval, and response is written into a record on the appliance, for the people who already have the job of checking it.
A trail an auditor can read without reconstructing the session from memory.
MODELS YOU HOST
The models are yours, hosted on the appliance. Applications call one stable interface, so a later model — or a later appliance — does not force the application to be rewritten.
Models you chose. An application that outlives any single one of them.
SYSTEMS YOU ALREADY RUN
Useful work has to touch the systems where the work already lives. Those connections are declared, one by one, and every route is written down. There is no default path from the appliance to the public internet.
The systems you already secure, and no surprise path beside them.