Project: Covert Cubicles Build Phase 3 / 7 —

MODULE 11 / 31 · LAYER 3 · LOGIC_CONSEQUENCE Story Flag Consequences

Translates story-flag claims from LOGIC_Branch into additional state changes. Idempotent per decisionId.

DEPENDENCIES: DATA_Peers, SM_Game, STATE_PeerTrust

Pending

Critical Caveat — Conservative Magnitudes (DRAFT ADR-015)

Researcher review required

Each consequence has a conservative default magnitude (typically -1) chosen so it is visible in trust trajectories but does not dominate the canonical \u00b11 from DATA_Decisions. These magnitudes are placeholders for empirical tuning after pilot data and pending supervisor review of the story flag taxonomy itself (ADR-013).

Automated Assertions

#	Assertion	Result	Detail

Interactive Workbench — Apply Consequences

Pick a (decision, choice) and click Apply. The trust grid shows before/after for all four peers; the effects list reads each individual change with its source flag.

Controls

Session

Pick a scenario, then Apply

Apply outcome

Quick scenarios

Defensive (should fail)

Peer trust: before \u2192 after

                        SUMMARY OF LAST APPLY
                    

                        \u2014
                    

Effects applied (last call)

No consequences applied yet.

Session consequence tags (cumulative)

No tags raised yet.

Consequence codebook (DRAFT ADR-015)

Maps each story flag (from LOGIC_Branch) to its mechanical effect. Magnitudes are conservative placeholders pending empirical tuning.

API Surface — Manual Verification

Open DevTools and try the calls below.