Repository navigation
Verify legacy trunk initialization and capability dispositions - #159
Merged
Merged
Conversation
This was referenced Sep 28, 2026
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/09-deployment-contracts
to
graphite-base/159
October 7, 2026 21:22
ElmoPA
force-pushed
the
codex/graph-integration-20260924/10-trunk-parity
branch
from
October 7, 2026 21:24
eda6f8d to
afbf006
Compare
ElmoPA
added a commit
that referenced
this pull request
Oct 7, 2026
…#199) Replace five identical model copies with thin aliases and express the two Qwen 180M variants through explicit flow-head overrides. Existing callers retain their resolved graph behavior. This extends the existing graph-contract stack ending at #159. Review the config deduplication and compatibility layer independently of the ARC and weighted-training integration above it. The branch points at the original consolidation commit `67357575`; no commit or code was rewritten to create this stack. Validation: the committed deduplication evidence records unchanged composition for all 254 contexts in this layer. Stack construction verified exact commit identity and parent ancestry. The complete assembled CPU validation and source dispositions are attached to #198; those results apply to the assembled code commit, not separately to every intermediate layer. Keep this PR in draft pending the assembled real-weight/data OSMO gate and applicable fresh CI/review. Stack order: #150–#159 → #199 → #200 → #201 → #198.
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.
Preserve the legacy HPT trunk initialization capability with an executable source reference. Generate CPU parameters using the original pinned
HPTModelfactory and loader, then load its exacttrunk.namespace through generic graph initialization. Compare masked outputs, both block outputs, loss, input gradients and all 28 parameter gradients. The local and immutable-Hub transport paths use the same strict tensor/hash validation; only Hub transport is substituted in the fixture test.Complete dispositions for all 83 legacy-only paths: 56 ported, 25 replaced and two without in-repository consumers at the audited source. Each entry has an owner and evidence, with GPU and assembled-destination gates still explicit. No legacy files are deleted by this layer. Fresh read-only destination preflight records unresolved merge paths without modifying either main branch.
Validation: isolated snapshot
8db359eabdfd2b1cd903f49cd8e66da3df6e8a03, 1,454 CPU tests passed; lock and pinned Ruff pass; recursive tests cover 254/254 YAML/component contexts. Fixture tensors are generated CPU data, not pretrained weights or historical ARC checkpoints.This draft is layer 10, based on #158. OSMO still returns HTTP 403 at the service/login endpoints; no integration GPU workflow has been submitted. Destination assembly and cutover remain incomplete, and DQC stays stopped.