# pulse-bridge configuration. Environment variables override these.
PULSE_BRIDGE_POLL_SEC=30
PULSE_BRIDGE_MIB_BASE=http://127.0.0.1:5520
# Nirlab Command Center (founder workspace) — where the Pulse/Activity feed lives
PULSE_BRIDGE_WORKSPACE_ID=293d29db-4978-4c54-a92e-b24d4c0a7115
PULSE_BRIDGE_CHANNEL=activity
# handle used in "@… NEEDS YOU:" escalation comments. Must be the lower(name)
# of an ACTIVE member of the workspace above — mib007 resolves user mentions by
# lower(u.name) over workspace_memberships. "nir" does not resolve here (the
# only human members are Board/local-board and RapidNir/rapidnir-admin), so we
# mention RapidNir — Nir's account in the Nirlab Command Center workspace.
PULSE_BRIDGE_MENTION=rapidnir
PULSE_BRIDGE_POSTER_NAME=Ledger
PULSE_BRIDGE_SHRE_ITEMS=/Users/aibot/.local/bin/shre-items
PULSE_BRIDGE_STATE=/Users/aibot/.shre/pulse-bridge/state.json
# mib007 service token (board-level, loopback): file + key
PULSE_BRIDGE_TOKEN_FILE=/Users/aibot/.shre/service-tokens.json
PULSE_BRIDGE_TOKEN_KEY=mib007
# Reverse intake: user posts in the activity channel become ledger items +
# kanban tasks executed by the Hermes dispatcher
PULSE_BRIDGE_INTAKE=1
PULSE_BRIDGE_INTAKE_MAX_CONCURRENT=3
PULSE_BRIDGE_HERMES_DIR=/Users/aibot/.hermes/hermes-agent
PULSE_BRIDGE_HERMES_HOME=/Users/aibot/.hermes
# Outbound mirror: live ledger add events -> Dash Kanban triage cards. Seeded
# historic/open items still mirror only to Pulse posts.
PULSE_BRIDGE_KANBAN_MIRROR=1
PULSE_BRIDGE_KANBAN_KINDS=needs-you,failed,pipeline,gap
PULSE_BRIDGE_KANBAN_TRIAGE=1
PULSE_BRIDGE_KANBAN_INITIAL_STATUS=
PULSE_BRIDGE_DASH_AGENT=dash-agent
# comma-separated user_names never ingested (bridge + agent accounts)
PULSE_BRIDGE_INTAKE_IGNORE=Ledger,Ellie,AROS
# chat-only prefixes (case-insensitive): posts starting with one of these are
# never turned into work and get no bridge reply
PULSE_BRIDGE_INTAKE_OPTOUT=💬,chat: