Left side: agent reaches merchant checkout
Show a real browser path with merchant, cart and purpose already filled in.
NORNR
The split-screen browser proof for approve before pay.
NORNR / Browser guard screen record
Split-screen proofThis is the cleanest visual proof of the product: the agent can browse and prepare the purchase, but the last consequential click still waits for NORNR to approve, queue or block the release.
The point of the screen record is not cinematic polish. It is to make the decision boundary visible to buyers in one glance.
Screen-record storyboard
If the demo needs narration to explain the control model, it is still too abstract.
Show a real browser path with merchant, cart and purpose already filled in.
Amount, counterparty, owner mandate and browser evidence appear before the pay click lands.
Keep this explicit. The buyer should see that the agent does not self-authorize the release.
Do not switch to an unrelated screen. The reviewer should see merchant, amount, reason and anomaly posture in one place.
The buyer should understand that execution happens after the decision, not before it.
End with the packet, not just the purchase confirmation.
What the split-screen should carry
Checkout approval by itself is not enough. The browser lane only becomes a category wedge when proof survives afterward.
Intent, policy decision, approval state, settlement state, receipt trail and audit export should still read like the same NORNR packet.
The queued browser action should resolve from one bundle with amount, merchant, reason and operator note in one place.
The strongest browser demo ends with a finance-safe packet, not only a screenshot that the checkout happened.