23 lines
1.3 KiB
Markdown
23 lines
1.3 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Production Service Runtime SHALL Use Conda-Aligned Execution Paths
|
|
Service units and operational scripts MUST run with a consistent conda-managed Python runtime.
|
|
|
|
#### Scenario: Service unit starts application
|
|
- **WHEN** systemd starts the dashboard service and watchdog
|
|
- **THEN** both processes MUST execute using the configured conda environment binaries and paths
|
|
|
|
### Requirement: Watchdog and Runtime Paths MUST Be Operationally Consistent
|
|
PID files, restart flag paths, state files, and worker control interfaces SHALL be consistent across scripts, environment variables, and systemd units.
|
|
|
|
#### Scenario: Watchdog handles restart flag
|
|
- **WHEN** a restart flag is written by admin control endpoints
|
|
- **THEN** watchdog MUST read the same configured path set and signal the correct Gunicorn master process
|
|
|
|
### Requirement: Deployment Documentation MUST Match Runtime Contract
|
|
Runbooks and deployment documentation MUST describe the same conda/systemd/watchdog contract used by the deployed system.
|
|
|
|
#### Scenario: Operator follows deployment runbook
|
|
- **WHEN** an operator performs deploy, health check, and rollback from documentation
|
|
- **THEN** documented commands and paths MUST work without requiring venv-specific assumptions
|