PRovidence

Eight legs. One eye that never closes.

In repro we trust
▶ Play PRovidence Quest
1337
Annuit committis
61,204files read
23bugs found
9fixed after a repro
14left with evidence
1,337commits by sunrise

The night from the story. Run it on your repo and you get your own numbers.

Meet the night shift.

One eye in a triangle, eight riveted legs, and a shadow that only shows up after midnight.

Anatomy of PRovidence: one eye that never closes, the triangle, the dark lid, white knees, rivets, the shadow

Commits before you roll over.

It starts at 01:07. By the time you wake up there's a pull request and a report, and it's waiting for you.

● live · night shiftactivity.log

    

  


  

    
One night, six moves.

    
The same order every night. Nothing gets touched until it has been seen twice.

    
    
      
  1. I
    Map before touching
    Walks every repo, every file, every language. Writes nothing. The first night is always read-only.
    2. 
      
  2. II
    Reproduce first
    A fix is only applied if the check fails right now. Then it runs the check again. Still failing? It puts the file back.
    3. 
      
  3. III
    Every bug is a typed record
    { "kind": "leaked-secret",
  "severity": "critical",
  "confidence": 0.9,
  "blast_radius": ["src/env.ts"],
  "status": "reproduced" }
    4. 
      
  4. IV
    Four legs code, four farm
    Every finding becomes a note linked to its file and module. Open the folder in Obsidian and you see your repo as a web.
    5. 
      
  5. V
    Stay inside the web
    No pushes to main. No secrets. No deletes. No rewritten history. These aren't instructions in a prompt; they throw errors in code.
    6. 
      
  6. VI
    Write the morning report
    What got fixed, what's left with evidence, and the last line, every time: what did I not see?
    7. 
    

  


  

    
Six limits it can't cross.

    
Every write goes through one function. That function says no.

    The safety web: never push to main, never touch secrets, never delete files, never rewrite history, reproduce before fix, ask before merge
  


  

    
      

        
PRovidence Quest

        
I opened my laptop and found a game. I'm the side character in my own repo now.

        
    
          
  • The level is your contribution graph. Empty weeks are pits.
    • 
          
  • The enemies are bugs: off-by-1, null, CORS, flaky, race…
    • 
          
  • The final boss is a merge conflict.
    • 
        

        ▶ Play with your graph
      

      PRovidence Quest: the spider jumping across a contribution graph while red bugs patrol
    
  


  
What did I not see?
The last line of every morning report.








PRovidence, the spider