DavidGCalles/Back-Arquetipo

AI Summary: This Architectural Decision Record (ADR) addresses critical security and operational issues within the `back-arquetipo` application, aiming for alignment with 12-Factor App principles for Cloud Run. It seeks to eliminate insecure hardcoded defaults for sensitive credentials and prevent secrets from being baked into container images during the build process. Furthermore, the ADR aims to resolve race conditions caused by simultaneous database initialization across multiple instances in a serverless environment.

AI Summary: This issue aims to sanitize the application's configuration and environment by completely removing all remnants of the previously existing RPI hardware module. This involves deleting specific settings from `config.py`, removing conditional logic related to the module from `app/__init__.py` and `run.py`, and eliminating a corresponding test. The overall goal is to enforce a strict 12-factor configuration by cleaning up dead code and settings.

AI Summary: This issue aims to clean the application's persistence layer by removing all database access objects, schemas, and SQL definitions specifically related to Raspberry Pi hardware. The task involves deleting three RPi-specific files and removing their imports, followed by verifying that no RPi-related 'ghost tables' are created upon initialization.

AI Summary: This issue aims to remove the API endpoints and controllers responsible for Raspberry Pi hardware interaction. The task involves deleting specific RPi-related middleware files and removing their blueprint registrations to prevent the application from exposing hardware functionality.

AI Summary: The `back-arquetipo` repository currently functions as a hybrid monolith, combining cloud-native logic with low-level hardware control, which violates the Single Responsibility Principle. This architecture leads to instability and crashes when deployed in serverless environments like Google Cloud Run, as physical GPIO interfaces are absent. The decision aims to decouple these incompatible domains, ensuring the backend runs reliably in cloud environments without hardware dependencies.