The goal of this deliverable is to draw the largely complete picture of the Pr��t-��-LLOD software and language resource stack. Typical for a stack of single tools, the requirements expressed are manifold. The Requirements Document therefore concentrates on the specific requirements for the tools in Chapter ���3.1 Requirements by Function���. Overall requirements are mostly bound to three design paradigms: ��� Containerisation ��� API Communication ��� Linked Data Utilization (i) The use of Docker containers and Kubernetes facilitates the stack tools��� deployment and portability. One of the key concepts of the architecture is the use of containers to encapsulate all components, settings and libraries of an individual LT service in one self-contained unit. (ii) The OpenAPI specification, together with the Swagger UI provides a flexible communication on the basis of a widely used standard. (iii) JSON-LD allows data to be serialized in a way that is similar to traditional JSON. In order to map the JSON-LD syntax to RDF, JSON-LD allows values to be coerced to a specified type or to be tagged with a language. A context can be embedded directly in a JSON-LD document or put into a separate file and referenced from different documents. The frontend architecture is principally web-based. Beside the Swagger UI to directly interact with the APIs, more high-level UIs are in use on a tools level (and beyond): Teanga and Linghub (technically CKAN). Interfacing from other resources and to other stacks and platforms is to be done via interfaces mainly built on the design paradigms of Containerisation, API Communication and Linked Data Utilization