# Why check ArchiMate repositories? ArchiMate is a graphical language and was developed for IT-architects who want to visualize ideas about the business, the application landscape, the infrastructure, and the strategic concerns of enterprises. Architects can store their models in what we call a repository (i.e. a mechanism to store models). A problem arises when a repository contains many models. Oversight is lost, models get incomplete, and inconsistencies occur. To a certain extent ArchiMate helps to prevent this by sharing objects between models. But organization-specific constraints cannot and may not be enforced by a generic tool. ArchiChecker is a tool that lets architects formulate and check organization-specific constraints on their ArchiMate repository. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ampersandtarski.gitbook.io/signals-from-archimate/master.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.