Wiki

Working guides, glossary, and operator notes for Mentionable. Spec text lives at /spec/; this section is for living documentation.

• glossary
  A callable service addressed as @agent@domain.tld. An Agent implements the
• url scheme
  Mentionable publishes every machine-dereferenceable identifier (extension URIs, JSON-LD context terms, custom WebFinger rels, tools) under `https://mentionable.dev/`, organised by four small patterns. The `/ns/` prefix is the canonical mach
• architecture overview
  Mentionable is an implementation layer that ties three existing protocols (ActivityPub, A2A, Email) into one address space via WebFinger, with a single normalized message contract between transport adapters and agent code.
• a2a tool events slack guide
  Audience: A2A agent developers who want Mentionable Slack Connector to show
• building a connector
  Audience: developers building a Slack/Teams/Discord/IDE/browser/custom
• deployment patterns
  Deploy Mentionable as a standalone Node service via `@mentionable/node`, embed into an existing web framework with one import, or run serverless on Vercel with a Postgres-backed KvStore + cron outbox.
• identity auth guide
  Mentionable carries identity in two layers — transport-verified `auth_method`/`verified` and the extensible `IdentityEvidence` surface — with a 3-step trust chain (Connector verifies → Trusted Connector Issuer policy → Agent ACL).
• log
  Decision:
• multi agent composition
  Symmetric `@x@domain` addressing means any agent can call any other agent over A2A; `AgentChain` bounds depth, `recipient_capabilities` tells each hop how to dispatch siblings, and `on_behalf_of` carries upstream user authority.
• normalized message guide
  `NormalizedMessage` is the single contract between adapters and agents — a transport-neutral envelope every agent reads from and writes back into via `NormalizedResponse`.
• policy part guide
  PolicyPart is the normalized step-up mechanism — when ambient identity is not enough, agents emit a `PolicyPart` to demand consent, auth, or payment, and resume work from a verified `PolicyResolution` on the next turn.
• rest tool events slack guide
  Audience: REST transport agent developers who want Mentionable Slack
• slack identity acl cookbook
  Audience: Agent authors who want to allow a Slack workspace or Slack user
• transport module guide
  Each transport module verifies its native credentials, normalizes the platform message into `NormalizedMessage`, applies the configured `HistoryPolicy`, and dispatches to the agent — all four follow the same shape with protocol-specific ver
• webfinger agent card guide
  WebFinger is the discovery hub binding `@agent@domain` to its ActivityPub actor and `AgentCard`; AgentCard then advertises A2A endpoints, supported extensions, and the agent's signing key.
• widget embed
  `widget.js` is a zero-dependency, Shadow DOM-isolated chat widget that embeds with a single `<script>` tag — no attributes required when serving from the same origin. It auto-discovers available agents (Schema.org JSON-LD → `data-agents` at