tinysocs-config-and-flags

Look up the variable in the atlas section for its service: dashboard and bot vars in section 3.1, node and federation vars in 3.2, feed and licensing vars in 3.3. Each entry lists the default value, source file, and line number verified against the repository.

The agent silently falls back to all defaults when agent-config.yml is missing, leaving no inputs configured. Also check Detection.Pack.Enabled, which defaults to false, so the signed pack path never runs unless explicitly enabled in the deployed YAML.

node.py hard-fails with sys.exit(1) when MASTER_SHARED_SECRET is unset, printing a FATAL message to stderr. bot.py similarly fatal-exits when BOT_SHARED_SECRET or NODE_SECRET is missing, so all shared secrets must be set before startup.

No, the default is inconsistent across files: bot.py and master.py default to verification on, while check_ledger.py defaults to skipping verification. Several dashboard.py httpx calls hardcode verify=False unconditionally and ignore the env var entirely.

When the tinysocs.agent.actions_queue module imports successfully, QUEUE_PATH is built from ACTIONS_QUEUE_PATH only and TINYSOCS_QUEUE_PATH is never read. Set ACTIONS_QUEUE_PATH instead, despite what the .env.example comment implies.

Do not use it for detection rule schema fields, installer and NSSM service mechanics, change-control decisions about flipping flags, or live symptom triage. Those belong to the detection-engineering, run-and-operate, change-control, and debugging-playbook skills respectively.