Technical debt is the future cost created by expedient decisions. Agent-generated duplication, unnecessary dependencies and undocumented abstractions can accumulate debt unusually quickly.
Documentation and decision records explain how to use the system and why consequential decisions were made. Architecture decision records preserve context that code alone cannot express.
Collaboration and review depend on shared standards, code review, issue tracking, ownership and constructive challenge. Human review should focus on risk and system intent, not only formatting.
