# Security The current application is a local research service. It has no live trading code, broker credentials, provider credentials, user authentication, or public deployment authorization. - `.env`, virtual environments, local artifacts, caches, and frontend build output are excluded from Git. - Secrets are loaded through a redacted boundary; logs redact secret-like field names. - The dashboard API is read-only and accepts no source code, shell commands, or filesystem paths. - Experiment IDs are constrained to safe identifiers and resolved under the configured artifact directory. - The API binds to `127.0.0.1` for local use. Do not expose it publicly without authentication, authorization, TLS, reverse-proxy policy, rate limits, and a database-backed audit model. - The raw archive contains market data and remains out of Git, Docker images, and frontend bundles. Future deployment must use distinct service identities, a secret manager, encrypted backups, dependency scanning, least-privilege filesystem access, and protected research-result storage.