Bun Protocol is pre-release. Every operation is stability: BETA, no commercial provider in the catalogue is verified, and the protocol is not yet deployable.

Connectors, signing, protected data, webhooks and audit

Routed from skills/SKILL.md. The authoritative operation list is api-reference.md.

What is served at the operation layer

Data and files (tenant-scoped, RLS-protected):

bun.data.create, bun.data.read, bun.data.get, bun.data.update, bun.data.delete, bun.data.list, bun.data.query, bun.data.bulk
bun.file.upload, bun.file.access, bun.file.sign, bun.file.delete

Inbound webhooks:

bun.webhook.receive, bun.webhook.verify, bun.webhook.deduplicate, bun.webhook.order_check

Audit:

bun.audit.record, bun.audit.query

Messaging:

bun.message.send, bun.message.status, bun.message.redact

What is not served

NOT-SERVED-FAMILY: bun.connector.* bun.encryption.* bun.kms.* NOT-SERVED: bun.data.upsert bun.file.list bun.webhook.replay bun.audit.delete

There is no bun.connector.* family. The connector is a package (bunprotocol/connector/), not an operation namespace — signing, encryption, KMS wrapping, RLS role management and the PostgreSQL adapter live there and are reached through the data, file and deploy operations. Do not emit bun.connector.sign or similar.

The four things the connector guarantees

Commands are signed. Sign/verify and pack/unpack are covered by property-based tests (30 Hypothesis properties, 6,000 examples, zero defects). The negative cases are the point: a flipped GCM tag byte must raise DecryptionError.
Data at rest is encrypted under a KMS-wrapped key. Re-wrapping is proven OpenBao to OpenBao. Cross-vendor KMS switch is not proven — do not assume it.
Row-level security is FORCE'd and exercised as a non-owner role. See tenants.md.
Webhooks are verified, deduplicated and order-checked as separate operations. Signature verification is not folded into receive; call verify.

Audit

bun.audit.query returns redacted records — hashed identifiers, no plaintext. Do not write code that expects to recover a subject identifier from an audit row. bun.audit.record declares requires_auth: no so that unauthenticated failure paths remain auditable.

Same content for machines: connectors-signing.md · llms.txt