Spark Intelligence Builder is the runtime core behind the Telegram gateway. In launch v1 it should not own the live Telegram bot token. It also owns the canonical governed tool-ledger table used for local authority observability.

• spark-telegram-bot owns Telegram long polling.
• Builder owns runtime state, provider profiles, memory bridge behavior, adapter logic, and domain-chip activation.
• Builder may receive Telegram-shaped updates through the bridge, but it should not start a competing Telegram receiver for the same bot token.
• Cloud provider secrets should be configured through Builder auth commands or Spark CLI secret storage, not committed env files.
• High-agency tool calls must be backed by Harness Core authority records and a bound ledger row; ledger ingest is not an authorization API.

• .env, .env.*
• local config.yaml, state.db, logs, runtime homes, and generated artifacts containing user data
• Telegram bot tokens
• LLM API keys
• OAuth tokens or refresh tokens

Run:

python -m pytest tests/test_secret_file_permissions.py tests/test_gateway_discord_webhook.py -q
spark-intelligence doctor
spark-intelligence harness tool-ledgers --limit 5 --json

Before public demos, rotate any token that appeared in chat, logs, screenshots, or issue text.