Platform · Model Studio
One control plane for the entire model lifecycle.
Review completed source evidence, apply local evaluation and policy, require an independent approver, issue a signed passport, and inspect the fail-closed gateway. Training and quantization remain documented but unavailable execution lanes.
The lifecycle
Evidence stages, one release authority
LeanLogix begins with completed source evidence. Unsupported execution lanes stay labeled as reference material; evaluation, independent approval, passports, and request-time enforcement form the implemented release path.
System of record
Every model is a registry entry
A model is not a file on someone's laptop. In the studio it is a typed record with the lineage that makes it auditable — what it was trained from, how, on what data, how it scored, where it sits, who approved it, and a signature you can re-check later.
The same record drives the studio UI, the release gate, and the procurement evidence pack. There is no separate spreadsheet to keep in sync — the registry is the source of truth.
Promotion from candidate → serving is a server-derived state change gated by completed-job provenance, evaluation, and a reviewer who is not the trainer. A registry channel alone never proves endpoint availability.
Example passport · SprintLoop-7B v6
Why a control plane
The studio replaces the gap between a good run and a defensible release
Most teams can produce a model. Far fewer can prove, months later, exactly what it was and why it was allowed to ship. The studio closes that gap by construction.
Governed data in, no customer rows
Datasets are registered, PII-scanned, and marked for customer-data status before a run can use them. The SprintLoop corpus is 2,800 verified examples with zero customer rows.
Hard probes, not vibes
Each catalog version carries behavioral, safety, and leakage evidence. A score remains evidence; it does not prove the configured endpoint loaded those weights or served a request.
Separation of duties
The approver is never the trainer. A release that has not cleared a reviewer who is independent of the build cannot enter the serving channel.
A passport that seals into proof
On release, a passport is sealed with an Ed25519 signature over its lineage and its stored artifact hash — so a regulator or customer can re-check it without trusting your dashboard. Until that artifact is stored, the registry shows the build as passport-ready, not signed.
Technique catalog
The methods the studio exposes
This is an evidence and design-reference catalog, not an execution menu. Evidence marks historically recorded methods, Reference describes evaluated approaches, and Roadmap identifies future work. The capability manifest controls what operators can actually run.
Fine-tune
Slim
Distill
Align
Prune
Merge
Continual
Inspect the release workflow on recorded evidence
Open the operator workspace to review completed-job evidence, evaluations, approval state, passports, and fail-closed routing. Registry labels are not presented as proof of live serving.