Home / Product / Features and Vision
Updated Jun 20, 2026 · Affirmology_Hermes_CommandCenter_CapabilityMap_v1.md
Jeff's north star, 2026-06-20: "The chat should be a place of epic delivery and interaction, a cheat code superhighway into all of our systems. At least for me; Sol and Colin's accounts should have a few limitations."
So Hermes is not a chatbot bolted onto the product. Hermes IS the command layer over the whole platform. Every system should be reachable, and every output deliverable, from the chat. Jeff holds the full keyset. Sol and Colin get a governed version. This doc is the target the action-layer builds (C15/C16/C17 and beyond) all point at, and the permission contract every action checks.
One chat, every system. If a thing exists in Affirmology (a chart, a reading, an oracle, a timing read, an audio, a Studio entry, a report, a person's record, a system job), Hermes can reach it, act on it, and deliver the result inline, on the user's explicit request. The chat becomes the fastest path into everything, not a place you leave to go "do the real work."
| System | What Hermes can do | Status | Jeff | Sol / Colin |
|---|---|---|---|---|
| Readings / oracles | Pull charts, run the council, search corpus + craft | LIVE | full | full (own + circle) |
| Timing | Transits, progressions, significant-events timeline | engine live | full | full (own) |
| Field-briefing audio (C15) | Render a reading to audio, play inline, save + share | to build | full, uncapped | gated + hard monthly cap |
| Cross-chat messaging (C16) | Push a reading/report/audio to a circle member's chat | to build | full | within circle only |
| Send to Studio (C17) | Create a Studio draft from a chat script, render-ready | to build | full | own drafts only |
| Catalog / library | List, search, retrieve, re-share past readings + audios | planned | full | own + shared-to-them |
| Studio control | Set structure/length/bed, label demo-candidate, trigger render | planned | full (incl. render trigger) | propose, not trigger demo changes |
| Reports / system view | Growth morning report, corpus stats, test/change queue status | planned | full | read-only summaries |
| People / charts | Add a person, compute a chart from birth data | partial | full | self/circle only |
| Growth / feedback | Feed feedback, queue a test/change, see what changed | partial | full (incl. trigger a run) | submit feedback only |
| Admin / settings | Tiers, keys, settings, demo lock | n/a | full | none |
(Statuses: LIVE = working now; engine live = computed, surfacing via chat to broaden; to build = greenlit, brief written; planned = on the map, not yet specced.)
as_person. The UI may hide what a person can't do, but the server is the gate. Additive-only and user-initiated-only hold across the board (Hermes never acts on its own initiative; every side-effect is an explicit user request).