Operational note

Operational approach

Modular architecture, document throughput and more precise debugging.

The separation between public site, application API and engine stems from a practical need: managing intense document loads without degrading user experience and security.

The API governs authentication, tenant, logical state and access. The engine handles queue, workers and processing stages. This separation reduces coupling and makes problems easier to read when PDF volume grows.

The public side stays light: it presents the product, supports access and does not host pipeline logic. In this way every layer stays understandable and verifiable.