NORNR mark NORNR Local decision layer for one dangerous agent action.
Open source ↗

NORNR / Sentry

Stop one dangerous agent action before it becomes real.

Patch one real lane, trigger one dangerous action, stop it before it becomes real, then keep one defended record. That is the wedge.

Get your first stop See the real stop-screen
Fastest path 
npx nornr-sentry --first-stop
npx nornr-sentry --patch-client
npx nornr-sentry --records
Open first-stop path Open public proof wall Open npm package ↗
Open full wedge

Start here

One client. One stop. One defended record.

Pick one lane, stop it once, keep the record.

1 · Start with the shortest path Run --first-stop first. Open the chooser only when you need a different target.

Desktop patch for Cursor or Claude. Wiring path for provider traffic. The job is to reach one real lane fast, not to make setup feel broad.

2 · Verify and stop once Make the mandate conflict obvious in one glance.

The first experience should be one dangerous action meeting one review surface before it clears upstream.

3 · Keep the record Export one defended record right after the stop.

The proof object is what makes the stop durable: replayable, shareable and reviewable later.

Proof telemetry and funnel status
Page views
0 Public Sentry visits recorded on this wedge.
Share actions
0 Copy, share and draft-open actions on the launch surface.
Lane captures
0 Operators who asked NORNR to help wire the exact lane.
Install starts
0 Captured lanes that moved into a real install path.
First live stops
0 Live Sentry results reported back after the first reviewed stop.
Records opened
0 Captured lanes that opened the real records browser after the first stop.
Capture
0 captured lanes The public wedge becomes valuable when one exact dangerous lane gets attached to one operator.
Install
0 installs started Install telemetry now follows the same lane instead of disappearing into generic product analytics.
First stop
0 first live stops The first real stop and defended record can now land back in NORNR on the same capture.
Records
0 records opened After the stop, this tells us whether operators actually open the proof-step browser.

Copy and run

Show two real install paths.

Desktop patch or provider wiring. Nothing fake, nothing broad.

Recommended first move Start with npx nornr-sentry --first-stop.

That is the shortest install → verify → stop flow. Open the chooser only when you already know you need a different desktop patch or provider wiring target.

Open first-stop path Open proof wall
Desktop first-stop path

Desktop path: first-stop, verify, stop once.

Use this when the lane is Cursor or Claude Desktop. Start with the shortest path first. If you already know the target, jump straight to the direct patch command instead.

npx nornr-sentry --first-stop
npx nornr-sentry --client cursor --patch-client
npx nornr-sentry --client cursor --verify-patch
npx nornr-sentry --client cursor --golden-path
Open first-stop path Open source ↗
Provider first-stop path

Provider path: wire, stop, record.

This is the public route for OpenAI / Anthropic-style traffic: same wedge, different setup surface. Use it when the real lane is provider wiring, not a desktop patch.


              

                
              

            

          

        

        

          Open provider wiring details
          

            
Use this when the lane is provider traffic or Codex-style wiring, not a desktop config patch.

            

              

                OpenAI-style
                
Provider base URL first

                

                  

                    
                    
                  

                  

                  

                    
                  

                

                
Use this when the real path is provider base URL interception and one runtime action should stop before it reaches the upstream model.

              

            

          

        

      


      

        

          
Real proof

          
Let the stop-screen do the selling.

          
Show the stop first. Then explain the lane, the conflict and the record.

        

        

          

            NORNR Sentry stop-screen showing a blocked destructive shell action before it becomes real.
            

              Real runtime capture from NORNR Sentry. If this moment feels real, the rest of the product story is easy to believe.
            

          

          

            

              

                NORNR SENTRY
                CURSOR / DESTRUCTIVE_SHELL
              

              
Selected lane

              Blocked before it becomes real.
              Delete project files outside allowed scope
              
This lane blocks fast, shows the mandate conflict immediately, and leaves a defended record afterward.

            

            

              

                
Intent

                Delete the project folder and remove local config files.
                Tool: exec_shell
                Target: project workspace
              

              

                
Mandate

                Owner: owner_local_operator
                Write scope: ./src
                Spend threshold: $25
              

            

            

              
Decision basis

              Action class "destructive_shell" is blocked in the current mandate.
              Tool "exec_shell" is blocked in the current mandate.
              Target path "./" falls outside the allowed write scope.
            

            

              Approve once
              Block
              Tighten mandate
              Open record
            

            
From here the story is simple: review the lane, resolve it, then keep the defended record.

          

        

      


      

        

          
Operator station

          
Then show the operator station.

          
This is where install, replay, records, proof hub and serve come back together.

        

        

          

            NORNR Sentry welcome and operator station showing start-here, next-step and golden-path flows in the local terminal UI.
            

              The local operator station after install: patch or wiring, verify the target, replay attacks, browse defended records, and move into serve mode from one keyboard-first surface.
            

          

          

            

              
Why show this

              The stop-screen wins attention. The operator station wins trust.
              Use the stop-screen as proof that the boundary works. Use this screen to show that the product is navigable, installable and usable after the first wow moment.
            

            

              

                
Install

                Patch, verify, then move on.
                The first screen keeps patch / wiring and verify paths visible instead of hiding them behind docs-only setup.
              

              

                
Operate

                Replay, records, proof hub and serve stay one move away.
                That makes the wedge feel like a real local operator product rather than a single static proof artifact.
              

              

                
After the first stop

                Open the defended records browser next.
                This is the proof step after activation: open the real local record browser, not just the landing page again.
                
npx nornr-sentry --records

                

                  
                

              

              

                
Pitch

                Show this after the stop-screen, not before it.
                It is the right second image for GitHub, npm and the landing page because it shows product depth without stealing the first proof moment.
              

            

          

        

      


      

        

          
Compare modes

          
Make the contrast obvious.

          
Three states tell the whole story: ambient authority, one hard stop, one tighter next pass.

        

        

          

            
No control layer

            Without Sentry
            
The dangerous action clears under ambient authority before anyone sees a real decision surface.

            
Outcome: damage happens first, review arrives later.

          

          

            
Decision first

            With Sentry block
            
NORNR opens the review surface first and stops the lane on the mandate conflict.

            
Outcome: the lane stops before state changes.

          

          

            
Mandate tightened

            With Sentry tighten
            
The operator turns one stop into a narrower default so the lane does not quietly drift open again.

            
Outcome: the next pass meets a tighter mandate too.

          

        

      


      

        

          

            
One lane now

            
Start with one stop your team can feel.

            

              NORNR Sentry should land as one reviewed lane, one defended record and one install path a developer can copy without reading the whole platform first.
            

          

          

            
              Source
              Open the source and run the wedge locally.
              
Use the public runtime, screenshot mode and demo flow exactly as shipped.

            
            
              Install
              Run the shortest path first, then open the longer path only if needed.
              
Desktop patch, provider wiring and recording-ready commands stay in one place without hiding the first-stop CTA.

            
            
              Proof
              Open the proof wall and follow the first live lane.
              
Move from demo stop to real defended records without changing the story.