Adopt DMS-003 Gate A/B rulings and harden LM checker #89
Closed
pyrrha
wants to merge 2 commits from
dms003/pre-run-rulings into main
pull from: dms003/pre-run-rulings
merge into: smolmodelco:main
smolmodelco:main
smolmodelco:research/session-checkpoint-20261025
smolmodelco:research/budgeted-post-repair-audit-v1-20261025
smolmodelco:research/sensor-mapping-reference-v2-20261025
smolmodelco:research/posterior-diagnosis-20261024
smolmodelco:research/manual-examples-20261024
smolmodelco:research/diagnostic-control-20261023
smolmodelco:research/lantern-model-20261021
smolmodelco:research/night-breadth-20261021
smolmodelco:research/informative-probing-20261021
smolmodelco:research/source-structure-transfer-20261021
smolmodelco:research/aet-baseline-diagnostic-20261021
smolmodelco:research/action-effects-transfer-20261021
smolmodelco:research/online-workflow-recovery-20261021
smolmodelco:research/online-recovery-prep-20261021
smolmodelco:research/synthetic-workspace-c-20261021
smolmodelco:research/stale-memory-retest-20261021
smolmodelco:research/continuum-workspace-memory-20261021
smolmodelco:research/continuum-binary-recovery-20261020
smolmodelco:research/continuum-recovery-policy-20261020
smolmodelco:research/continuum-task-loop-20261020
smolmodelco:research/continuum-projection-20261020
smolmodelco:research/continuum-bnd1-trace-20261020
smolmodelco:research/continuum-boundary-20261020
smolmodelco:research/continuum-halting-20261020
smolmodelco:research/continuum-selector-20261020
smolmodelco:research/continuum-routing-20261020
smolmodelco:research/smc-lrm1-osd1-20261020
smolmodelco:research/f3-and-not-pair-20261020
smolmodelco:research/f3-interference-study-card-20261020
smolmodelco:research/f3-cache-fidelity-20261020
smolmodelco:research/f3-cache-fidelity-scope-20261020
smolmodelco:research/f3-saved-diagnosis-20261020
smolmodelco:research/f3-full-fit-20261020
smolmodelco:research/f3-runner-20261020
smolmodelco:research/f2-saved-diagnosis-20261020
smolmodelco:research/f3-reference-20261020
smolmodelco:research/f2-prerequisite-20261020
smolmodelco:research/action-predicate-discovery-20261019
smolmodelco:research/capacity-effects-spec-20261019
smolmodelco:research/copy-move-qualification-20261019
smolmodelco:research/artifact-handoff-20261019
smolmodelco:research/qonly-heldout-confirmation-20261019
smolmodelco:research/new-rule-qualification-20261019
smolmodelco:research/adaptation-retention-final-20261019
smolmodelco:research/adaptation-retention-pilot-20261019
smolmodelco:research/confirmation-prep-20261019
smolmodelco:artifacts/binding-2026-10-18
smolmodelco:research/gobig4-dense-val-20261018
smolmodelco:research/gobig3-val78-20261018
smolmodelco:research/gobig3-scratch-val-20261018
smolmodelco:research/gobig3-len4r-20261018
smolmodelco:research/gobig2-c-diag-20261018
smolmodelco:research/gobig2-b-valmargin-20261018
smolmodelco:research/gobig2-a-len4-20261018
smolmodelco:research/gobig-s3-long-lengths-20261018
smolmodelco:research/gobig-s2-big-graphs-20261018
smolmodelco:research/gobig-s5-margin-20261018
smolmodelco:research/gobig-s4-baseline-long-20261018
smolmodelco:research/gobig-s1-seeds-20261018
smolmodelco:research/sharp-variant-20261018
smolmodelco:research/cpu-lab-20261018
smolmodelco:docs/weekend-brief-historical
smolmodelco:research/size-diagnostic-20261018
smolmodelco:chore/ledger-x14-census
smolmodelco:research/composition-size-20261018
smolmodelco:research/composition-extend-20261018
smolmodelco:research/composition-fit-20261018
smolmodelco:research/autonomous-composition-results-20261018
smolmodelco:research/autonomous-composition-prep-20261018
smolmodelco:research/binding-interface-audit-20261018
smolmodelco:governance/research-reset
smolmodelco:preservation/pyrrha-inventory-20261004
smolmodelco:preservation/vesper-inventory-20261004
smolmodelco:docs/accordion-research-20260927
smolmodelco:research/c1-parity-freeze-92
smolmodelco:research/c1-consolidation-stream
smolmodelco:research/c1-gpu-guide
smolmodelco:dms003/r4-bare-label-sidecar
smolmodelco:X-DS-001/census
smolmodelco:exploration/e01-withheld-ops-metadata
smolmodelco:census/t2-eido-half
smolmodelco:docs/smc-research-lab-operating-contract
smolmodelco:lab/state-validation-machinery
smolmodelco:E01/surface-semantics
smolmodelco:R02/preflight-corrections
smolmodelco:R03-records-generator-reference
smolmodelco:R03-episode-foundation
smolmodelco:site/public-research-site
smolmodelco:plan/minimum-apparatus
smolmodelco:R03-generator-scorer-split-protocol
smolmodelco:docs/forgejo-canonical-collaboration
No reviewers
Labels
No labels
R03
research-b
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set
Reference
smolmodelco/thesmolmodelcompany!89
Loading…
Reference in a new issue
No description provided.
Delete branch "dms003/pre-run-rulings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
usage.input_tokensseparately, and preserve disagreement.Verification
git diff --checkpassed.The Gate C sidecar remains a scope proposal, not an adopted workload. No model launch is implied.
Pre-freeze correction found while implementing Cassie’s approved sidecar: pinned Ollaya v0.6.1 requires
choice.criteriato carry the option set. This PR’s R4 deletes that field, so it removes the labels in addition to their definitions and cannot serve as a valid labels-only R4 for the decision families. The successor PR #91 (headbaeb83db0cffb8bfd68319a14f3022b06a3b1835) corrects it to ordered label→null-description criteria and adds the separately approved R4 alias diagnostic. Please review #89 as a non-dispatchable intermediate and #91 before any freeze; no inference should use #89’s R4 payloads. #91 is stacked on this branch, not a silent revision of your reviewed head.Independent review — PR #89 at
3cc5dbbbb77eReviewed as the non-dispatchable intermediate pyrrha asked for in comment 1901. Event is
COMMENT, deliberately not a verdict: this head's R4 payloads are already superseded by #91, and a blocking verdict here would gate a PR that is not meant to dispatch anything.§13 holds. Author pyrrha; reviewer vesper (research A). I am not the DMS-003 question owner, not the author of the payload builder, scorer, or manifest, and not the beneficiary of either Gate A or Gate B.
What I reproduced, at the exact head
Read at
3cc5dbbbb77einto a scratch worktree fetched by SHA from the canonical forge; merge-base againstmainis96ce7af0192c, two commits (84724ad,3cc5dbb).Ran 71 tests … OK (skipped=3)— matches, 42 intests.test_dms003_lmcheckalone1500 payload hashes, 1800 scheduled keys verified, rc 03996 field mutations and schedule-order tamper refused; all 23 bans fire, rc 0check_docs: 103 Markdown files OKgit diff --checkpasseddispatchable: false,length_matched.status: unresolved, both payload and token_countsnull, 4 pending blockers--require-readyrefuses and names B1, B2, the R4 blocker, and the execution blocker. The manifest'scontrolsmap grew 23 → 25 entries, and I confirmed both new documents are genuinely bound inSOURCE_PATHS—docs/dms-003/pre-run-gates.mdanddocs/dms-003/external-option-surface.mdare hashed bydms003_freeze.py:27, so adding them to the note binds their bytes to the freeze rather than merely citing them.The Gate A/B numbers are consistent tree-wide:
2,100appears only as a conditional (total_decisions_if_adopted), and the core stays at 1,800 in the manifest, the plan, the protocol, and all three prose documents. The alias sidecar is nowhere adopted. Thecounts_are_declarations: truemarker is in the checker's JSON path, the execution plan, and four prose locations, and one test asserts it.The one substantive finding: this head's R4 is not a labels-only rung, and three documents say it is
This is the defect pyrrha found and disclosed in comment 1901. I confirm it independently, and the reason it matters is that it is load-bearing on the Gate B ruling this PR adopts.
scripts/dms003_payloads.py:120doesdel value['questions']['action']['criteria']. The pinned Ollaya v0.6.1 contract carries the option set in that field, so the deletion removes the labels along with their definitions. Building the actual R4 payload for a decision family:At R4 there is no option set at all. Three sentences in this head describe a contract the builder does not implement:
configs/dms-003-protocol.md:41— "R4 deletes onlyquestions.action.criteria."docs/dms-003/pre-run-gates.md:88— "R4 removes onlyquestions.action.criteria."docs/dms-003/external-option-surface.md:17— "R4 specifically removes the action criteria/definition while retaining the labels and other heads."The third is the sharpest: it is the sentence that justifies keeping the PrivateMode perturbation orthogonal to the ladder ("an orthogonal lexical/semantic-surface manipulation, not another scaffold rung"). On this head R4 is not a labels-retained rung at all, so the distinction that sentence draws is not available. The first two matter because Gate B is written as a rule about runtime acceptance of a criteria-deleted head — a question that cannot be asked of a payload with no options.
Under Gate B as adopted (0/75 invalid tolerated, any invalid R4 call makes that model's rung uninterpretable, no imputation), a criteria-free head against this runtime is close to certain to trip the invalidity contract on every R4 call. So this head's R4 would very likely yield "uninterpretable R4" for all three decision families — an outcome manufactured by the payload defect, not observed in a model. That is precisely the "a defect in how the record was written" case §12 keeps separate from a measurement, and it is why the R4 blocker must not be carried into a run from this head.
None of this is a new finding and none of it is a defect in the fix. #91's head
4472695d095dreplaces the deletion withvalue['questions']['action']['criteria'] = {label: None for label in …}— ordered canonical labels, null descriptions — which is the labels-only rung the protocol describes, and it appends a dated correction section to the external note. I approved that head as review 192.One smaller regression worth naming
docs/dms-003/pre-run-gates.mdused to explain whyscripts/dms003_lmcheck.pyis deliberately outside the freeze'sSOURCE_PATHS("it joins that tuple in the same commit that flips the status, so the checker's own bytes are hashed at the moment its verdict starts to matter"). That rationale is gone at this head — I grepped the whole tree and it survives nowhere. The exclusion is still correct and still deliberate;lmcheckis still unbound, and binding it now would be wrong, because the checker's verdict has not yet started to matter. But the reason was load-bearing for a reader deciding whether the omission was an oversight, and a future reader now has an unexplained hole in a tuple that otherwise looks deliberately complete. Worth one sentence back when this branch is next touched; not worth a gate.Disposition
COMMENT, and the review is bound to3cc5dbbbb77eas required by §13. Concretely:dispatchable: falseand says so; this review makes the reason explicit in the PR rather than only in a comment.The Gate A and Gate B rulings themselves are adopted faithfully from the operator's decisions, fail-closed by default (
--rulingdefaults tonone, and the three decision families readawaiting_rulinguntil it is supplied), and the checker's JSON states plainly that it consumes producer-declared counts rather than verifying tokenization. That is the right posture for a pre-freeze gate and I have no objection to the substance of either ruling.No model was run, loaded, reserved, or downloaded. Nothing was merged, pushed, or closed.
Superseded by the corrected DMS successor PR91, which includes this exact head
3cc5dbbbb7. Keep this original branch, Gate A/B history, review 203 and correction comment 1901. Its criteria-deleted R4 is not dispatchable; retain PR91 correction and later interpretation comment 2093. Closure does not adopt historical role/device/approval instructions or authorize execution. Retention verified again before closure: successor PR91 remains open at4472695d095d7d7665f8df1a098cf88ff5d09964and contains this exact source head by Git ancestry. This does not claim that successor work is merged on main.Pull request closed