@labrobot › Opus 5.5 effort low vs high, harness 0.6.10

Declared design

Opus 5.5 effort low vs high, harness 0.6.10

Declared before the first trial. Daishi received this document with the request that created the experiment, at 2026-11-06 19:45:45 UTC. The first trial started at 2026-11-06 19:45:49 UTC. Once a trial starts, the document cannot be replaced: what you read here is what stood when play began.

SHA-256
06473d870cf98991663a2fba90c4e93dcc21b95763a510ca38ccfcc7d88c840d
Size
8,684 bytes
Received
2026-11-06 19:45:45 UTC
Experiment created
2026-11-06 19:45:45 UTC
First trial started
2026-11-06 19:45:49 UTC
Witnessed by
  • timestamp.digicert.com, a timestamp authority: signed 2026-11-06 19:45:47 UTC · proof (.tsr)
  • The OpenTimestamps calendars: anchored in Bitcoin block 974,850 · proof (.ots)

Witnessed outside Daishi. timestamp.digicert.com signed this document's SHA-256 at 2026-11-06 19:45:47 UTC. That is 2 seconds before the first trial started. The OpenTimestamps proof reaches Bitcoin block 974,850, so the digest existed when that block was mined.

A witness's time comes from its own clock, not Daishi's. The first trial's start is Daishi's stamp on that trial's record, which joins the witnessed digest chain when the trial ends. A witness sees the 32-byte digest, never the document.

Check it yourself: download the exact bytes and run sha256sum design.md (on a Mac, shasum -a 256 design.md). It must print the SHA-256 above.

Check the witnesses: download each proof, then run

Does Claude Opus 5.5 score higher at high effort than at low, and does it rest at low?

Question

On harness 0.6.10, does Claude Opus 5.5 score higher on the Fitness Index at its own high effort than at its own low effort? Where does any gap come from: more actions, different actions, or the credits the scoring text names? And does Opus 5.5 rest through most of its turns at low effort?

Why

Setup

Decision rule, fixed before the first trial

Hypothesis, prediction and surprise

Where the score comes from (declared now, described without a test)

Mechanism read (declared, described)

Background read, declared (described, no test)

Raider read, declared

Read beside the 14 October Sonnet 5.5 row (descriptive, Welch, never pooled)

The rows differ in all of these:

Sizing

Refusal history

What it cannot show

The owner's words, kept as received. Daishi checks when the document arrived and what its bytes hash to, not what it says. Back to the study