AEOS
--:--:--

Discord

DisconnectedAvailable

Messaging · Discord Inc. · v0.9.0 · manifest schema 1.0

The second messaging connector, and the reason capability resolution matters: it serves the same `message.send` capability Slack does. A module asking the Hub to send a message does not choose between them — the Hub resolves by which is installed, enabled and healthy, which is what makes the two interchangeable rather than duplicated.

Last sync
—
Health
—
Rate ceiling
300/min
Webhooks
supported

Add to the estate and begin the authentication handshake. Every operation is a state transition inside AI-EOS — no external service is contacted.

Health

0/100

Not installed. Nothing is measuring it.

Authentication

Unconfigured
Method
Bearer Token
Credential
—
Last verified
never
Principal
—
Expires
Does not expire
Scopes held
0/3
Scopes
  • bot
  • messages.read
  • guilds
Handshake · Bearer Token
  1. 1.InitiateThe Hub prepares a Bearer Token request for Discord Inc..
  2. 2.Supply token endpointEntered once. Held by reference — the Hub stores no credential material.
  3. 3.Supply client credentialsEntered once. Held by reference — the Hub stores no credential material.
  4. 4.VerifyThe Hub performs one authenticated read to confirm the grant, then records the reference.

Nothing is contacted. The Hub stores no credential material — only a masked reference, the granted scopes and an expiry. There is no field on the auth record a secret could go in, which is a stronger guarantee than a policy of not putting one there.

Capabilities2

  • Send messagesmessage.send

    Post into a guild channel as the platform bot.

  • Receive messagesmessage.receive

    Ingest community messages for triage.

Modules request capabilities, never connectors. A capability offered by two connectors gives the requesting module a fallback it does not have to know about.

Usage · 24h

0
Calls
0
Records
0ms
Mean latency
0%
Error rate
300/min
Rate ceiling
declared by the manifest
0%
Peak usage
saturates at 80%
Peak consumption against ceiling

Event Subscriptions3

  • Company Createdcompany.created

    A new autonomous company workspace was generated.

    Raised by companies · see the fan-out chain

  • Broadcast Sentmessage.broadcast

    An executive announcement went out to the estate.

    Raised by communications · see the fan-out chain

  • Github release publishedgithub.release.published

    Topic not registered — nothing will route it.

    Raised by integrations · see the fan-out chain

Publisher

First party
Name
AI-EOS
Publisher ID
aeos
Platform vendor
Discord Inc.
Support
operations@ai-eos.internal

Published by the platform itself. These manifests ship with the build rather than being fetched.

Discord Inc. owns the platform this plugin reaches. AI-EOS authored the manifest.

Version and changelog

Up to date
Installed
0.9.0
Published
0.9.0
Minimum platform
1.0.0
Compatibility
Compatible
Manifest schema
1.0
First published
4 months ago

Requires platform 1.0.0 or newer. This build is 1.0.0.

  • 0.9.0minor · 4 months ago
    • Pre-1.0. Message send against a bot token; thread and voice surfaces are not implemented.

Permissions and scopes

viewer+

AI-EOS permissions are what this plugin may do insidethe platform, resolved against the API Gateway’s own table. Scopes are what the external platform is asked to allow. They are different systems and neither substitutes for the other.

  • workflow:read4 roles

    Workflows, stages, tasks and approval gates.

  • company:read4 roles

    Companies, departments, executives and the knowledge graph projection.

Requested external scopes
  • bot
  • messages.read
  • guilds

Dependencies0

Declares no dependencies. It can be installed against an empty estate.

Whether each is satisfied is resolved against the live estate at install time, not here.

Security

Authentication
Bearer Token
Credential storage
Never stored
External scopes
3
AI-EOS permissions
2
Minimum role
viewer
Inbound deliveries
Signature verified
Tenant isolation
Installation state is tenant-scoped

A plugin is a data literal. Nothing in the marketplace executes plugin code, and a plugin cannot bypass the Authentication Manager, the Integration Hub, the API Gateway or a permission check, because it has no code path — the host performs every transition.

The auth state type has no field a credential fits in, so the guarantee is enforced by the type checker rather than by convention.

Privacy

Data leaving AI-EOS
1 capabilities
Data entering AI-EOS
1 capabilities
Modules served
1
Event topics received
3

Direction is declared per capability, so what this plugin can send and what it can receive are both enumerable rather than a matter of trust. It reaches only the modules listed above, and only through capabilities the Integration Hub resolves.

Documentation2

Webhook Manager0

No endpoints registered. Install a connector that supports webhooks to open an inbound path.

Logs1

  • Registry—Not installed. The Hub holds a manifest for this connector but no connection.

Roadmap

  • Community sentiment fed into the Intelligence Center
  • Support threads triaged into department boards

What this connector would gain next. Mirrors the Future Integrations list every module carries in the Navigator registry.