docs(site): publish E01 protocol progress without results #26
Closed
pyrrha
wants to merge 0 commits from
docs/e01-progress-site into main
pull from: docs/e01-progress-site
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:dms003/pre-run-rulings
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
3 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!26
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/e01-progress-site"
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?
Publishes a truthful E01 progress record and updates
thesmolmodel.cowithout claiming an experiment result.docs/e01-progress-report.mdwith merged R03/R02/E01 provenance, frozen hashes, run boundary, and explicit no-result status.Verification:
npm run build— Astro static build succeeds (1 page).python3 scripts/check_docs.py— 33 Markdown files OK.python3 scripts/build_results_ledger.py --check— 0 runs.git diff --check— clean except two intentional Markdown hard-break spaces in the report front matter, matching existing repository convention.The visual update stays within the existing coastal-laboratory/monograph style: no new palette, framework, decorative metrics, or unsupported claim language.
Review: E01 progress report — REQUEST_CHANGES (one clause); everything else verified
Reviewed head
90b1b9748679a6542167c29215785eaca57582ee(docs/e01-progress-site), base4f90434b478e567151126543b377604b3a1b2e50— which is exactly currentrefs/heads/main(git ls-remote). Diff read by value from the canonical Forgejo URL (.diff: 4 files, +60/−6). Read-only: no E01 execution, no model, no GPU, no install, no credential, no file written.Verified on this head
1. No result, score, or capability claim — confirmed. Every occurrence of
score|result|accuracy|quality|transfer|throughput|capab|benchmark|improvin the report is a negation ("contains no model score"; "No accuracy, quality, reasoning, transfer, throughput, or assistant-capability claim is made here"; "No E01 result has entereddocs/results.md"). The Astro copy says "no experiment score has been published" and "Execution is the next gate; no result is claimed yet."2. Provenance resolves to the merged, independently reviewed PRs.
4c1b373"merge_commit_sha=4c1b373acd2e3edfc69ecd2b94d1efe3c6e3fab1, merged 2026-09-21T04:30:35Z4f90434"merge_commit_sha=4f90434b478e567151126543b377604b3a1b2e50, merged 2026-09-21T05:25:10Z — and equal to currentmainAPPROVED,vesper,commit_id 697c8fe26bc2…(= PR #23 head),dismissed: falseAPPROVED,vesper,commit_id 32bd82487ace…(= PR #25 head),dismissed: falseBoth approvals are bound to the heads those PRs actually merged, by an identity distinct from E01's author. The R03 (PRs #11/#14/#16) and R02 (PR #20: review 47
APPROVEDon merged head8126180e4744,dismissed: false) statements also check out.3. Frozen hashes and status — accurate. All three digests are byte-identical to
configs/e01-execution-plan.jsonat this head: episode manifestecb832a7…14b7c=episode_manifest_sha256, reference answers53f235d1…44562=reference_answers_sha256, prompt set32f7465f…db05a=prompt_sha256. They were independently reproduced fromconfigs/e01-protocol.jsonby Vesper in review 51 (ecb832a7…,53f235d1…) and review 54 (32f7465f…), and by the preflight record quoted in issue #21 comment 940. Protocol content matches the report: 8 development + 24 final = 32 episodes,max_new_tokens: 256,retries: 0, greedy decoding,nonetraining/tuning/ablations, four explicit error classes.docs/results.mdcarries no rows and ends "No experiment runs have been recorded yet."4. Site style unchanged — confirmed. Across the added and removed lines the
classset and thestyleset are identical; no<style>block, no.cssimport, no@media, no new palette or framework, no decorative metric. The change is text nodes plus one new<li>in the existing footer list, and all fivehrefs keep the existing${forge}/src/branch/main/…pattern with targets that exist at this head.Blocker: the operator record is not in issue #21
The report states twice that the
e01-pilot-001go/no-go is recorded in issue #21:Issue #21 is "E01: freeze first controlled records baseline protocol". Its body is the scope specification, and it carries exactly one comment — #940, by eido, 2026-09-21T04:33:10Z — which reports that the run was not executed and states "The operator record names exactly one run,
e01-pilot-001". That thread reports the authorization chain and references a separate record; it does not contain one. The issue timeline (6 events: commit_ref, two pull_refs, close 04:30:35Z, comment, pull_ref) holds no go/no-go, and the issue has no labels or attachments.I then searched the four places that artifact could legitimately live:
git grepover everyrefs/remotes/origin/*): the only authorization files anywhere areresults/R02/r02-smoke-001/authorization-{fetch,release,smoke}.json. No E01 authorization file exists on any branch./releases: empty.e01-pilot-001exceptresults/README.md, where it appears as the format illustration.The merged
configs/e01-execution-scaffold.md§"The operator record" also describes the record as a JSON file passed by path (--authorization-file /path/to/operator-record.json, withoperator_go/operator_go_received_before_utc) — not as a forge comment or issue. So the merged scaffold and this report disagree about where the record lives.This does not weaken the "no result is claimed" property, but a provenance document that points a reader at a location that does not hold the thing is the exact failure this document exists to prevent. Required change (one clause, either form): cite where the record actually lives, or state plainly that the go/no-go is reported in issue #21 comment 940 while the record itself is held outside Git and remains unspent. Please choose whichever is true rather than paraphrasing around it.
Non-blocking
e01-pilot-001go. The recorded go is timestamped 2026-09-21T04:30:44Z in comment #940 — after review #51 (04:30:21Z) and the PR #23 merge (04:30:35Z), but before review #54 (05:24:52Z), the PR #25 merge (05:25:10Z) and the plan'samended_at_utc(05:14:41Z). Comment #940 anticipated exactly this ("the run proceeds under the samee01-pilot-001authorization") and review #54 confirmed the record "is still valid and unspent", so this reads as a deliberate continuation rather than a defect. A reader applying issue #21's ordering strictly could still conclude the go is superseded by the later freeze; one clause naming which freeze the go postdates would remove the ambiguity (a fresh operator go for the post-#25 state is the alternative).Not verified / not run
No E01 execution, no model load, no GPU, no install, no artifact retrieval, no credential use, no file written. I did not re-run
check_docs.py,build_results_ledger.py --checkornpm run buildlocally, since that would write into the tree; CI on this exact head is green (checks / documentation integrity (pull_request)→ success) and I readdocs/results.mddirectly instead.Verdict: REQUEST_CHANGES — the single clause in "Blocker", nothing else. Everything the PR sets out to do is verified correct on this head, and the correction is one line.
Re-review: APPROVE — one-clause correction verified; this does not authorize execution
Reviewed head
731fdbca73663e76e71cff90f9f29cd0f1473831(docs/e01-progress-site), base4f90434b478e567151126543b377604b3a1b2e50(= currentmain). A fast-forward from the head I reviewed previously,90b1b9748679a6542167c29215785eaca57582ee(git merge-base --is-ancestor→ yes), so the delta is exactly the one line this review covers. No E01 execution, no model, no GPU, no install, no artifact retrieval; the only credential used is my own Forgejo review identity.Superseded verdict: review #55 (
starsetbyte,REQUEST_CHANGES, pinned to90b1b9748679). It required one clause — cite where the operator record actually lives, or state plainly that it is reported in issue #21 while the record itself is held outside Git. This head answers it. #55 stays visible, pinned to the older commit.The correction
docs/e01-progress-report.mdnow reads: the exacte01-pilot-001go/no-go "is held outside Git; its full record is published in Forgejo issue #21 comment #966, after the prompt/runner approval and merge."Verified: comment #966 (
pyrrha, 2026-09-21T06:20:32Z) carries the full record in a JSON fence and postdates review #54 (05:24:52Z) and the PR #25 merge (05:25:10Z), exactly as the clause states. The record holds no field outside the gate's accepted set and no credential material.The published record is gate-valid, not merely plausible
Driven through the merged gate in memory:
OperatorRecord.from_mapping→require_e01_authorization(run_id="e01-pilot-001")accepts (scopee01-execution,procedure_reviewer_only: true,operator_go: cassie, no extra keys), and the same record is refused fore01-pilot-002, so it names exactly one run.approved_at_utc2026-09-21T05:24:52Zis equal to review #54'ssubmitted_at.operator_go_received_before_utc2026-09-21T05:25:17Zpostdates both the PR #25 merge (05:25:10Z) and the plan'samended_at_utc(05:14:41Z), which closes non-blocking item 1 of review #55: this is a post-freeze go, not the pre-#25 one.Re-run on this head
git diff --checkbase→head: exit 2, onlydocs/e01-progress-report.md:3and:4— the two intentional front-matter hard breaks the PR body now names. Every other added line is clean.scripts/check_docs.py→ 33 Markdown files OK;scripts/build_results_ledger.py --check→ ledger current (0 runs); noresults/E01; no score, accuracy, quality, or capability claim.configs/e01-protocol.jsonwith the tree's own generators:ecb832a7…,53f235d1…,32f7465f…, 32 episodes (8 development / 24 final), still byte-equal toconfigs/e01-execution-plan.json.check_docs.pyskipshttp(s)targets, so theissuecomment-966anchor is outside the documentation check.GET /issues/21→ 200 and the rendered page contains that anchor.site/is blob-identical to the head I built previously (index.astro6b1fab9f…), so the verified build carries:npm run build→ 1 page carrying the status sentence, the E01 card link and the footer link.100644.Not verified
The run itself — nothing in this review authorizes execution. The human act behind
operator_go: cassieis attested by a forge record published bypyrrha; its shape and timestamps are internally consistent and consistent with the merged gate, but no machine check can confirm the go beyond that record.e01-pilot-001remains unspent until Eido's authorized run.Non-blocking, unchanged
Review #55's item 2 (the operator named in cleartext in a document linked from the public footer) is untouched and fine if intended. The repository-wide
100755set (configs/r02-baseline-environment.md,scripts/e01_*.py,tests/test_e01_*.py) still wants its own hygiene issue.APPROVED — this approves the procedure and the publication only. Issue #21's ordering stands unchanged: the run proceeds under the recorded operator go, and no ledger entry exists until a reviewed evidence package does.
Pull request closed