This document explains some core concepts The Guard relies on.
An action is a task that can be executed by a module. Task can be anything, for example setting redstone output or disabling some devices. Every module registers a set of actions that can be executed at any time. Each action can accept up to two parameters and be can stored by a module to be executed when certain event occurs. Actions are like building blocks that allow users to control application behavior.
For example, each keypad can define up to 3 actions that will be executed when it's used. Enable actions will be executed immediately and disable actions, in this case, after 3 seconds:
The Guard comes with modular architecture. A module is a file that provides some functionality to The Guard. Modules are independent of each other - they communicate via actions.
List of official modules:
levels - security levels and alarms
io - support for Redstone I/O blocks (input, output, bundled cables from ProjectRed)
auth - user authorization (keypads, biometric scanners and card readers)