video1.0<iframe src="https://www.loom.com/embed/448b5d54c099460e80fc18191dcb3eaf" frameborder="0" width="2088" height="1566" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>15662088Loomhttps://www.loom.com15662088https://cdn.loom.com/sessions/thumbnails/448b5d54c099460e80fc18191dcb3eaf-8619bc590413f971.gif82.456556In this video, Chris Chedgey discusses the three main concepts of our architecture capability. First, he explains the current architecture, which is automatically generated during sonar analysis and serves as a live documentation of our application's component hierarchy. Second, he highlights the intended architecture, which helps us determine the essential components and their relationships. Lastly, he addresses how deviations between the current and intended architecture are reported, along with issues like tangles, which can impact our quality gates. We encourage you to engage with this information to ensure we maintain effective architectural oversight.