diff --git a/Data/Engine/CURRENT_STAGE.md b/Data/Engine/CURRENT_STAGE.md
index 30cf14b..043d18b 100644
--- a/Data/Engine/CURRENT_STAGE.md
+++ b/Data/Engine/CURRENT_STAGE.md
@@ -60,10 +60,8 @@
 - 11.3 Commit after integration tests (or mocked unit tests) confirm API workflows.
 
 [IN PROGRESS] 12. Final parity verification
-- 12.1 Follow the staging playbook in `Data/Engine/STAGING_GUIDE.md` to stand up the Engine end-to-end and exercise enrollment,
-  token refresh, agent connections, GitHub integration, and scheduler flows.
+- 12.1 Follow the staging playbook in `Data/Engine/STAGING_GUIDE.md` to stand up the Engine end-to-end and exercise enrollment, token refresh, agent connections, GitHub integration, and scheduler flows.
 - 12.2 Record any divergences in the staging guide’s table and address them with follow-up commits before cut-over.
-- 12.3 Once parity is confirmed, coordinate entrypoint switching (point deployment at `Data/Engine/bootstrapper.py`) and plan
-  the legacy server deprecation.
-- Supporting documentation and unit tests live in `Data/Engine/README.md`, `Data/Engine/STAGING_GUIDE.md`, and
-  `Data/Engine/tests/` to guide the remaining staging work.
+- 12.3 Once parity is confirmed, coordinate entrypoint switching (point deployment at `Data/Engine/bootstrapper.py`) and plan the legacy server deprecation.
+- Supporting documentation and unit tests live in `Data/Engine/README.md`, `Data/Engine/STAGING_GUIDE.md`, and `Data/Engine/tests/` to guide the remaining staging work.
+- Engine deployment now installs dependencies via `Data/Engine/requirements.txt` so parity runs include Flask, Socket.IO, and security packages.
diff --git a/Data/Engine/README.md b/Data/Engine/README.md
index 1b9d433..266459c 100644
--- a/Data/Engine/README.md
+++ b/Data/Engine/README.md
@@ -65,6 +65,10 @@ The Engine mirrors the legacy defaults so it can boot without additional configu
 
 As migration continues, services, repositories, interfaces, and integrations will live under their respective subpackages while maintaining isolation from the legacy server.
 
+## Python dependencies
+
+`Data/Engine/requirements.txt` mirrors the minimal runtime stack (Flask, Flask-SocketIO, CORS, requests, PyJWT, and cryptography) needed by the Engine entrypoint.  The PowerShell launcher consumes this file when preparing the `Engine/` virtual environment so parity tests always run against an environment with the expected web and security packages preinstalled.
+
 ## HTTP interfaces
 
 The Engine now exposes working HTTP routes alongside the remaining scaffolding:
diff --git a/Data/Engine/requirements.txt b/Data/Engine/requirements.txt
new file mode 100644
index 0000000..6f7693c
--- /dev/null
+++ b/Data/Engine/requirements.txt
@@ -0,0 +1,11 @@
+#////////// PROJECT FILE SEPARATION LINE ////////// CODE AFTER THIS LINE ARE FROM: <ProjectRoot>/Data/Engine/requirements.txt
+# Core web stack
+Flask
+flask_socketio
+flask-cors
+eventlet
+requests
+
+# Auth & security
+PyJWT[crypto]
+cryptography