# ─────────────────────────────────────────────────────────────────────────
# WHAT BELONGS IN THIS FILE — and what does NOT
#
# This file is for the DEPLOYMENT'S OWN identity and its model keys. That is
# all. Provider credentials do NOT live here.
#
#   HERE, in .env
#     LEAFMESH_LICENSE_KEY, LEAFMESH_ENV_TOKEN
#     the ports, REDIS_* / Postgres  (the store the vault itself lives in)
#     your model provider key(s): OPENAI_API_KEY / ANTHROPIC_API_KEY /
#       GOOGLE_API_KEY …  (these are read from the environment as the mesh
#       starts, so they must be here — the vault is read too late for them)
#
#   NOT HERE — in the VAULT, added on Studio's Infrastructure page
#     every channel credential  (Slack bot_token / signing_secret / app_token,
#       Teams, Discord, Cliq, WhatsApp, Email)
#     every connector credential (MCP, Zapier, Composio, n8n, custom)
#     Config then names it:  connection: "slack-workspace"
#
# Why it matters: since 2.4.180 the mesh REFUSES TO BOOT if it finds a
# provider credential written into config — and `${ENV_VAR}` does not help,
# because substitution happens before the check runs, so the check sees the
# token itself. `connection:` is the only path that works.
#
# Note: a value is EMPTY here, never a comment. `KEY=   # explanation` is read
# by python-dotenv as the COMMENT being the value.
# ─────────────────────────────────────────────────────────────────────────

# {{project_name}} — environment (template — copy to .env)
LEAFMESH_LICENSE_KEY=

OPENAI_API_KEY=
ANTHROPIC_API_KEY=

REDIS_HOST=localhost
REDIS_PORT=6379
REDIS_PASSWORD=

# Escalation channels
# PAGER_WEBHOOK + SLACK_MARKETING_CHANNEL are consumed by the manager's
# escalation block in configs/config.yaml (webhook + slack channel targets).
PAGER_WEBHOOK=
SLACK_MARKETING_CHANNEL=
# SLACK_BOT_TOKEN + SLACK_SIGNING_SECRET are NOT consumed anywhere yet.
# The escalation 'channel: slack' target needs a Slack adapter wired in
# code/connector to actually post (these tokens are read by that adapter).
# Set them only after you wire the adapter — they are not plug-and-play.
SLACK_BOT_TOKEN=
SLACK_SIGNING_SECRET=

# Connector webhooks (n8n workflows fronting YOUR systems)
# Analytics platform (GA4 / Amplitude / Looker) — marketing_analytics_agent
N8N_MARKETING_ANALYTICS_WEBHOOK_URL=
# MAP (Marketo / HubSpot) weekly campaign sweep — campaign_orchestrator_agent
N8N_CAMPAIGN_ORCHESTRATOR_WEBHOOK_URL=

LEAFMESH_ENV_TOKEN=development
