# ModelForge v1.3.0-rc.1 — qualification candidate

`v1.3.0-rc.1` identifies the release-candidate source and artifact set. This file belongs in its
archive; the annotated tag, Gitea prerelease, exact image identities and retained qualification
evidence must be verified from the published release record. A prerelease does not authorize a
production deployment.

The current source targets Alembic schema `20260924_0039` and Node Agent protocol 1. The final
candidate must contain four first-class images: API, Web, Node Agent and Runtime Worker. P15A must
bind their exact OCI labels, content-addressable RootFS layer sets, SBOM, provenance, source/archive
hashes and exact-image security reports into one retained transport bundle. P12–P14 must load that
bundle without rebuilding it.

The user-visible ModelForge changes are the already merged project-first model management,
onboarding, model library, immutable dimension pinning and guarded replacement/rollback flows. The
candidate reports the `rc` release channel so its API health and system metadata cannot be confused
with the stable production line.

## Known limitations

- The `v1.3.0-rc.1` tag and Gitea prerelease are permitted only after every mandatory readiness
  row is verified against the exact artifact set; the version string does not prove that gate.
- The release record must retain proof of the isolated RC stack, real ExampleRAG consumer path,
  project replacement/rollback, PostgreSQL 0039 recovery, fault journeys and 60-minute soak.
- A real GPU inference gate requires an available RTX 4080 SUPER window; unmanaged workloads are
  never stopped or changed by this candidate process.
- Observed production remains v1.2.3/schema-0032 unless a separate stable promotion procedure
  explicitly authorizes a change.