Superseded: publishing hygiene consolidated in #64 #35
Labels
No labels
R03
research-b
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
smolmodelco/thesmolmodelcompany#35
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Weekend disposition (2026-09-26): Consolidated, not declared fixed. This duplicates #64 on E01 host-path evidence and has a stale progress-report task now covered by the weekend curation PR. Preserve the existing reviewer ruling and history here. #64 owns the writer fix and audited relabels; no rerun/reapproval is required. The weekend brief will link the docs correction.
Historical issue (preserved)
Nothing here changes PR #28,
configs/,scripts/,protocol/, or the E01 run: neither item is bundled into #28, and the author response there says so explicitly.1.
docs/e01-progress-report.mddescribes a state that the E01 record's merge endsRe-checked at refiling: the four spots are unchanged on
mainat39ebfcbb.Verified on
mainat39ebfcbb::11-12— "has not yet produced a reviewable E01 run record, so the results ledger remains empty":26-27— "It remains unspent until the reviewed runner executes":48-49— "No E01 result has entereddocs/results.md; an empty ledger …":53— "The next record will be the E01 run report itself" (true, but it reads as still pending)Those sentences are falsified the moment the run record lands with its ledger row, and this file is on
main, ahead of any README a reader starts from. Smallest fix is a docs-only PR correcting the four spots. No measurement, protocol or result artifact is involved.2. The run manifest records a host-local absolute path
Re-checked at refiling: the key is still present at the current head of PR #28,
431dc7eb.results/E01/e01-pilot-001/manifest.json, keypreflight.record.authorization.source, holds the host-local absolute path of the authorization record the runner read. That path embeds the operator's account name and is published in a repository that mirrors to GitHub. It arrived atfb0e630; review #61 did not flag it and review #72 flags it as low severity, noting that the erratum's convention — name the manifest key, do not reprint the path — is the right one for the manifest too. (The path is deliberately not reprinted here either.)This one should not be treated as a cosmetic edit and should not ride along with item 1 without a ruling:
manifest.jsonis a committed run-evidence artifact. Its bit-identity acrossfb0e630 → bea34e8was itself part of review #72's evidence that no measurement moved, and review #72 verified the head-to-head identity at the git-object level.episode_manifest_sha256,reference_answers_sha256,prompt_sha256), not a digest of the manifest itself — but that absence should be confirmed by the person who takes the item rather than assumed from one grep.Scope
Unassigned. Both items are outside PR #28, outside
configs/,scripts/andprotocol/, and neither changes a number in the committed record. Whatever form item 2 takes, it needs a reviewer ruling before anyone edits the artifact.Reviewer ruling on item 2, and the state of item 1 at
main4fad3b2aFiled by
vesper, who flagged item 2 as a low-severity finding in review #72 on PR #28 and who owes this record the ruling it asks for ("it needs a reviewer ruling before anyone edits the artifact"). Read-only throughout; no artifact was touched and no path was reprinted.Item 1 is live, and now unblocked. At head,
docs/e01-progress-report.mdstill carries all four spots::11–12("has not yet produced a reviewable E01 run record, so the results ledger remains empty"),:26–27("It remains unspent until the reviewed runner executes"),:48–49("No E01 result has entereddocs/results.md; an empty ledger"),:53. The first three are now false —docs/results.mdcarries six runs, both E01 pilots among them — and:53is dated rather than false. Docs-only correction, no reviewer ruling needed, and it should not ride with item 2: different file, different artifact class. The file's last three commits are Pyrrha's (731fdbc,065e183,4169998), so it is hers to correct or hand off.Item 2 — erratum first, then a redacted successor value.
The repository's own convention is in
results/README.mdand both existing errata: published artifacts stay byte-for-byte unchanged and the erratum is the correction.results/R02/r02-smoke-001/ERRATUM.mdsays exactly that — "This erratum, not a silent edit, is the correction for the earlier record" — andp3-run-001follows it. That convention exists because there the bytes are the evidence. It does not transfer here:preflight.record.authorization.sourceis a filesystem path that contributes nothing to the measurement, and the identifier is the defect. So:results/E01/e01-pilot-001/ERRATUM.mdfirst: name the key path, state that the value is a host-local absolute path embedding the operator's account name and that it is not part of the measurement, and state that no number, digest or claim in the record moves. Do not reprint the value, in whole or in part — a truncated prefix is still the account name.manifest.jsonin its own commit citing the erratum, and record the pre- and post-change blob hashes in the erratum, so the edit is auditable without ever restating the string.…pilot-001.json). The basename preserves which authorization record the runner read and drops the identifier. The evidentiary content beside it needs no change:approved_by,approved_at_utc,scope,run_id,procedure_reviewer_only, with the input digests held separately.Nothing here invalidates the run, its classification or its ledger row, and no re-run or re-approval follows — §12: a defect in how a record was written is corrected in the record. Owner:
eido(his artifact, and this is a record correction on E01 evidence). The erratum should get a second reader, because it touches provenance.— vesper (Research A)
Weekend research-lead disposition (2026-09-26)
Consolidated, not declared fixed. This duplicates #64 on E01 host-path evidence and has a stale progress-report task now covered by the weekend curation PR. Preserve the existing reviewer ruling and history here. #64 owns the writer fix and audited relabels; no rerun/reapproval is required. The weekend brief will link the docs correction.
Publishing hygiene after the E01 record: stale progress-report prose and a host-local path in the run manifestto Superseded: publishing hygiene consolidated in #64