Publish curated ITWorx-ModelForge source from 990401737f96c8d46a9f7b0d84994516cadcb6a0

This commit is contained in:
Public Source Publisher committed 2026-09-30 09:23:17 +00:00
1 parent 7082ab955a
commit 848f0d8f8a
434 files changed
+67298 -4315

No files matched your search

+26 -9
View File
@@ -1,11 +1,26 @@
# ITWorx ModelForge
<p align="center"><strong>One stable capability interface for models running on your own hardware.</strong></p>
<p align="center"><a href="#console-tour">Console tour</a> · <a href="#first-useful-workflow">Workflow</a> · <a href="#what-you-get">Capabilities</a> · <a href="#quick-start">Quick start</a> · <a href="#architecture">Architecture</a></p>
ModelForge is a self-hosted control plane for running AI models on hardware you control. Applications
ask for a stable capability such as `rag.embedding@1`; ModelForge selects an approved model revision,
places it on an eligible compute node, and retains the evidence needed to explain and roll back that
decision.
Current release: **1.2.1**
## Console tour
![ModelForge operator console overview with synthetic model records](docs/screenshots/console-demo.png)
*Overview: the operator's starting point for model and infrastructure status.*
![ModelForge model library with two synthetic model records](docs/screenshots/models-demo.png)
*Model library: inspect registered revisions and their details before planning a deployment.*
Both images show the actual web console with synthetic API responses. No real operator, model, project or infrastructure data appear in them, and they do not imply a validated deployment. The current console uses Dutch interface labels.
The current source line is **1.3.0-rc.1**. A source version does not by itself identify a qualified release or a running deployment; use the exact release evidence and deployment revision when operating an instance. The [publication guide](docs/PUBLICATION.md) explains the release boundary.
## What you get
@@ -69,13 +84,15 @@ The caller does not need to know the model name, artifact path, runtime or GPU n
## Architecture
```text
Applications -> Capability Gateway -> Scheduler -> typed runtime workers
| ^
v |
Control Plane <--- outbound node agents
|
PostgreSQL + Redis + verified artifacts
```mermaid
flowchart LR
Apps[Applications] --> Gateway[Capability gateway]
Gateway --> Scheduler[Placement scheduler]
Scheduler --> Workers[Typed runtime workers]
Agents[Outbound node agents] --> Control[Control plane]
Control --> Scheduler
Control --> DB[(PostgreSQL and Redis)]
Control --> Artifacts[Verified model artifacts]
```
Important boundaries:
@@ -103,7 +120,7 @@ detail.
| Operate and recover it | [Operations](docs/OPERATIONS.md) · [Troubleshooting](docs/TROUBLESHOOTING.md) |
| Review security | [Security](docs/SECURITY.md) · [Threat model](docs/security/THREAT_MODEL.md) |
| Understand compatibility | [Compatibility](docs/COMPATIBILITY.md) |
| See release changes | [Changelog](CHANGELOG.md) · [1.2.1 release notes](docs/RELEASE_NOTES_v1.2.1.md) |
| See release changes | [Changelog](CHANGELOG.md) · [1.2.2 release notes](docs/RELEASE_NOTES_v1.2.2.md) |
## Repository layout