Hermes landing pad: dialogue-first community entry with memory graph panels

Landing Pad

Dialogue, not just delivery

Hermes-powered entry points for communities entering the Overweb estate.

Hermes Landing Pad

A landing page is usually a one-way brochure. A landing pad is built for dialogue. Over time it can learn from a visitor's choices, suggest how their perspective might be read, and invite them to refine that capture until it reflects what they actually mean.

I design and deploy Hermes landing pads for communities, institutions, and builders who need a trustworthy front door into the Meta-Layer estate: Gov Hub governance, Desirable Properties, Overweb Studio substrate work, or BRC333 immortalization paths.

Product-honest learning

How a landing pad learns

Learn

Session memory, confirms, and chosen sources. Not silent profiling. Visitors stay in control of what becomes part of the record.

Suppositions

Working hypotheses until the visitor confirms sources, mappings, or text. Hermes proposes; people approve or correct.

Refine

Correct us, add sources, patch text, or update consent. The pad improves as the community teaches it what matters.

Route

Estate-aware routing sends builders to Overweb Studio, stewards to Gov Hub, and immortalizers to BRC333 Studio without one generic chatbot answer.

Estate context

From pad to estate

Hermes already spans Desirable Properties, the Metaweb book, and partial Gov Hub context. Landing pads extend that into a routed entry surface for the full Meta-Layer estate:

  • Org pads at /pad/{slug}: public corpus briefing, Desirable Properties invite, community chat
  • Person pads for stewards and builders who need a consent-first profile surface
  • Domain routing: DP norms, Gov Hub ML-REQ/ML-ADR, Overweb substrate, BRC333 immortalization
  • Sandbox first: new domains and pads can ship in dev before production chat

This is the same Hermes architecture discussed for extending estate coverage: one chat surface, separate retrieval domains, clear citations, and human governance in the loop. See also Community AI (Hermes) for the full agent product.

Engagement

What I build with you

Pad design and corpus

Define what the pad knows from public sources, what requires confirmation, and how visitors enter your governance stack.

Hermes integration

Memory graph, contributions, Discuss hooks, and teach/share/watch/control flows scoped to your community.

Estate routing

Connect the pad to Gov Hub workgroups, Overweb Studio sandbox paths, or BRC333 publishing when those are the right next step.

Launch and stewardship

Pilot with a cohort, measure what visitors actually use, and refine language and practices from live dialogue.

Next steps

Build your community's landing pad