Sentinel — current development and permission boundaries
The inspected private development package is 0.1.0-beta.75. Use the existing detailed Sentinel chapters for configuration and recovery; do not publish its source or infer production readiness from a version number. Installation/activation uses the normal addon package controls and legitimate entitlement, not a hardcoded owner bypass.
Review each enabled protection with a normal member, staff account and the real owner before relying on it. Keep recovery/allowance controls reachable to the owner. Core/service integration and real hosting acceptance are separate gates; a setting being present or a fixture passing is not proof that an external service executed successfully. Source updates do not authorize destructive production actions.
Record the actual enabled modules, false-positive evidence and corresponding audit trail before changing thresholds. Preserve the data/identity on update and use a verified backup for recovery rather than uninstalling live protections.
