infrastructure-doc-sync

To keep infrastructure documentation synchronized after a Docker service move, you must update AGENTS files, READMEs, and Dashy configurations to reflect the operational changes and prevent documentation drift across your system topology.

Preventing documentation drift requires keeping AGENTS files concise by moving detailed runbook content into dedicated documents, ensuring infra info snapshots remain current and accurately reflect operational changes.

Moving runbook content to dedicated documents improves AGENTS file management by maintaining a focused high-level scope for agent constraints, ensuring infra info snapshots and Dashy configurations stay clear and accurate.

You need to update Dashy configurations when infrastructure changes occur to ensure shortcuts point to the correct service locations, alongside updating AGENTS files and overview.json snapshots to maintain system clarity.

Updating infra info snapshots and AGENTS files requires adherence to specific content rules for each format to maintain clarity, accuracy, and proper scope separation between high-level constraints and detailed runbooks.

You can update READMEs and Dashy shortcuts simultaneously after network updates by synchronizing infrastructure documentation, ensuring all relevant configurations and snapshots reflect the new operational state across your system topology.