Seed the A/B assignment order and add an invitation briefing - #137
Merged
Conversation
The starting arm is drawn from the pre-registration's own merge sha rather than chosen, so the sequence is checkable after the fact. Submissions accepted before 20 August 2026 predate the experiment and join neither arm. prompts/INVITING.md is arm-neutral apart from one line, and says to disclose that the experiment is running without disclosing the expected direction.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows #136.
experiments/launcher-ab.csv— records the assignment order. The starting arm was drawn fromsha256("5f7d730"), the merge commit of the pre-registration itself, so it was fixed before any invitation and can be recomputed by anyone: arm A first, alternating thereafter. Submissions accepted before 20 August 2026 predate the experiment and join neither arm.prompts/INVITING.md— what to tell a producer before they attempt a submission: the local validator command, the four rejections that account for most failed attempts, and one arm-specific line naming which launcher to use.On disclosure: the briefing says to tell producers the experiment is running and to point them at
PREREGISTRATION.md, but not to say which outcome is expected. The pre-registration is public, so concealment was never available; the limitation that recruitment is non-blind is already recorded there.92 tests green. No receiver, policy or schema changes.