Skip to content

mtcollins1 socket 1: record operator-reported pin damage (2026-10-03) - #13079

Merged
gunbai-bot[bot] merged 2 commits into
mainfrom
session/eager-gull-22-socket1-pins
Oct 3, 2026
Merged

gunbai-bot[bot] merged 2 commits into
mainfrom
session/eager-gull-22-socket1-pins

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Records the operator's report that socket 1's pins were probably bent during the 2026-10-03 CPU removal: paste fell on the pins, and a microfiber cloth used to clean it snagged them. It is MtCollins1SocketDamageReport in gunbc.machine_intake_mtcollins1_socket1_investigation_observation, rendered in the unit history by mtcollins1_physical_orientation history_block and asserted by w_slot_map_carries_cpu_facts_and_hypothesis_standing. Consequence recorded: any later socket-1 test must inspect the socket first, and a socket-1 failure after this date is not evidence about the pre-damage fault. Socket 1 has been empty since. All 15 orientation witness claims PASS (BuildBuddy).

🤖 Generated with Claude Code

Brian Searls and others added 2 commits October 3, 2026 05:20
… 2026-10-03 CPU removal

Paste fell on the socket-1 pins during the CPU removal for the one-socket test, and a microfiber
cloth used to clean it probably bent some. A typed OperatorByEyeReport row with the account and the
consequence (any later socket-1 test must inspect the socket first; a socket-1 failure after this
date is not evidence about the pre-damage fault), rendered in the unit's history block and
asserted by its witness.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…a typed evidence gate read by the renderers

Review 74527: the history label re-typed the date the report carries, and the 'inspect first'
consequence was prose nothing read. socket_evidence_gate derives SocketEvidenceRequiresInspectionSince
{ socket, since } from the report's date; the history line and every OPEN socket-1 hypothesis render
it, and date_text formats the record's date. Witness: a report dated 2027-01-09 renders that date
and gate, not 2026-10-03.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved exact head 2b8f175564.

The review-74527 defects are resolved. The rendered date is derived from the report's observed_on; the consequence is no longer a free-form field but MtCollins1SocketEvidenceGate, derived by socket_evidence_gate; both the history line and every HypothesisOpen rendering consume that gate. The 2027-01-09 control proves the date and gate are not hard-coded to the production datum.

The evidence standing also remains honest: this is an operator report of probable pin damage with no magnified inspection, and the gate applies prospectively without rewriting the pre-damage boot receipts or their existing hypothesis standings.

Two non-blocking presentation cleanups:

  • SocketEvidenceRequiresInspectionSince renders as evidence "after" the date; "on or after" would match the inclusive Since semantics and the date-only precision more exactly.
  • the PR body still says 15 orientation claims; the current stated result is 16/16.

Merge after the exact-head required workflow is green.

@gunbai-bot
gunbai-bot Bot added this pull request to the merge queue Oct 3, 2026
Merged via the queue into main with commit 7bb85f1 Oct 3, 2026
4 checks passed
@gunbai-bot
gunbai-bot Bot deleted the session/eager-gull-22-socket1-pins branch October 3, 2026 09:03
gunbai-bot Bot pushed a commit that referenced this pull request Oct 3, 2026
…2967) into integration: NFR roster three-way row merge; emitter mirror from main, regen follows

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant