Autonomous Administrative System daemon version 2.

The main goal of the project is to create a modular platform supporting UNIX system administration tasks in the field of monitoring environmental parameters and process status as well as responding to incidents.

The active runtime is plugin-based and the daemon acts as a runtime host and execution supervisor.

The repository still contains archived historical material from the former module-oriented runtime, but that code is no longer part of the active execution path.

The current architecture is plugin-based:

• plugins are discovered from the directory configured as plugins_dir,
• each plugin directory or symlink is one plugin instance,
• each instance gets its own config section derived from the entry name,
• plugin type is declared by the plugin API, not by directory category,
• worker plugins emit messages through the dispatcher,
• worker-side notification timing is handled by shared plugin helpers, not by the daemon,
• communication plugins consume routed messages from configured channels.

Standalone plugins may keep their own tests, changelog, and operational documentation inside the mounted plugin repository. The local plugins/email/ repository is an example of that model.

The daemon must not assume direct plugin-to-plugin communication. Message routing is valid only when the user defines matching channel rules in the configuration file.

The legacy modules are preserved only as historical reference material under archive/.

The project is entirely written in python3 and runs in a dedicated virtual environment.

The main process is executed in the foreground and it is assumed that it will be supervised by a service manager such as "runit" or "daemontools".

The project is dedicated and tested on FreeBSD platforms, most of the plugins should work properly in the Linux environment.

Poetry is used only in development environments for dependency management, locking, testing, and documentation work.

Production and deployment environments should use requirements.txt as the runtime installation source:

pip install -r requirements.txt

requirements.txt is treated as the deployment artifact generated from the current Poetry runtime lock set for the active host runtime. Archived reference code under archive/ does not define deployment dependencies for the current daemon.

At first startup, or after the daemon discovers new configuration sections or options, AASd writes the missing defaults to the config file, logs an operator review notice, and exits cleanly. Runtime startup resumes only after the operator reviews the updated configuration and launches the daemon again.

During load() and reload(), the daemon also validates known plugin schedule fields such as message_channel and at_channel and emits warning logs for unsupported or suspicious values before plugin startup begins.

1. Installation
2. Archived Modules
3. Flow Diagram
4. Architecture Analysis
5. Plugin API v1
6. Plugin Migration Status
7. Business Logic API

The repository now includes a Sphinx-based documentation toolchain with MyST Markdown support. This is a development workflow and assumes Poetry is available in the local development environment.

make docs

Generated HTML output is written to docs/_build/html/.