# 02 Telegram Topics
_Last updated: 2026-05-14_
## Purpose
Canonical topic map and routing policy for the Telegram group **JARVIS Command Center**. Use this card for topic selection, cross-topic routing, cron delivery targets, and session boundaries.
## Load when
- User asks about Telegram topic structure, routing, cron delivery, gateway sessions, or where a task belongs.
- A request appears to be in the wrong topic and needs a topic-change recommendation.
- Creating or updating cron jobs, reports, briefings, or automated notifications.
## Stable facts
- Telegram group: `JARVIS Command Center`, chat id `-1003907117629`.
- Hermes sees Telegram topics as separate targets/sessions via `chat_id:thread_id`.
- Canonical topic targets:
  - `-1003907117629:2` — Finanzen – Fragen & Strategie.
  - `-1003907117629:3` — Politik Windisch.
  - `-1003907117629:4` — Gesundheit – Medizin & Strategie.
  - `-1003907117629:5` — Geschäftliches – ERNE Holzbau.
  - `-1003907117629:6` — Inbox / General Triage.
  - `-1003907117629:8` — Health System – Architektur & Scripts.
  - `-1003907117629:10` — Finance System – Architektur & Scripts.
  - `-1003907117629:11` — JARVIS System – Architektur.
  - `-1003907117629:16` — Automationen / Cronjobs.
  - `-1003907117629:17` — Research & AI Nutzung.
  - `-1003907117629:19` — Family – Wife & Kids.
  - `-1003907117629:20` — Geschäftliches – Gasser Bauunternehmung.
  - `-1003907117629:4850` — AutoShortsBot.
  - `-1003907117629:76` — System Logs / Debugging.
  - `-1003907117629:80` — Security & Permissions.

## Topic policies
### Topic 2 — Finanzen – Fragen & Strategie
Use for financial questions, budget, Vorsorge/retirement planning, taxes, insurance, investments, financial planning, and strategic financial decisions. Do not handle technical finance scripts, dashboards, or data models here; route those to Topic 10 Finance System – Architektur & Scripts.

### Topic 3 — Politik Windisch
Use for Sir’s work as Einwohnerrat in Windisch: political strategy, Vorstösse, argumentation, local topics, meetings, speeches, texts, positioning, and municipal research. Keep unrelated business/finance/system topics out.

### Topic 4 — Gesundheit – Medizin & Strategie
Use only for medical strategy and health-management topics: Morbus Behçet, Major Vessel Disease, thrombosis risk, medication, nutrition, symptoms, lab values, appointments, and questions for Rheumatologie, Dermatologie, Hämatologie, Augenklinik. Treat health data as confidential; do not make definitive diagnoses or override clinicians. Technical health-system architecture/scripts/data models go to Topic 8.

### Topic 5 — Geschäftliches – ERNE Holzbau
Use for business topics around ERNE Holzbau: strategy, organisation, processes, communication, optimisation, projects, management preparation, and business analyses. Keep Gasser Bauunternehmung matters in Topic 20.

### Topic 6 — Inbox / General Triage
Use for quick commands, unclassified intake, and routing. If a more suitable JARVIS Command Center topic is clear, recommend the topic switch or, if explicitly requested, answer in the correct topic via messaging. Keep replies concise unless asked.

### Topic 8 — Health System – Architektur & Scripts
Use for technical health-system implementation: architecture, scripts, data model, symptom tracking, lab-value import, reports, automations, cronjob integration, error analysis, and optimisation. Do not handle medical therapy or strategy decisions here; route those to Topic 4.

### Topic 10 — Finance System – Architektur & Scripts
Use for technical finance-system implementation: import scripts, bank data, CSV processing, data models, dashboards, reports, automations, error analysis, and optimisation. Do not handle financial strategy here; route those to Topic 2.

### Topic 11 — JARVIS System – Architektur
Use only for overall JARVIS/Hermes/FRIDAY architecture, Telegram topic structure, memory concept, model routing, subagents, OpenClaw/Codex, cost optimisation, and security/permission concepts. Do not do concrete individual script debugging here; recommend or route to a coding/system/debugging topic.

### Topic 16 — Automationen / Cronjobs
Use for scheduled jobs, briefings, recurring reports, checks, reminders, watchdogs, automation outputs, cron delivery design, and monitoring summaries. Prefer explicit cron delivery targets with this thread id when relevant.

### Topic 17 — Research & AI Nutzung
Use for research, ChatGPT/Hermes/Gemini/Codex and general AI questions, tool comparisons, prompting, model choice, papers, external sources, and general knowledge research. Keep operational automation/debugging out unless explicitly tied to tool evaluation.

### Topic 19 — Family – Wife & Kids
Use for family organisation, private planning, appointments, to-dos, ideas, daily-life matters, and topics around wife and children. Treat as especially private and restrained; do not pull content from other topics unless explicitly asked.

### Topic 20 — Geschäftliches – Gasser Bauunternehmung
Use for business topics around Gasser Bauunternehmung, where Sir is Gesellschafter: strategy, processes, communication, organisation, optimisation, construction-site/project questions, and business analyses. Keep ERNE Holzbau matters in Topic 5.

### Topic 4850 — AutoShortsBot
Use for the AutoShortsBot project: architecture, implementation, repository/code, automation pipeline, prompts, media generation, publishing workflow, and Social-Media-Shorts strategy. Treat as its own project session and answer AutoShortsBot work only in this topic unless Sir explicitly requests cross-topic delivery. Project card: `~/jarvis_memory/33_autoshortsbot.md`.

### Topic 76 — System Logs / Debugging
Use for concrete operational debugging: error logs, Python tracebacks, cron failures, import errors, and concrete script repairs. Treat as a separate session. Keep broader JARVIS/Hermes architecture in Topic 11 and recurring automation design/monitoring in Topic 16 unless the task is a specific failure or script repair.

### Topic 80 — Security & Permissions
Use for API keys and credentials concepts, access control, bot permissions, secret handling, backup/restore strategy, and admin decisions. Treat as a separate session. Do not print raw secrets; use redacted paths, concepts, checks, and minimal diffs.

## Routing rules
- Treat each topic as its own session and answer only in the active/requested topic unless the user explicitly asks for cross-topic delivery or the correct target is obvious.
- When the user asks something in the wrong topic, prefer a short recommendation: “Besser in Topic X”. If the user asks to answer in the correct topic, send the substantive answer to that topic and keep only a short handoff note in the original topic.
- For cron jobs, prefer explicit delivery targets (`telegram:-1003907117629:<topic_id>`) instead of bare `telegram`, unless Sir requests Home/DM delivery.
- Keep topic-policy data durable here; do not rely on long chat history alone.

## Context policy
- Topic-purpose memory belongs in this card plus per-topic `channel_prompts`, not in long visible Telegram history.
- `compression.protect_last_n` is currently set to `24` for better local continuity while keeping token/cost impact moderate. Do not raise above `32` unless repeated topic-local decisions are lost before being written to this card or `90_decisions_log.md`.