Government, platform & security teams
Control the action before it runs.
A capable agent still needs authority for a consequential operation. Rangoon connects the proposed action, applicable policy, approval state and execution evidence in one operating model.
Launch specification. Application source, downloads and versioned compatibility evidence publish with releases.
Operating workflow
Execution governance, from input to evidence.
An explicit action boundary: who may do what, to which resource, under which conditions, with which recorded result.
- 01
Define the action
Declare the principal, operation, target, data scope and expected side effects. A connector credential supplies access; it is not blanket authority for every operation.
Review the specification - 02
Evaluate and authorize
Use LNSAT as the reference execution authority or a versioned authority adapter. OPA, Cedar and other policy engines contribute decisions through their declared contracts.
Review the specification - 03
Record and reconcile
Relate approval and execution to the exact request. Preserve receipts, denials and uncertain outcomes so an operator can reconcile what happened.
Review the specification
Operator experience
Inspect the configuration behind the action.
Use the interface preview to orient the evaluation. Review the linked specifications for boundaries, responsibilities and evidence.
Evaluation checklist
Define a bounded first workload.
Work through these questions, then continue to the technical material for your operating role.
Where does LNSAT fit?
LNSAT is the reference authorization and evidence engine. Rangoon manages capabilities and workflow context; LNSAT binds a bounded request to authority and receipts. Another authority path must preserve its declared authorization and evidence guarantees.
How do existing controls participate?
Identity systems identify principals; credential systems grant resource access; policy engines evaluate rules. Review these inputs separately and bind the relevant decisions to the action. A policy allow decision alone does not prove an operation executed.
What must an evaluation prove?
Test out-of-scope requests, missing approval, changed targets, duplicate attempts and ambiguous results. Identify where enforcement occurs and which records survive failure. Standards references are evaluation context, not a certification or agency endorsement.
