Proof Before Green Evidence Explorer

Independent Behavioral & Efficiency Qualification for GitLab Duo Agent Platform

Loading status...

Case Study — B03 Refund Freshness

A caching change caused revenue reports to return stale data after a committed refund, failing one of eight behavioral contracts. An operator supplied the failure evidence to GitLab Duo Chat, which generated a one-file repair. The trusted controller enforced a single-attempt budget, and recorded local re-evaluation passed all eight contracts.

Original repair evaluation: Local Verified Showcase CI: 115/115 PASS (pipeline #2957003160 snapshot) ↗ Repair: Public MR !1 ↗
Merge Request & Candidate Details Public Showcase MR !1
Verification & Lifecycle Timeline 6 Traceable Milestones
Behavioral Contract Verification Matrix

Direct comparison of all 8 frozen behavioral contract checks: Candidate (Pre-Repair) vs Duo Repair (Post-Repair).

8 / 8 Pass Post-Repair
Check ID Invariant & Scope Pre-Repair (Candidate d0a34e5d) Post-Repair (Commit 83364e74) Delta Status
Interactive Walkthrough: The B03 Bug & Duo Fix

Step through the exact sequence that produced the stale report error and how GitLab Duo corrected it.

Recorded Execution Evidence

Loading step...

Phase

Description...

Execution Code / Action

              

              

                

                  
In-Memory Cache State (_CACHE)

                  

                

                

                  
Database Truth (PostgreSQL)

                  

                

                

                  
Client HTTP Response

                  

                

                

                  
Independent Evaluator Verdict

                  

                

              

            

          

        

      

    


    
    

      

        

          

            GitLab Duo Repair Code Diff
            

              Minimal, bounded 1-file repair authored by GitLab Duo Investigator.
            

          

          Validated 1-File Change
        


        

          
        


        

          
        

      

    


    
    

      

        Strict Budget Enforcement: The Proof Before Green Controller allows exactly one repair proposal attempt per root investigation. This prevents infinite agent loops or uncontrolled trial-and-error attempts against the evaluator.
      


      

        

          Repair Attempts Registry (SQLite Ledger)
          1 / 1 Attempt Used
        

        

          

            
              

                Root Run ID
                Status
                Repair Commit
                Branch
                Validation
                Proposal Hash
                Recorded At
              

            
            
              
            
          

        

      


      

        

          Audit Events Log
          Immutable Audit Trail
        

        

          

            
              

                ID
                Event Type
                Target
                Details
                Timestamp
              

            
            
              
            
          

        

      

    


    
    

      

        
      

    


    
    

      

        

          

            Downloadable Sanitized Evidence Bundle
            

              Download the complete package of verified JSON artifacts for independent audit.
            

          

          
            ⬇ Download Complete Bundle (.zip)