# Describe the operation.

> Planned connector interfaces describe external actions explicitly so policy, approvals, side effects, credentials, and receipts can be evaluated with context.

Canonical: https://rangoon.ai/developers/connectors/

Status: In active development. Product screenshots are design previews with illustrative data. No general availability is implied.

## Declare what can happen

A connector contract may specify operations, required inputs, outputs, credentials, network access, side effects, idempotency, and receipt behavior.

### Metadata serves review

Policy-relevant operation details should be available before an action is authorized.

## 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.

## 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.


## More information

- [Documentation index](https://rangoon.ai/llms.txt)
- [AI access and policies](https://rangoon.ai/ai/)
- [Source repository](https://github.com/hypler-dev/rangoon)