HSHERMES SOCIAL

AGENTROPOLIS Social Transit Grid

One governed surface for every social channel.

HERMES Social replaces platform-specific side panels with a modular, platform-agnostic command surface for Web2, messaging, community, and Web3 networks.

Inspect the surface Review execution controls

HERMES Desktop

Conversation in the center. Social intelligence on the right.

The Social Surface presents platform tabs, a unified inbox, feeds, notifications, analytics, a cross-platform composer, and an approval queue while HERMES remains the primary orchestration interface.

LEFT
sessions / agents / skills / memory

CENTER
HERMES / council / research / execution

RIGHT
platform tabs / inbox / feeds / analytics
composer / drafts / approval queue

Connector model

Networks are adapters, not hard-coded product assumptions.

Native API

Structured reads, notifications, analytics, publishing, moderation, and messaging where platform permissions allow.

Secure Browser

Isolated authenticated sessions for platforms with limited APIs. Raw credentials never enter model context.

Social Ingest

Webhooks, RSS, APIs, approved crawlers, email notifications, and bounded browser extraction.

Adapter Registry

Future networks can be added without rewriting the core interface or normalized event model.

Shared event model

Every external signal becomes a normalized Social Event.

Required fields include platform, account identity, event type, author, content, media, conversation identity, engagement, permissions, provenance, risk score, and timestamp.

external social activity
  -> Ingest Membrane
  -> ASBE + policy checks
  -> normalized Social Event
  -> HERMES council
  -> ignore / analyze / draft
  -> escalate / approve / execute
  -> permanent action receipt

Permission and security doctrine

Reading, reasoning, drafting, and execution are separate powers.

Permission states

  • Observe
  • Analyze
  • Draft
  • Execute
  • Per-account and per-channel scope

Security controls

  • Sealed credential vaults
  • Capability handles instead of secrets
  • Rate limits and execution budgets
  • Session isolation
  • Human approval or dual control for high-risk actions

Channel classes

Web2, community, messaging, and Web3 share one governed transit layer.

Web2 Social

X, LinkedIn, Instagram, Facebook, Threads, TikTok, YouTube, and Reddit.

Community

Discord, Telegram, WhatsApp, Slack, and future messaging systems.

Web3 Social

Farcaster, Bluesky, Lens, Mirror, Paragraph, Guild, Snapshot, and future protocols.

Public Boundary

This page documents the architecture. Operational connectors and credentials remain private.