Governed Slack workspace connected to Hermes and approved knowledge sources. Project, automation, onboarding, approval, and runner channels with role boundaries, company-safe RAG, and human review gates.
Privacy-safe system map. Private records, identifiers, and workspace details are excluded.
System Summary
Built a Slack-based AI workspace where employees can request automations, find company knowledge, learn a role, approve work, and track runner status through a repeatable human-in-the-loop flow.
Business Problem
Company requests, knowledge, and approvals were scattered across DMs, threads, and documents, making it hard to find answers, track what was decided, or hand off work safely.
What Czar Studios Built
Workspace and channel architecture, scoped Slack app integrations, Hermes profile and gateway separation, company-safe retrieval with citations, channel operating rules, and approval gates before live actions.
Architecture and Data Flow
Slack is the employee interface; Hermes profiles act as operators and runners; approved knowledge sources hold reviewed company information; hybrid retrieval answers questions with source links. Each enabled channel has an allowlist, a behavior contract, and a clear responsibility boundary.
Integrations
Slack, Hermes, approved Obsidian and Google Drive sources, Qdrant, SQLite, and reviewed retrieval pipelines. Private areas remain outside the agent boundary.
Permissions, Guardrails, and Human Review
Per-app OAuth scopes, exact channel allowlists, role-based channel access, reviewer approval before any live action, and audit-ready workflow records.
Testing and Verification
Channel coverage, allowlist and behavior-contract parity, retrieval citations, and end-to-end employee request flows were verified.
Practical Outcome
Company knowledge became searchable from Slack with source citations, requests moved from chat into structured automation tickets, and approval gates kept consequential actions human-controlled.
Privacy-Safe Proof Notes
Architecture and channel-flow diagrams only; no workspace IDs, private channel names, employee names, or internal documents are exposed.