THE FIELD GUIDE / OPERATIONS
Deployment discovery & dependency-aware self-patching
Discover the infrastructure Mr Patchy depends on and review a maintenance sequence that preserves service.
Read the topology before making a plan
Correlate controller, worker and integration identities with enrolled hosts, guests, containers and backing failure domains. Include shared dependencies such as MySQL, storage, DNS, ingress, identity and cloud transports where evidence supports the link. Each edge carries source, freshness and confidence. Unmapped or stale dependencies are visible.
Review the maintenance order
Preview the exact hosts, dependencies and transactions alongside backup, recovery, capacity and availability gates. Co-located components count toward the same failure domain. If work removes the only controller, ingress or database path, the plan exposes the blocker and required recovery or external maintenance path.
Hand off and verify each step
Drain eligible roles, transfer ownership, patch under the authorized maintenance policy and verify the host and application before rejoining. If topology or transaction evidence changes, obtain a fresh review. An uncertain outcome stops dependent work until reconciliation.
Open the application reference for capability scope and technical details.
Open View scope in issue #444 ↗