System Audits can be as simple or custom as you need. They can replace the need for traditional introspection tools if designed into your extensions properly.
A Use this tag when logging a generic audit block
E Use this tag when logging an `event` block as described in the standard EntityScript™ library
S Use this tag when logging a `search` block
P Use this tag when logging and identifying a parsed behavior
K Use this tag when logging and identifying a new `main` or `active` function call
System Audits: Extended file auto-checks
The main .CORE/ directory performs very little. It does however perform audit_home checks. Essentially, it looks for a status queue. If the queue exists the system starts and stays running. If it doesn't exist it can start but won't run.
.audit_home/STATUS.X will tell the operator and the machine upon startup that the system and all tracked/known files from the last session are still there and in working order. The goal is to take anything that makes this hit to '.ERROR' and to isolate it for later processing.
This folder will produce the following file if everything is okay:
produce in-> .CORE/
If there was a syncing error or startup problem, the following will be true.
You can check out more about generating manual scripting-based processes and extending system audits with packages available through the implementation language: Scripting