Editing
Hanna
From H4KS
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
= Hanna = Hanna is the internal automation assistant used across H4KS to streamline workflows, coordinate tasks, and log important events. This page documents Hanna's purpose, architecture, usage, governance, and maintenance. == Overview == Hanna is a modular automation agent that integrates with IRC channels, project tooling, and bespoke workflows through a pluggable plugin architecture. It is designed to be privacy-conscious, auditable, and resilient. == Purpose and scope == * Automate repetitive tasks (notification routing, log aggregation, task creation) * Enforce standards and governance across channels * Provide quick access to information and open action items * Serve as a consistent interface for human operators and automated processes == Architecture == * Core engine: message parser, command dispatcher, plugin manager * Plugins: * IRC plugin: connects to #lobby and other channels * N8n adapter: triggers workflows via n8n * Logging: emits structured logs to central log store * Status: basic responsiveness and health checks * Data model: contexts per user/session, per-channel, per-workflow state * External interfaces: IRC, REST endpoints, Webhooks == Deployment and configuration == * Runs in containerized environment; uses environment variables for config * Config: /etc/hanna/config.yaml * Secrets handling: Vault or secret manager * Versioning: SemVer == Usage == * Basic commands: ** Hanna help ** Hanna status ** Hanna log <level> <message> * Examples: ** Listening to channel logs and summarizing nightly events ** Triggering a workflow in n8n via the N8n adapter * Access control and privacy: only authorized users can invoke admin commands == Security and privacy == * Authentication and authorization model, role-based access control * Data retention and deletion policies * Audit logging and tamper-evident records where feasible == Maintenance and governance == * Owners: Hanna team; primary maintainers include Valware and mattf * Change management: PRs, code reviews, tests, and staging reviews * Release cycle: monthly minor releases with quarterly major updates == Backup and disaster recovery == * Daily backups of critical state and logs; retention 30 days * Offsite replication and periodic DR drills * Runbooks and escalation paths for outages == History and changelog == * 1.0 initial release and stabilization * 1.1 added IRC connectivity defaults and improved logging * 1.2 introduced N8n node adapter and improved security checks == Related pages == * Hanna's Parents: Valware and mattf * Hanna LLC * Hanna Backup Procedures * N8n-nodes-hanna License * Mita and Hanna Collaboration * Debugging Bub Message in Mini Hanna Node
Summary:
Please note that all contributions to H4KS are considered to be released under the Creative Commons Attribution (see
H4KS:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Page actions
Page
Discussion
Read
Edit
History
Page actions
Page
Discussion
More
Tools
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Search
Tools
What links here
Related changes
Special pages
Page information