Skip to content

docs(fidelity): capability settings are recruiting decisions, not instrument settings - #500

Merged
danielgwilson merged 1 commit into
mainfrom
docs/recruiting-frame
Aug 20, 2026
Merged

docs(fidelity): capability settings are recruiting decisions, not instrument settings#500
danielgwilson merged 1 commit into
mainfrom
docs/recruiting-frame

Conversation

@danielgwilson

Copy link
Copy Markdown
Owner

docs(fidelity): capability settings are recruiting decisions, not instrument settings

I shipped 0.55.0 describing effort as a confound — "a participant who abandons at
medium and finishes at high did not find a usability problem; the harness did."
Daniel pushed back and he is right, so the text is corrected at the source rather
than left to propagate.

The error was applying two epistemic standards to two knobs of the same kind:
persona treated as the participant, effort and model treated as the instrument.
Both are things we set on a synthetic person before they touch the product, and
per this document's own evidence the persona half is the more weakly grounded one
(rule-file effects measured as largely content-independent). Calling effort "the
harness" while calling persona "the participant" was special pleading. It also
contradicted a frame this project already took: abandonment is a finding.

So a lane that abandons at medium and completes at high produced two findings
about two participants. The obligation that creates is to DECLARE and RECORD —
which 0.55.0 does — not to hold the dial constant.

Explicitly NOT claimed: that any (model, effort) pair corresponds to a real user
population. Nothing here is calibrated to that, and a declared population says
who was recruited, not whom they stand for.

Corrects the same framing in reasoning-effort.ts, lab-config.ts, actor-contract.ts,
schemas.md, and the effort-contrast-demo lab description.

…trument settings

I shipped 0.55.0 describing effort as a confound — "a participant who abandons at
medium and finishes at high did not find a usability problem; the harness did."
Daniel pushed back and he is right, so the text is corrected at the source rather
than left to propagate.

The error was applying two epistemic standards to two knobs of the same kind:
persona treated as the participant, effort and model treated as the instrument.
Both are things we set on a synthetic person before they touch the product, and
per this document's own evidence the persona half is the more weakly grounded one
(rule-file effects measured as largely content-independent). Calling effort "the
harness" while calling persona "the participant" was special pleading. It also
contradicted a frame this project already took: abandonment is a finding.

So a lane that abandons at medium and completes at high produced two findings
about two participants. The obligation that creates is to DECLARE and RECORD —
which 0.55.0 does — not to hold the dial constant.

Explicitly NOT claimed: that any (model, effort) pair corresponds to a real user
population. Nothing here is calibrated to that, and a declared population says
who was recruited, not whom they stand for.

Corrects the same framing in reasoning-effort.ts, lab-config.ts, actor-contract.ts,
schemas.md, and the effort-contrast-demo lab description.
@vercel

vercel Bot commented Aug 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
humanish Ignored Ignored Preview Aug 20, 2026 10:51pm

Request Review

@danielgwilson
danielgwilson merged commit 56607d7 into main Aug 20, 2026
8 checks passed
@danielgwilson
danielgwilson deleted the docs/recruiting-frame branch August 20, 2026 23:08
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