Fix Chaotic Microservices Architecture by Documenting Before Rewriting

A software architect working on a growing gamedev project with roughly twenty services argues that architectural disorder is best addressed through documentation rather than rewrites. The project's services evolved organically without deliberate design, leaving decisions scattered across chat logs and individual memory, causing incidents and ballooning estimates. The proposed first step is a one-page 'service passport' for each service, capturing its purpose, responsibilities, stack, owner, and operational details. These passports are maintained by service owners, updated alongside code changes, and kept brief to avoid becoming abandoned wiki pages. Aggregated into a registry and a plain-text call graph stored in version control, they create a living map that exposes real boundaries, orphaned services, and integration risks before they cause costly failures.