Registry · Models
Release records and source-attributed upstream snapshots.
LeanLogix owns local release evidence. External observations are legacy, dated snapshots whose upstream facts remain canonical in MOEModels; their signatures prove receipt integrity, not release authorization. A row or channel label does not prove hosting, endpoint reachability, loaded weights, or inference.
The registry
Local release records, separated from upstream snapshots
This is not a universal model registry or hosting inventory. MOEModels owns upstream discovery and public facts. LeanLogix retains source-attributed snapshots only for compatibility and local audit; serving still requires a separate authorized release, configured endpoint, and request-time gate.
Ecosystem models · 8
LockedIn Labs ecosystem models
The models built by the LockedIn Labs ecosystem and LeanLogix’s own platform — SprintLoop, ControlFrame, HealthNext, and the routing/infra layer. These are the builds the platform was first proven on.
External records · 5
External and partner evidence
External, partner, and customer model records that LeanLogix does not own. Inclusion preserves evidence and review state; it does not claim the platform hosts or serves the model.
A production channel is a registry fact, not proof that an endpoint is configured, reachable, or serving the recorded weights. Ecosystem and external records use the same evidence contract. The passport column reads passport-ready until explicit signed-passport evidence is present. A stored artifact and hash read artifact sealed — useful integrity evidence, but not a signed passport, certification, hosting claim, or Verify action. Early builds with no eval or evidence are shown exactly as they stand; the registry doesn't round drafts up to releases.
Observed · public-fact snapshots we do not host
A tamper-evident provenance index for widely used models
MOEModels owns upstream discovery and canonical public model facts. These legacy observation receipts are tamper-evident, dated snapshots of the source LeanLogix read for compatibility and local audit. Signature validity proves snapshot integrity under its signer; it does not authorize a release, certify the source, or create a benchmark or quality claim.
All 10 observation receipts had their embedded-key signatures and observation schemas re-checked server-side as you loaded this page. These are observed, not hosted, evaluated, released, or served. A valid embedded-key signature proves snapshot integrity; LeanLogix authority is trusted only when the signer matches an independently configured pin. Open any row to inspect both results, or paste the receipt into the public verifier at lockedinlabs.ai/verify. Embedded key a97122c37f…97fac1e1.
Repository sandbox
Illustrative dataset records
These static seed rows demonstrate the intended dataset contract. They are not a live registry read, do not establish that a scan ran in production, and are kept separate from release authority.
The governed library
This catalog is the public read of the registry
The operator workspace exposes sandbox examples separately from live version history, evaluation records, release state, and authenticated passport evidence. A seed or channel label never establishes serving eligibility.
Inspect the registry behind these evidence records
13 model records on the public catalog today — 8 ecosystem records and 5 external records. Step into the Studio to inspect evidence and release state; use the governed gateway to determine actual serving eligibility.