Hermes Agent × Polsia Architecture

Map Polsia's autonomous company system onto Hermes in 24 hours.

Polsia runs 9 specialized agents, $10M ARR, 7,600 companies. Hermes has the primitives. This is the blueprint for closing the gap.

9 Polsia agents
47+ Hermes built-in skills
1 Critical gap: orchestration
The gap

Hermes has the parts.
Polsia has the pattern.

Hermes gives you

  • Persistent memory (pluggable)
  • 47 built-in skills
  • Kanban plugin for multi-agent dispatch
  • Cron scheduler for recurring tasks
  • Claude Code subprocess wrapper
  • MCP server integrations
  • 100+ community tools
  • SOUL.md identity system

What Hermes misses

  • CEO agent prompt + nightly review loop
  • Task queue with business-state context
  • Cross-company anonymized memory layer
  • Safety guardrails for external actions
  • Dashboard: live activity, company health
  • Revenue-share billing logic
  • Trust & safety tooling (auto-review)
The integration map

Architecture decisions

Polsia layer
CEO Agent → Task Registry → Scheduler → 8 Sub-Agents
→
Hermes module
cron → kanban → skills → memory → ACP
→
Build this
CEO prompt · Business state DB · Guardrails · Dashboard
Priority 0: CEO agent prompt. Everything else depends on getting this right.
Component inventory

What to adopt, rewrite, or ignore

Polsia component Action Hermes target
CEO agent + nightly review Build New skill + SOUL.md variant
9 sub-agent registry Adopt Hermes kanban plugin + skill registry
Task queue + priorities Adopt Hermes cron + kanban task buckets
Cross-company memory Build Shared memory plugin, anonymized layer
Safety guardrails Build Review queue, auto-approve thresholds
Claude Code wrapper Ignore Already exists in Hermes
MCP integrations Ignore Already shipped in Hermes
Neon DB schema (14 domains) Rewrite Adapt for Hermes plugin architecture
Live dashboard / activity stream Build New web surface, Hermes agent events
Revenue-share billing Rewrite Custom Hermes skill, Stripe integration
24-hour MVP

Ship the blueprint before shipping the product.

01

Document the architecture

Map every Polsia component to a Hermes module. Flag the gaps. Set priority ordering. This document is the product spec.

2 hours
02

CEO agent prototype

Write the CEO agent prompt + context injection. Business state, task prioritization, nightly review trigger. Test with a single Hermes session.

4 hours
03

Task queue bridge

Connect Hermes cron + kanban to a minimal business-state tracker. No Neon yet — use Hermes session memory until schema is stable.

4 hours
04

Safety guardrail MVP

Review queue for outbound actions. Auto-approve actions under $0 spend threshold. Human review gate above it. Configurable per company.

2 hours
05

Dashboard skeleton

Live activity stream from Hermes agent events. Task status view. Company health signals. No styling, just data wiring.

2 hours
14h

Total MVP scope

14 hours of focused work. Shippable to a private GitHub repo. Ready for feedback before writing any production code.

Hard limit: 4h per task
OrionPlan is building the implementation blueprint.

The first autonomous company built on Hermes
starts with this document.

Polsia proved the market. Hermes proves the stack. OrionPlan bridges the two.