Model acquisition and integrity
How a model reaches a machine running AI Stays Local, and what has to be true before the runtime will use it.
The verified acquisition foundation is implemented in the product layer. Guided desktop installation is the next integration phase and is not yet generally available.
AI Stays Local acquires approved model artifacts directly from their publishers or approved repositories. Large checkpoints are not proxied through TGSS LLC by default.
Model profiles use immutable revisions and verified manifests. A model is not exposed as ready until its required files pass integrity checks.
Interrupted downloads are designed to resume safely. A failed installation does not replace an existing verified model.
Repository credentials remain on the customer's system and are not transmitted to TGSS LLC.
The parts, and their state
| Part | What it does | State |
|---|---|---|
| Approved sources only | Artifacts come from the publisher or an approved repository. A provider-independent interface covers Hugging Face, plain HTTPS and a local directory. | Implemented in the product layer. |
| Immutable revisions | A profile names an exact revision, never a branch that can move. | Implemented in the product layer. |
| Publisher and licence on record | Every profile carries its publisher and its licence, and this website refuses to build a model record without both. | Implemented in the product layer. |
| Allowlisted manifests | Only the files a manifest lists are fetched. Path traversal, absolute paths, symbolic links, archives and executables are refused. | Implemented in the product layer. |
| Signed catalogue | The catalogue can be signed with Ed25519. An unknown signing key, a rolled-back catalogue and an unsupported schema are each rejected. | Implemented in the product layer. |
| Resumable downloads | An interrupted download is designed to resume from where it stopped rather than start again. | Implemented in the product layer. |
| Cryptographic verification | Every required file is checked against its recorded digest before the model is marked ready. | Implemented in the product layer. |
| Atomic promotion | A verified model is promoted into place in one step. A failed installation leaves the previous verified model where it was. | Implemented in the product layer. |
| Local credentials | A repository token is stored on the customer's machine, redacted from logs and output, and never sent to TGSS LLC. | Implemented in the product layer. |
| Safe removal | An installed model can be removed through the product, and installation state persists between sessions. | Implemented in the product layer. |
| Guided desktop installation | Hardware scan to model selection, licence acceptance and progress in a graphical application. This is the next integration phase. | Next integration phase. Not yet generally available. |
| Production signing keys | Distribution of the production catalogue signing key to customer installations. | Next integration phase. Not yet generally available. |
What you can check on this site
Every model record on the models page names its publisher, its licence, its source repository and the exact revision the evidence was taken on. A model with a missing publisher, licence or immutable revision fails this website's own build.
No model has a public download today. The command reference for acquisition ships with the build that testers receive, and is not reproduced here.