The database tables quantity, tenant, request, result, link quantity request, link quantity result, status log request and status log result depicted in Figure all have a uuid column as a primary key, and load time column time-stamping when the row is first appended to the table. This design, along with a backend logger, ensures traceability and reproducibility, which facilitates an exact tracing of the sequence of operations performed in the MAP at any point in time. The tables adhere to an append-only design, with only a few exceptions controlled through UPDATE interactions, e.g., for fields defining whether specific quantity and tenant entries are currently active in the MAP. A small expansion of the database schema allowing for a strict append-only design can be found in Figure SI-1, which will be implemented in the release of version 2.0.0. table relationships with the direction defining the origin of the primary key mapped to a table as a foreign key. Besides this schema, a separate single table database is used for user credentials.