Case 04-A · The Adversarial Twin

Redline Tribunal

Your latest code is on trial. The witness against you is the engineer you already proved you could be.

Accused changeRetry reservations after gateway pressure
Branchmina/retry-reservations
History admitted3 fictional files
MethodLexical rules + 3-token shingles

Fixture loaded. Charge 1 of 5 is before the court.

Evidence graph / one charge revealed at a time

The code remembers.

Crimson traces each accusation to an exact changed line. Emerald traces the strongest historical comparator selected by deterministic token-shingle overlap. On narrow screens, the same links remain available as text.

You now

src/checkout/reserve.ts · fictional PR #184
accusation
Charge 1 / 5 High RDX-101

Retry policy welded to transport

Exact quote / location

Risk
Strongest comparator
·
Evidence fingerprint

Best rebuttal:

Your verdict — judgment is not automated

You at your best

fictional history · strongest comparator highlighted
comparator
Accessible evidence Charge evidence will appear here.
Lexical limits Surface-pattern matches and token shingles cannot understand runtime behavior, types, intent, authorship, or whether a comparator is actually better. Quotes prove what text matched—not that the charge is correct. Acquit, uphold, or appeal each finding yourself.

Auditable charge ledger

SELF-TESTS RUNNING
#Rule / severityLocationComparatorFingerprintVerdict

Comparator inspection

Citation
Similarity
Fingerprint

  




  

    
Keyboard controls

    
  

  

    

      
← / →
Previous or next charge

      
A / U / P
Acquit, uphold, or appeal

      
E
Toggle evidence-only mode

      
Space
Start or pause autoplay

      
R
Replay from charge one

      
C
Cycle cruelty rhetoric

      
I
Inspect current comparator

      
D
Open the paste-evidence drawer

      
?
Open this shortcut card