YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
CLRR checkpoints
Canonical checkpoint storage
Public project checkpoint repository. Open a method to see its seeds directly:
checkpoints/<dataset>/<backbone>/<method>/seed-<n>/best.zip
When the same method/seed has multiple distinct configurations, each archive is stored inside a configuration folder below that seed. Configuration names describe the actual method or protocol; dates belong in metadata. Never overwrite different weights. Strong LoRA A/B and LSR lambda comparators have explicit method labels in the index.
The verified reorganization preserved all 90 final archives and all existing score-bearing file contents. All 16 previously unknown archive seeds were verified as 42 from archived training arguments. Actual ES4/ES10 settings remain unchanged. Recovering a seed does not establish complete training provenance.
- Current checkpoint table
- CSV index
- Storage guide
- Current old-to-new mapping
- Seed evidence
- Public independent verification
- Checkpoints
Provenance
Original recipes, cohorts and receipts remain available beside each checkpoint and in the registry. New runs require complete run_metadata.json. The index primary flag recommends the corrected implementation rather than selecting on test scores. Layout receipts record migration provenance, not new training results.
Earlier path mappings and migration receipts remain historical snapshots: resolve their destinations through the current seed layout mapping. Metadata-only development reports are under registry/reports/development. Only selected final archives remain in the current tree; this does not claim deletion of historical Git blobs or permanent storage reclamation.