Model Server (model-server/)
Architecture, pipelines, workers, configuration, and ownership guidance for the model server.
Model Server (model-server/)
This area documents the model-server/ repository. It is Marsad's Flask service for analysis pipelines, social-platform collection, generated reports, and background processing.
Use these pages when changing code owned by the service: Flask request handling, provider and collector integrations, RQ workers, generated artifacts, and callback delivery. They complement, rather than repeat, the shared System Architecture and Cross-Repository Contracts.
The Model Server accepts work from the Web App, executes it asynchronously, and reports its outcome back to the Web App. It does not own browser-facing workflows, Web App database records, or user authorization decisions.
Architecture
Repository responsibilities and technical boundaries.
Pipelines & Workers
Analysis, collection, reporting, queues, and worker behavior.
Development & Configuration
Local commands, setup, and configuration ownership.
Integration Boundaries
The Model Server's contracts with the Web App and shared infrastructure.
Contributing
Change scope, validation, and documentation expectations.
Reading guide
Start with Architecture to understand the repository's boundaries. Use Pipelines & Workers before changing asynchronous work, and Integration Boundaries whenever a change crosses into the Web App, Redis, or shared storage. Development & Configuration covers a safe local runtime; Contributing gives the change and validation checklist.
For user-facing product behavior, start in Product. For a contract shared with another repository, start in System.