Skip to content

Add exact QK full-v5 recovery history admission - #325

Draft
ElmoPA wants to merge 1 commit into
codex/mot-imagenet-admission-20261026-v1from
codex/mot-qk-full-v5-interruption-service-20261027-v1
Draft

ElmoPA wants to merge 1 commit into
codex/mot-imagenet-admission-20261026-v1from
codex/mot-qk-full-v5-interruption-service-20261027-v1

Conversation

@ElmoPA

@ElmoPA ElmoPA commented Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator

The QK full-v5 recovery service can now distinguish four positively verified prelauncher attempts from the original scientific training parent. It reopens the exact retained evidence and a fresh complete claim/queue/step census; parent 412825 remains terminal UNKNOWN and is never represented by a fabricated native certificate.

The exact 314,227,000-parameter profile also checks all 558 conditional parameter counters and private weight/Adam state, including Q/K, SwiGLU, camera and language-fusion tensors. Frozen scientific source A, original checkpoint history, highest positive production checkpoint inspection, all-rank restoration, genuine producer/native observers and finalizer requirements are preserved. The service-owned historical readers never execute Python from evidence paths. Host/container CSV checks bind the actual gpu21 directory identity and preserve current scientific output.

Validation: 78 focused service-only metadata/adversarial/CPU tests pass on the exact published parent plus this service delta; the reviewed prospective service+ops composition passes 84 cases. An independent review verified source, historical-proof semantics, portable tests and archive bytes/modes. This commit does not supply a deployment, recovery request, actual failed-parent proof, checkpoint inspection or distributed GPU restoration. The ops binding is a subsequent independently reviewed change after this service's actual head/export are verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant