Operational Checklist

Operational Checklist

Verification boundary: This page combines platform design guidance with static evidence from the release. It does not prove that every detected interface is enabled, reachable, secure, or operational in the deployed environment.

Daily/shift-start checks

• System time synchronized and no large clock offset alerts.
• Required services active without restart loops.
• Disk, memory, CPU and network within operating limits.
• Public hostnames and local health endpoints respond correctly.
• OpenBus/data/knowledge/files dependencies reachable.
• Representative sensor/track/task workflow completes.
• Backups completed and no unresolved critical security/audit alerts.

After any change

• Configuration syntax validated.
• Only intended service/process changed.
• Local, proxy and end-to-end tests passed.
• Logs reviewed for new warnings/errors.
• Version/change record and rollback state updated.

Handover record

Record active release, known degradations, temporary workarounds, open incidents, pending changes, sensor availability, external dependency state and the next required action. Operational continuity should not depend on oral memory.

Maintainer Notes

Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.