Standard Operating Procedure: Daily System Maintenance

1.0 Purpose

To define the mandatory procedures for daily system maintenance, self-healing, and autonomous agent verification. This ensures 100% uptime and data fidelity for the SigmaFidelity™ ecosystem.

2.0 Universal Mandates (2026 Baseline)

1. The Operator Charter: No maintenance task is complete without a Peter Sentinel snapshot.
2. Guidance First: If a "Zombie Process" persists after self-healing, ASK the CEO before manual termination.
3. Tier 6 Telemetry: Every maintenance cycle completion and system-health check must be logged to the Tactical DB.

3.0 Procedure

3.1 Mandatory Startup and Self-Healing

Every operational session must begin with the following sequence: 1. Execute Startup Master: bash scripts/startup_master.sh. 2. Verify Self-Healing: Ensure output reports "--- SigmaFidelity: Initiating Self-Healing Sequence ---".

3.2 Autonomous Agent Verification

Verify that the autonomous suite is running stably: 1. George Pulse: Check logs for "--- Sleeping for 6 hours (SigmaFidelity Standard Loop) ---". 2. Peter Sentinel: Confirm 15-minute shadow snapshot rhythm is active.

3.3 Database & Logic Integrity

1. Production Diagnostics: Run the diagnostic dashboard via the container: docker exec hwb_web_app python diag_dashboard.py
2. Telemetry Handshake: Verify new interactions are appearing in the SigmaInteractionLog.

3.4 Sovereign Disaster Recovery Appliance Maintenance (Drive D:\)

To ensure physical survivability during severe weather events across Texas (tornadoes, freezes, hurricanes):

1. Pre-Storm & Weekly Refresh: Connect Drive D:\ and execute D:\run-backup.ps1 from Windows PowerShell as Administrator.
2. Database Dump Verification: Confirm that fresh hwb_dev_db.dump (47.1 MB) and hex_dev_db.dump (21.2 MB) are generated in database_snapshots/.
3. 1-Click Integrity: Verify presence of restore-system.bat, restore-system.ps1, and emergency documentation on Drive D:\ root.

4.0 Verification (Zero-Defect Check)

• Docker containers (web, compliance, db, gateway) all show status "Running".
• Port 8000 (Gateway) is responding with 200 OK.
• System is approximately 12% more efficient via automated indexing (Maria's Audit).

5.0 Revision History