# 90 Decisions Log

_Last updated: 2026-05-14_

## Purpose
Append-only record of important decisions and rationale.

## Load when
- When a significant user/agent decision is made or reviewed
- When tracing why a policy/system choice exists

## Stable facts
- This file should track decisions, date, context, rationale, and owner.
- It is not a dump for secrets or raw logs.

## Operating rules
- Append concise entries; do not rewrite history except to correct factual errors with note.
- Record source/evidence path when useful.
- Separate decision from recommendation.

## Data sources
- User confirmations
- Config changes
- System audits
- Relevant domain cards

## Do-not-store
- Secrets, tokens, full private documents
- Speculation as decision

## Open questions
- Preferred decision ID format?
- Which past decisions should be backfilled?
## 2026-05-14 — Telegram topic routing policy
Decision: `JARVIS Command Center` Telegram topics are treated as separate sessions with explicit routing. Topic 11 is the architecture/governance lane; concrete individual script debugging belongs in a coding/system/debugging lane, not Topic 11. Topic policies are stored in `02_telegram_topics.md` and reinforced via Telegram channel prompts.
Rationale: prevents memory bleed, keeps automation outputs and architecture decisions separated, and allows cron jobs to target exact topics.
Owner: Sir / JARVIS.


## 2026-05-14 — Completed Telegram topic map and channel prompts
- Reconstructed the full JARVIS Command Center topic map from prior per-topic setup sessions and channel directory thread ids.
- Mirrored all known topics (2,3,4,5,6,8,10,11,16,17,19,20) into `/home/agent/jarvis_memory/02_telegram_topics.md` and `gateway.telegram.channel_prompts`.
- Raised `compression.protect_last_n` from 16 to 24 as a moderate continuity improvement; avoid >32 unless proven necessary.
- Gateway restart is required before new channel prompts are active.


## 2026-05-14 — Added Security and Debugging Telegram topics
- Added Topic 76: System Logs / Debugging for concrete logs, tracebacks, cron failures, import errors, and script repairs.
- Added Topic 80: Security & Permissions for credentials concepts, access control, bot permissions, secret handling, backup/restore, and admin decisions.
- Adopted hybrid routing: DM/Home is the quick butler inbox; JARVIS Command Center Topic 6 is official triage; durable/fachliche work goes to the relevant specialist topic.
- Gateway restart is required before the new channel prompts become active.