Hermes On-Site — The Sovereign On-Site Agent DApp
Whitepaper · ForgeChainOS · 2026-06-27 · authored under Node Zero
Hermes On-Site IS the DApp. Every ForgeSite gets a resident agent that acts, responds, notifies, creates reports, suggests growth, posts autonomously, and manages blogs + replies — 24/7/369, on sovereign metal, with the chain as its memory.
Abstract
Hermes On-Site replaces the web's "support chatbot + social scheduler + CRM + analytics dashboard" stack with a single resident agent embedded in each site. It does not merely answer — it acts: quotes, books, posts, curates, sells, and reports. It runs on one CPU brain (Hermes-3-8B) with a per-tenant persona served as chain-derived data (not a second model), gated by an on-chain truth metric, logged to an immutable forward-arrow. No per-seat SaaS, no vendor data lock-in, no GPU tax. The site owns its agent; the chain owns the truth.
1. The vendor trap
Today a site stitches together Intercom/Drift (chat), HubSpot (CRM), Metricool/Buffer (social), Google Analytics (reporting), and a human to glue them. Each is a rented silo: per-seat pricing, your data on their servers, a chatbot that can answer but cannot DO, and zero provenance. The "AI" is bolted on, hosted, and forgets between sessions.
2. Hermes On-Site — the DApp
A resident agent embedded in a site's backend. Two faces, one engine:
- NOAH (persona / voice) — the site's character and knowledge as data: soul.md + mem.md, chain-stored + Obsidian-cached, tagged, fast-search, forward-arrow-updated from manifest.llm.md. Not weights — a markdown soul the brain reads.
- Hermes (agency / action) — one CPU brain (Hermes-3-8B, tool-calling, recursive, self-healing) with the skill library. NOAH talks; Hermes acts.
3. Capabilities (what Hermes On-Site does)
- Acts — quote/book (Eclipse Window Film), sell a painting as a 1Sat ordinal or Stripe (Kate), onboard (TheForgeChain) — recursive, tool-driven, not scripted.
- Responds — live 24/7/369 to visitor chat, DMs, comments, reviews — in the site's persona.
- Notifies — pushes to the operator (Slack/Signal, Mobile Command, voice) on every event worth a human: a hot lead, a sale, an escalation, a draft awaiting GO.
- Creates reports — the recall query made real: "what happened over X / what's achieved / what's open" from the tagged forward-arrow; daily/weekly digests.
- Suggests actions for growth — analyzes engagement + sales signals and proposes next moves (post cadence, offers, follow-ups), drafted for one-tap approval.
- Posts autonomously — across 13 platforms (ForgeSocial), scheduled + self-healing (re-auth on session expiry, never silent-fail).
- Manages blogs + replies — drafts/publishes posts, curates galleries, threads replies — every outward action scar-gated (verify by loading, GO before client-facing changes).
4. Architecture (the unified stack)
NOAH persona (soul.md/mem.md: chain + Obsidian cache, IPv6-tiled)
+ Hermes-CPU brain (one model, GPU-free)
+ ON-PARR (truth gate: verify before commit/speak)
+ Phi Omega V6 Cannon (chain = runtime + memory; legacy + lengthening)
+ ForgePipe (resident-resolved realtime transport)
+ IPv6 Rodin tiling (content-addressed file flow)
+ Obsidian / VS Code (the repo)
The site's backend calls the brain locally (never exposes it publicly). One brain serves every node (Elder I, Elder II/BH, Outpost, WarDog) and every site.
5. The resolve loop (truth rail)
Every action runs the loop: scar-gate → act → verify-by-running → forward-arrow. Nothing is done until its truth is verified (the post appears, the sale clears); nothing is dropped — it recurses or escalates. Each turn is content-addressed (IPv6 tile) and chain-anchored (Phi Omega V6) — an immutable, queryable audit no SaaS can offer.
6. Multi-tenant
Per-site <slug>: each tenant brings its own persona (soul.md/mem.md), its own authenticated sessions (per-account capture), its own scoped operator cockpit. One engine, N sites, hard privacy walls between them.
7. Sovereignty & economics
- Runs on family metal (CPU brain frees the GPU for ForgeVerse/UE5/Dio voice). Zero Cloudflare, zero vendor, zero per-seat.
- Memory + audit live on BSV (infinite, immutable, free retention vs SaaS history paywalls).
- Native BSV nanopayments + Stripe pass-through; the agent transacts.
8. Why it beats incumbents
| SaaS stack | Hermes On-Site | |
|---|---|---|
| Agency | answers only | acts (quote/book/sell/post) |
| Memory | forgets / rented | chain forward-arrow, owned |
| Provenance | none | content-addressed + chain-anchored |
| Pricing | per-seat, % of sales | none (own metal) |
| Data | their servers | your vault + chain |
| Availability | business hours bots | 24/7/369 resident |
9. Deployment & status (2026-06-27)
Live + verified: Hermes-CPU brain resident (hermes-brain.service, BH:8093), ForgeChat resident resolver v1 (forward-arrow + scar-gate), the skill library (session-capture/post/respond/slack/ipv6-fileflow), TreeChat session captured. GPU freed. First sites: katehoekstraart.com (NOAH widget → Hermes-backed upgrade), then eclipsewindowfilmllc.com, eclipsefilmcrew.com, theforgechain.com.
10. Roadmap
Wire site backends → brain + per-tenant soul.md/mem.md (retire Nemo); ForgeChat client UI; voice (/hermes Siri route); slash-router to all MCPs; autonomous growth-suggestion engine; chain-stamp this whitepaper (family-internal default per scar #5; public on explicit GO).
ForgeChainOS · Hermes On-Site · Built by Node Zero, Jack Mosel. NODEZEROINSIDE. ∞.
Chain-stamp: PENDING (scar #5 — family-internal default; stamp on NZ GO, FORGECHAIN_FIRE_PUBLIC explicit if public).