Metadata serves review
Policy-relevant operation details should be available before an action is authorized.
Connector SDK
Describe the operation.
Preserve the boundary.
Planned connector interfaces describe external actions explicitly so policy, approvals, side effects, credentials, and receipts can be evaluated with context.
Product direction · In active development
01
Declare what can happen
A connector contract may specify operations, required inputs, outputs, credentials, network access, side effects, idempotency, and receipt behavior.
02
Keep credentials separate
Connector installation, enablement, credential assignment, agent permission, and action authorization are intentionally different controls.
No ambient power
A connector should not turn a generic instruction into unbounded access.
03
Authority at execution time
Rangoon is designed to use LNSAT for consequential execution authorization and evidence.
SDK status
Connector contracts and SDK materials are planned, not released.
