Plugin Internal Lifecycle

The plugin operates in a continuous internal cycle governed by engine.min-evaluation-interval-ms. Each cycle passes through the following phases:

Phase	Description
Observation	The Eye polls all enabled server domains — entities, chunks, players, mechanics, network and others — and builds a snapshot of the server state at that instant. Each domain is updated according to its configured sampling interval.
Analysis	Nine independent sub-engines each evaluate the snapshot against their domain. Sub-engines cover areas such as entity management, chunk pressure, redstone load, player quality of service and network health. Each one produces zero or more prioritized action proposals.
Orchestration	All proposals are scored, deduplicated and filtered against safety constraints, cooldown timers, circuit breaker state and resource usage limits. The highest-scoring proposals that pass all filters are selected for execution.
Execution	Selected actions are dispatched to the corresponding platform executor. Paper and Folia have separate execution paths to guarantee the correct thread context on each platform.
Feedback	Results are recorded in the action history. Effectiveness metrics and adaptive control parameters are updated. Auto-revert timers are started for reversible actions.

Note: The specific scoring algorithm, each sub-engine's domain boundaries and internal feedback mechanisms are proprietary. This description is sufficient for operational diagnostics and configuration tuning.