Interactive systems lab

Run the logic.Inspect the decision.

A browser-based proof surface for the public examples: roster cleanup, adaptive practice, competitive validation, source-lane scoring, support-depth decisions, and readable outputs.

Runs locally in browserMirrors public examplesShows decision trail
Open runner SquadBrain code Lasting Ground code

Scenario runner

Choose the proof.Watch the state change.

This is the part a reviewer can actually use: each scenario updates the evidence card, the decision trail, and the exact proof links.

SquadBrain validation
Validation boundary

Competitive results are recomputed before rank movement.

Questionable quick-match submissions are checked against timing, prompt count, answer order, and correctness before they can affect competitive state.

highrisk level
answer-speed-reviewflag surfaced
25 testspublic TS checks
  1. 01Normalize the roster input.
  2. 02Prioritize practice and rank match candidates.
  3. 03Validate the match result before accepting rank movement.
Open proof fileOpen demo

Live output summary

Readable scorecards generatedfrom the actual run.

The runner keeps the raw JSON below, but this layer turns the computed output into quick product-grade evidence: risk, support, priority, validation, and delivery proof.

SquadBrain validation

SquadBrain

Roster cleanup + adaptive play logic

The sample data includes realistic inconsistencies: duplicate names, uneven casing, invalid jersey values, multiple match candidates, and a questionable quick-match result. The demo normalizes the roster, builds prompt candidates, prioritizes practice, ranks fair opponents, and flags result risk before rankings move.

Input


          

          

            
Output

            

          

        

      


      

        

          

            
Lasting Ground

            
Source-lane scoring + packet summary

          

          
        

        
The sample packet uses sample address data. The point is the system behavior: source authority, freshness, missing lanes, and warnings shape what the packet is allowed to say.

        

          

            
Input

            

          

          

            
Output

            

          

        

      

    


    

      
What this demonstrates

      

        
Typed product thinkingCore behavior is split into small rules a reviewer can run and test.

        
Evidence disciplineOutputs change when source support is incomplete instead of pretending certainty.

        
Portfolio clarityThe page connects screenshots and case studies to executable logic.