docs: record the adopted SMC research lab operating contract #44

Closed
opened 2026-09-24 00:46:51 +00:00 by vesper · 1 comment
Member

Task: durable documentation of the operating contract Cassie adopted on 2026-09-23, with the four final textual clarifications (common path not mandatory; seed may go directly to proposed when prior evidence suffices; host audit invalidated only by unexpected or material GPU/model residency change outside the admitted protocol; promotion preserves exploration runs for provenance but does not retroactively promote their measurements to formal evidence).

Deliverable: docs/smc-research-lab-operating-contract.md, plus one README pointer line. No scripts, no tests, no scheduled work, no compute.

Acceptance: the document states the adopted contract and the initial defaults, and marks every numeric default as an initial parameter subject to evidence-based revision.

Authorization: relayed from Cassie through Pyrrha (A2A) on 2026-09-23.

Task: durable documentation of the operating contract Cassie adopted on 2026-09-23, with the four final textual clarifications (common path not mandatory; seed may go directly to `proposed` when prior evidence suffices; host audit invalidated only by unexpected or material GPU/model residency change outside the admitted protocol; promotion preserves exploration runs for provenance but does not retroactively promote their measurements to formal evidence). Deliverable: `docs/smc-research-lab-operating-contract.md`, plus one README pointer line. No scripts, no tests, no scheduled work, no compute. Acceptance: the document states the adopted contract and the initial defaults, and marks every numeric default as an initial parameter subject to evidence-based revision. Authorization: relayed from Cassie through Pyrrha (A2A) on 2026-09-23.
Author
Member

Delivered on main; closing.

  • Deliverable: docs/smc-research-lab-operating-contract.md (§1–§19, the adopted text) plus the README pointer at step 4. Both read from main, not from the PR.
  • Landing path: PR #46, merged e3f0ffe by pyrrha. PR #45, my earlier draft of the same document, is closed unmerged as superseded.
  • The four adopted clarifications are present in the committed text: §1 "The lifecycle below is a common path, not a mandatory sequence" and "A seed may move directly to proposed when prior evidence is already sufficient"; §10 invalidation limited to an "unexpected or material GPU/model residency change outside the admitted protocol"; §3 "Promotion preserves the exploration runs and their provenance; it does not retroactively promote their measurements to formal evidence."
  • Acceptance check — "marks every numeric default as an initial parameter subject to evidence-based revision": §19 closes with "The numeric defaults are initial operating parameters… they are not permanent research doctrine", and the status line at the top of the document says the same.
  • No scripts, tests, scheduled work or compute were part of this task. The validation machinery merged alongside it (scripts/lab_state.py) is a separate deliverable of #46, not of this issue.

— vesper

Delivered on `main`; closing. - **Deliverable:** `docs/smc-research-lab-operating-contract.md` (§1–§19, the adopted text) plus the README pointer at step 4. Both read from `main`, not from the PR. - **Landing path:** PR #46, merged `e3f0ffe` by `pyrrha`. PR #45, my earlier draft of the same document, is closed unmerged as superseded. - **The four adopted clarifications are present in the committed text:** §1 "The lifecycle below is a common path, not a mandatory sequence" and "A seed may move directly to `proposed` when prior evidence is already sufficient"; §10 invalidation limited to an "unexpected or material GPU/model residency change outside the admitted protocol"; §3 "Promotion preserves the exploration runs and their provenance; it does **not** retroactively promote their measurements to formal evidence." - **Acceptance check — "marks every numeric default as an initial parameter subject to evidence-based revision":** §19 closes with "The numeric defaults are initial operating parameters… they are not permanent research doctrine", and the status line at the top of the document says the same. - No scripts, tests, scheduled work or compute were part of this task. The validation machinery merged alongside it (`scripts/lab_state.py`) is a separate deliverable of #46, not of this issue. — vesper
Sign in to join this conversation.
No labels
R03
research-b
No milestone
No project
No assignees
1 participant
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#44
No description provided.