I will build an HR automation agent using hermes

Building an HR Automation System with Hermes + Obsidian + Slack

• Stack: Hermes Agent (reasoning), Obsidian (markdown + YAML data layer), Slack (approvals), n8n (glue)
• Why Obsidian: human-readable, git-trackable files; folder structure acts as the schema, no database needed
• Two-vault split: Vault A (roles, PTO, org chart, onboarding) is open to the agent; Vault B (comp, SSNs, disciplinary) is access-gated
• Vault B writes require: a scoped tool call, Slack approval from an authorized human, and a logged reason
• Onboarding: Hermes drafts a checklist, manager approves in Slack, record saves to Vault A, n8n triggers accounts and equipment
• PTO: employee asks in Slack, agent checks balance, manager approves, balance updates with a markdown audit trail
• Why Slack: no learning curve, native approval gates, timestamped decisions, no frontend to build
• Templates: standardized schemas (employee, onboarding, PTO, role, disciplinary) keep agent reasoning reliable
• Lessons: build the two-vault split first, gate every write behind human approval, markdown scales further than expected
• Bigger picture: the pattern works for any agent operating over structured knowledge with human oversight