Repository navigation
Validate retained model recipes on source-pinned OSMO inputs - #156
Merged
Merged
Conversation
This was referenced Oct 2, 2026
Collaborator
This was referenced Oct 2, 2026
ElmoPA
marked this pull request as ready for review
October 2, 2026 19:05
This was referenced Oct 7, 2026
ElmoPA
changed the base branch from
codex/graph-integration-20260924/06-ci-gates
to
graphite-base/156
October 7, 2026 21:16
ElmoPA
force-pushed
the
codex/graph-integration-20260924/07-osmo-validation
branch
from
October 7, 2026 21:18
37cb8db to
a9df3c1
Compare
ElmoPA
added a commit
that referenced
this pull request
Oct 7, 2026
Retained recipes could silently accept the wrong data frame, and network-only preflight missed broken language schedulers. Add model-owned preprocessing requirements to the restored root recipes and enforce them before model construction and during checkpoint/inference binding. Shared runtime code compares declared data state without model-family dispatch. Execute the pinned EgoVerse source to preserve ten numerical data/normalization/metric references and both full language learning-rate schedules. Preserve camera-frame MSE at rotation wraparound, sparse-video upload FPS and tempo video lifecycle. Extend offline constructor checks through the actual model wrapper, training behavior, optimizer and scheduler; repair the missing UNITE baseline identity declaration without changing its objective. Validation: isolated snapshot `813e786f7e50e7dfae897e1bc55cc4130269858c`, **1,430 CPU tests passed**; locked dependencies and pinned Ruff pass; **254/254** YAML and component contexts pass. Fixture provenance and tolerances are documented in `docs/integration/FIXED_FIXTURE_PARITY.md`. This draft is layer 08, based on #156. Real-weight/data OSMO execution is blocked by HTTP 403 at the service/login endpoints; no integration GPU workflow has been submitted. Nested deployment contracts and assembled-destination validation remain open. No legacy-runtime cutover or deletion is authorized by these CPU results; DQC remains stopped.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Run the retained HPT and PI recipes through five real optimizer updates, validation, checkpoint saving, and the shared no-hardware inference loader on OSMO L40s. The matrix covers EVA, Aria, Mecka, Scale, retained HPT Yam, both cotraining paths, and a two-GPU HPT case. CPU input staging verifies complete disjoint episode manifests, public weights and tokenizer hashes before scheduling GPUs; outputs use conditional writes at new R2 prefixes.
PI exposes optional gradient checkpointing and sampler compilation controls while retaining existing defaults. This draft does not claim real-weight training, destination assembly, or legacy cutover has passed.
Validation: isolated 1,411 tests passed; 253/253 YAML compositions and constructor contexts passed; lock, Ruff check and format passed. The synthetic harness verifies five actual updates plus bound checkpoint reload. R2 probes confirmed both ordinary and multipart writes reject replacing an existing object. The full snapshot and log hashes are recorded in
docs/integration/evidence/osmo-harness-cpu-receipt.json.Stacked on #155. GPU receipts will be added after execution; DQC remains stopped.