Release identity
SHA-256 of the pack file bytes: 75e6792b4bc7182ae1a19e375a02d7d655cd371322183f2540960581e685c51a
Distributable: digest matches the release manifest. The binary carries a digest-bound manifest of the distributable library; a pack whose bytes differ from its manifest entry — endpoint, tier, allowlist, or credential edited, with provider, version, and review block preserved — fails the digest check, loses distributability, and renders MODIFIED rather than as the shipped reviewed artifact. Review state and artifact status are different facts: the first is a documentation-review declaration, the second is the identity of the exact bytes.
Capabilities (5)
slack.conversations.list v1.0.0R0
- Action
- read
- Endpoint
GET https://slack.com/api/conversations.list- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-slack-bot-token- Data class
- internal
List the channels in the workspace the bot can see.
slack.conversations.history v1.0.0R0
- Action
- read
- Endpoint
GET https://slack.com/api/conversations.history- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-slack-bot-token- Data class
- pii
Read message history from one channel; messages routinely contain personal data, so the read is registered at the pii class.
slack.chat.postMessage v1.0.0R3
- Action
- send
- Endpoint
POST https://slack.com/api/chat.postMessage- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-slack-bot-token- Data class
- internal
Post a message to a channel. A message cannot be unsent, and send is one of the IRREVERSIBLE ACTIONS (delete, send, pay, deploy, approve, share and transfer), which is why it carries the R3 floor.
slack.files.share v1.0.0R3
- Action
- share
- Endpoint
POST https://slack.com/api/files.sharedPublicURL- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-slack-bot-token- Data class
- internal
Share a file beyond the workspace it was uploaded to. A share cannot be un-seen by whoever received it, and share is one of the IRREVERSIBLE ACTIONS, which is why it carries the R3 floor.
slack.reactions.add v1.0.0R2
- Action
- create
- Endpoint
POST https://slack.com/api/reactions.add- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-slack-bot-token- Data class
- internal
Add an emoji reaction to a message.
Credential reference
The pack names a reference, never a secret. Installing a pack registers capabilities and makes them governable; registration is not connectivity. The credential is created at the provider and held in the client's own secret manager under the reference the pack names, and deployment testing is still required to show the credential path works and cannot be bypassed.
- Reference
secret-ref-slack-bot-token- Custody
- customer_vault
- Injection
- header (Authorization)
A Slack bot token held in the client's own secret manager. The stored material must be the complete Authorization header value (scheme included), never just the token. AAES holds this reference and never the value. The bot scopes are a starting point: review them against the channels this workspace actually needs before enabling.
Resources
slack-workspace(channel, pii):slack://workspace/REPLACE-WITH-WORKSPACE-ID
Review record
Review completed: 2026-09-20 · Reviewer: aaes-eng (an opaque id that resolves internally to the responsible reviewer)
- https://docs.slack.dev/reference/methods/chat.postMessage (retrieved 2026-09-20)
- https://docs.slack.dev/reference/methods/conversations.history (retrieved 2026-09-20)
- https://docs.slack.dev/reference/methods/files.sharedPublicURL (retrieved 2026-09-20)
- https://docs.slack.dev/changelog (retrieved 2026-09-20)
A pack review is not a vendor or examiner attestation. A retrieval date says when a source page was read; it does not by itself establish what the page said then. No pack is vendor-endorsed, and none has been connectivity-tested against a live vendor tenant.