The ecosystem

needs verification

The mobile app captures a researcher's explanation. lt-core owns identity and workflow. The Media Processing Engine (MPE) produces playable media. Strapi owns the published content model; the Hugo website builds public pages from it.

Solid app-to-core and web-to-Strapi arrows are the confirmed segments in the integration baseline. Dotted arrows preserve its business-target classification. Newer core code implements processing requests, callbacks and website payload projection, but that alone does not prove the complete production MPE-to-CMS handoff.

The request path from phone to website

Large uploads go directly to object storage; lt-core issues and completes their control requests. Finished media uses Cloudflare R2. Website configuration is embedded in the page, while the core Video API requires authenticated mobile-domain access.

For the steps and the remaining publication boundary, read How a video gets published.

For maintainers: source references

These references require repository access. Everything needed to understand this page is explained above.

• integration baseline
• upload API
• processing integration
• website player adapter