OPSD model registry

This repository is the canonical public index for OPSD model artifacts owned by LSW142857. Large weights remain in immutable per-checkpoint model repositories; this registry gives them one stable, unambiguous hierarchy.

Layout

OPSD/
├── strong/
│   ├── first_user/iterations/
│   └── trailing_user/iterations/
├── medium/
│   ├── first_user/iterations/
│   └── trailing_user/iterations/
└── weak/
    ├── first_user/iterations/
    └── trailing_user/iterations/

Each available iter_XXXXXXX directory contains an artifact.json pointer. The number is the zero-indexed training iteration, so iter_0000031 means 32 completed optimizer updates. An arm-level README records whether an experiment is available, still training, private, or not yet run.

Available artifacts

PI	Teacher prompt	Iteration	Updates	Format	Direct load	Artifact
Medium	trailing_user	8	9	merged full model	yes	open
Medium	trailing_user	16	17	merged full model	yes	open
Medium	trailing_user	31	32	merged full model	yes	open
Weak	trailing_user	1	2	unmerged LoRA + full-MTP bundle	no	open
Weak	trailing_user	2	3	unmerged LoRA + full-MTP bundle	no	open
Weak	trailing_user	3	4	unmerged LoRA + full-MTP bundle	no	open
Weak	trailing_user	4	5	unmerged LoRA + full-MTP bundle	no	open

Strong trailing_user is currently training. Its validated model repositories will be added without changing this hierarchy.

Machine-readable inventory: registry.json. Artifact schema: schema/artifact.schema.json.

Naming contract

• Use only strong, medium, or weak for PI level.
• Use the exact code-level prompt modes first_user and trailing_user.
• Use zero-indexed, seven-digit directories: iter_0000008, not checkpoint8.
• Record the immutable Hugging Face commit in every artifact.json.
• Mark whether the artifact is directly loadable. Never describe an OPSD trainables bundle as a merged model.
• Do not place optimizer state, datasets, rollout transcripts, logs, or tokens in this public registry.

Legacy repositories

Older public repositories whose prompt mode or artifact contract is not unambiguously encoded are listed in legacy_unclassified/README.md. They are not silently assigned to an arm.