NitWings starts with the live behavior, recent changes, logs, configuration, architecture, and operating history. The checklist follows the problem, not the other way around.
Delivery evidenceHeaders, DNS, authentication, provider responses, placement, complaints, bounces, reputation, and sending history.
Sender data and policyAudience source, suppression, consent, segmentation, warmup, frequency, compliance, and internal sender policy.
MTA behaviorQueues, retries, routes, concurrency, throttling, IP pools, bounce processing, feedback loops, and TLS.
Linux systemsServices, CPU, memory, disk, network, kernel, security, patches, logs, backup, capacity, and resilience.
Cloud architectureAccounts, subscriptions, projects, regions, networks, identity, compute, containers, data, security, and shared services.
Cloud operationsScaling, monitoring, logging, backup, recovery, governance, compliance, inventory, performance, and cost.
Delivery pipelinesSource control, builds, tests, artifacts, environments, approvals, releases, deployment methods, and rollback.
Infrastructure codeModules, state, configuration, secrets, drift, policy, repeatability, review, and change history.
Containers and platformsDocker, Kubernetes, managed services, networking, storage, scheduling, security, health, and capacity.
ObservabilityMetrics, logs, traces, dashboards, thresholds, alerts, ownership, escalation, and useful operating baselines.
Security controlsIAM, RBAC, secrets, vulnerability scanning, firewalls, patching, pipeline security, and audit evidence.
Operating readinessHigh availability, failover, disaster recovery, runbooks, incident response, root-cause analysis, and handover.