Where M22 measures alignment-with-self (correlation against pre-game values),
M23 characterises the actual behavioural distribution. Three operationalisations
(counts/ratios/means) across three breakdowns (whole/byPhase/byPeer). Together
they form complementary RQ1 substrate.
Per ADR-019 and ADR-021, the value-encoding codebook in M12 LOGIC_ValueEncoding
is a draft awaiting inter-rater coding and pilot calibration. M23 reads decision
choices through that codebook to produce its profile. Until the codebook is replaced
via setEncoding(), M23's profile values are also DRAFT and should not
be used for pre-registered analyses. The codebookProvenance field surfaces M12's
current status (currently isDraft=true) on every aggregate.
Complementary to M22 \u2014 different analytical question
M22 DATA_DecisionConsistency answers "how well did behaviour track stated values?" (correlation).
M23 answers "what was the actual behavioural distribution?" (descriptive profile). A session can
have low consistency for two qualitatively different reasons \u2014 drift from one's own values
vs. genuinely mixed values throughout \u2014 and only the combination of both modules can
disentangle them. Both feed RQ1; neither replaces the other.
Automated Assertions
#
Assertion
Result
Detail
Interactive Workbench — Live Value Profile
Drive the session lifecycle on the left; the profile aggregate updates after each action.
The 3\u00D73 matrix below shows all three operationalisations across all three breakdowns.
Bars are scaled within each cell (0\u20131 for ratios/means, 0\u2013n for counts).