I was checking into an office building last week. At the reception desk, I told them exactly who I was there to meet, and my visitor pass was printed almost immediately. I assumed I was ready to go upstairs, but the elevator didn't open. A security guard stopped me first, checked whether my pass actually allowed access to that floor, and only then let me continue. Two different responsibilities. One step recorded what I wanted to do. The other decided whether I had the authority to do it.
That moment came back to mind while reading Newton Protocol. Applications produce a business intent, but they don't determine whether that intent is acceptable. Before a transaction is constructed or signed, the Runtime evaluates the intent through Policy, where governance rules such as spending limits, approval thresholds, or compliance requirements are checked. If Policy rejects the request, the transaction never reaches execution.
It's a separation of responsibilities. Applications express intent. Policy establishes authorization. @NewtonProtocol doesn't make every application carry its own interpretation of governance, because the same action should be judged by the same rules regardless of where it originates. The system works because each layer handles the part it is designed for.
There is a short gap between creating an intent and receiving approval, where the action has been requested but execution is not yet allowed. That gap isn't unnecessary friction. It is the point where governance is established before a transaction can exist. I'm still curious how Policy evaluation is optimized under the hood, but the separation itself makes sense: applications describe what should happen, while governance decides whether it should happen.
#Newt @NewtonProtocol $NEWT $LAB $B
That moment came back to mind while reading Newton Protocol. Applications produce a business intent, but they don't determine whether that intent is acceptable. Before a transaction is constructed or signed, the Runtime evaluates the intent through Policy, where governance rules such as spending limits, approval thresholds, or compliance requirements are checked. If Policy rejects the request, the transaction never reaches execution.
It's a separation of responsibilities. Applications express intent. Policy establishes authorization. @NewtonProtocol doesn't make every application carry its own interpretation of governance, because the same action should be judged by the same rules regardless of where it originates. The system works because each layer handles the part it is designed for.
There is a short gap between creating an intent and receiving approval, where the action has been requested but execution is not yet allowed. That gap isn't unnecessary friction. It is the point where governance is established before a transaction can exist. I'm still curious how Policy evaluation is optimized under the hood, but the separation itself makes sense: applications describe what should happen, while governance decides whether it should happen.
#Newt @NewtonProtocol $NEWT $LAB $B