Interaction lab
Interaction Cases
Multi-turn dialogues rarely fail at the first answer. They fail when context drifts, a branch is silently dropped, or one side assumes information the other never received. These case studies document those failure points and the checks that made them visible.
What these cases test
- Branch integrity — does every conditional path stay reachable and recoverable?
- Information asymmetry — what happens when the human and the AI hold different assumptions?
- State retention — which facts survive a topic switch, a correction, or a long context?
- Boundary recovery — can the interaction return to a safe state after a bad turn?
A multi-turn refactor exposed an information gap: the AI assumed the root locale inherited shared theme options, but VitePress resolves nav and sidebar per locale. Three config copies were consolidated without changing a rendered page.
- multi-turn
- information-gap
- i18n
- Config blocks
- 3 → 2
- Pages verified
- 21
- Locale regressions
- 0
Moving 16 scoped style blocks into a global layer is only safe if element selectors are re-scoped. A rule-level diff proved parity: 108 rules in, 108 rules out, zero leaks.
- css-architecture
- boundary-control
- visual-parity
- Pages migrated
- 16
- Rules preserved
- 108/108
- Style blocks removed
- 18
- Leaks
- 0
A 22-scene, 44-choice psychological thriller reaches all seven endings, but one conditional choice can never appear: the only item that satisfies its flag is granted in a scene with no path back to it.
- state-tree
- boundary-conditions
- graph-validation
- information-asymmetry
- Scenes
- 22
- Choices
- 44
- Endings reached
- 7/7
- Dead conditional choices
- 1
A four-role social deduction game shipped with a green 11/11 regression suite and four rule-level mismatches: a +500 payoff that paid +50, a disguise checkbox the engine never read, a +75% term bound to the wrong action, and a +50 cap that was really +40.
- information-asymmetry
- multi-round-validation
- ui-engine-contract
- rule-audit
- Contract checks
- 20
- Player-visible blockers
- 2
- Engine regressions
- 11/11
- Unsupported findings
- 0