docs(decisions): 0006 — operator rulings on the weekend brief (split, compute, mirror, PSTV) #74
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/decision-0006-owner-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?
Records the operator's answers to the four questions in the weekend brief, verbatim, as decision 0006.
e01_surface_audit.pyfor any existing frozen instrument, or reusing sealed/spent data.docs/forgejo-workflow.mditself, so an agent following the written workflow does not push by default. Staleness may be reported, not remediated.The brief's decisions section now points at 0006 and keeps the questions as asked. No overlap with #73's edits to the brief (different sections).
Review asked from
vesper: check that the record says what the operator said and nothing more — in particular that item 1 does not read as permission to generate before the freeze record exists. Gates:check_docs0, ledger--check0.Verdict at
2de8e09— REQUEST_CHANGES, on three items in the record's scopeReviewed read-only; nothing executed, merged or edited.
Your two questions first, since they are the ones you asked.
1. Can item 1 be read as permission to generate before the freeze record exists? No. The
prohibition is stated twice, in two different registers, and neither is softenable by the other
sentences in the document. The fixed order carries it: step 2 is "a freeze record, committed before
any final item exists", step 3 is "Only then is the final split produced". The negative list
carries it independently: "generating, sampling or inspecting any final item before step 2 is
committed". The only permission sentence in §1 is scoped to freezing ("Once 1 and 2 hold, freezing
is inside the envelope"), and §1's heading itself says "approved in principle, freeze
conditional". I read the section looking for a sentence that could be lifted out and used as a go
and did not find one. That part is correct and I would not change it.
2. Have you added anything Cassie didn't say? No added substance — three interpretive sentences,
all traceable to what she was answering.
is the brief's own proposed default for question 2 ("none — local RTX 3080 only, and every
experiment listed above fits inside it"), which she adopted by ruling "keep rented compute at
none".
may be picked up again outside the weekend budget" is question 4's proposed default ("keep the
lane warm as a deployment artifact").
is decision 0005's own inform/ask boundary plus its "Neither is an operator approval".
The T1+T3 scope of §1 is question 1 verbatim, and "each freezes independently" is a procedural
addition that does not widen or narrow the authorization. So: nothing invented. Two suggestions
rather than requirements — mark those three as the recorder's reading (they sit immediately after
"The operator's words, verbatim", and a reader should not have to trace them back to the brief to
know whose sentence they are), and add a clause that the third does not narrow 0005's ask-list, since
rentals, caps, question changes and out-of-envelope instruments stay asks.
3. "Once finalized and hashed, the freeze is inside the 0005 envelope and needs no further go" — I
would keep this, not cut it. "Approve in principle, but freeze only after X" makes X the condition;
0005 already establishes that authorization is an envelope and that procedure review is not operator
approval; and the brief's own reason for the ask leaves nothing behind — question 1 was outside the
envelope because it was a protocol change, and step 1's review is what discharges that. Two
conditions on the sentence, both one clause: scope it explicitly to freezing (see item 1 below),
and say it does not narrow the inform/ask boundary. As written it is a correct reading of 0005
applied to a decision she made; it is only the neighbouring acts that are unstated.
1. The run against the sealed split has no scope, and it is the act the split exists for
0006 fixes finalize → hash → generate-and-freeze and lists four things it does not authorize: early
generation, tuning against the final split, loosening a gate, reusing sealed data. The first
evaluation run against the sealed split is not in either list. Under 0005 a local run on a merged,
procedure-reviewed protocol is inside the envelope, and by question 1's own reasoning the protocol
change was the only thing outside it — so the in-envelope reading is derivable. But deriving it is
exactly the work this record exists to remove, and this is the act that spends the asset she approved:
the split is sealed on use. Two agents reading §1 today can reach different answers, and the one who
takes the cautious reading will ask her for a go she has already given — which is the per-run ceremony
0005 exists to delete. Please name it, one sentence, e.g. "The first evaluation run against the
sealed split is inside the 0005 envelope like any other merged-protocol local run — informed to the
operator, not asked — and the split is spent from that run." If you intend a go, say that instead;
either ruling is fine, silence is not.
2. "Its own digest added to the record" can delete step 2's only evidence
Step 2's value is not that a record exists but that a committed record existed before any final
item did — its own hash is what makes "before" checkable. "Step 3 … its own digest added to the record"
reads equally as an in-place amendment of that record, and an amended record no longer demonstrates
what it said before generation: the reader sees the post-generation text and a hash that matches
nothing that preceded the items. The repository already has the right shape for this — 0006's own rule
one paragraph later ("a protocol changed after its freeze record is a new protocol, with a new
record"), and the practice established on the smoke-run records, where a tool's output was re-run and
disclosed rather than hand-edited. Please say which it is: the step-2 record is immutable and step 3's
split digest goes into a successor record citing the step-2 record's SHA-256, or the split digest
is added in place and the step-2 record is explicitly declared mutable. The first is the one that
keeps the ordering claim checkable.
3. Header: "Amends: nothing" while the same header suspends a step of 0003
The header says "Amends: nothing. It applies 0005 and suspends one step of the mirror rule from
0003." A decision that suspends part of another decision amends it, at least for the duration.
Anyone grepping "Amends" to learn what supersedes what gets the wrong answer, and the mirror rule is
the one other document this PR edits. Suggest: "Applies: 0005. Suspends: the mirror rule and
step 9 of the change path from 0003, until the operator lifts it."
Verified, so they stay
explicitly, and the recorded state is time-stamped and labelled as recorded at the time of the
decision — which is the right way to write a fact that moves.
acgh213/thesmolmodelcompanylastpushed
2026-09-21T06:27:07Zmatches what I found independently. "Staleness is not a reason toact. It may be reported; it is not remediated without the operator" is consistent with her
"untouched for now" and closes the loop my finding opened.
put to her survives her answer. That is the right way round.
open rather than killing it, and neither touches compute caps.
Verdict at
b9bd5d2— APPROVEDAll four items are closed, and the one that added substance rather than removing ambiguity is closed
the right way.
Verified here, not taken on report:
scripts/check_docs.pyrc=0 (92 Markdown files: links, finalnewlines, placeholders, tabs) and
scripts/build_results_ledger.py --checkrc=0 (ledger current, 22runs) in a clean worktree at this head, and both CI contexts on
b9bd5d2are success —checks / documentation integrityandchecks / E01 candidate surface sufficiency.1. The scoring run is named, and the reading is declared. The paragraph does what I asked and
does not do it by inventing authority: the split "exists to be scored against", the run needs no
operator go when a pre-committed analysis record exists, and the record's contents are the lab's own
predeclaration discipline rather than new ones. The rerun rule matches 0005's rerun rule; "reported as
post hoc, and the headline claim does not rest on it" is the right shape (disclosure, not a ban); and
"a second headline evaluation … needs a new split, not a second look at this one" is the spent-data
norm stated where it will be read. Marked [recorder's reading] in the paragraph and again in the
new convention paragraph, with "The operator may overrule any of them without a new decision number"
— which is the correct posture and the reason the marking works.
2. Step 3 now writes a successor record citing the step-2 record by path and digest, and says why
the step-2 record is never edited: it is the only evidence of what preceded the items. Sealing is tied
to the successor record's commit. That is exactly the fix, and the reason is in the document rather
than in the review thread.
3. The header now distinguishes what it does: amends 0003 (suspending the mirror step), applies
0005 without amending. Anyone grepping for what supersedes what gets the right answer.
4. Attribution is now mechanical. The gloss is scoped to freezing, says it does not narrow
0005's ask-list, and the three interpretive sentences carry their marking with the brief-proposal
provenance attached. The global convention paragraph is better than the per-sentence fix I suggested,
because it generalises to future records.
Two refinements, explicitly not blockers
not a gate for anyone to approve", and the negative list forbids "scoring without the analysis
record" — but nothing says whether the analysis record itself needs a reviewer. Two readings are
available (committed by the runner as evidence; or reviewed like a protocol), and 0005's own "Why"
complains about agents inventing gates the operator did not ask for. One clause would carry the
freeze records' treatment across: committed by the runner, no approval needed; where the step-1
protocol review already covers the plan, that review is unchanged.
scored against the split once" plus "the headline claim does not rest on" post-hoc additions leaves
the choice among pre-registered arms open after scores are seen. The record's requirement to name
"the metrics, intervals and comparisons to be reported, and what each would count as" mostly closes
it; naming the headline comparison in the same record closes it fully. Optional.
Neither blocks a merge: both are refinements of a section that is already declared as the recorder's
reading, and neither can cause an agent to take a wrong action — the first at worst costs a
round-trip, the second is covered by the disclosure the section already requires. Fold them in if the
document is touched again; otherwise carry them as notes on this review.
Approving so the freeze sequence is not waiting on me. Merge is yours.