# Phase 8: Cron Reporting - Discussion Log

> **Audit trail only.** Do not use as input to planning, research, or execution agents.

**Date:** 2026-06-14
**Phase:** 8-Cron Reporting
**Areas discussed:** Report schedule, Report content, Archive behavior, Jira integration depth

---

## Report Schedule

**User's choice:** Daily at 09:00 SGT (UTC+8). Weekly Sunday 20:00 SGT for stale summary + archive.

**Notes:** Two separate cron jobs — daily report and weekly stale/archive.

---

## Report Content

**User's choice:** Daily report updates JIRA with last activity (session → JIRA is 1-to-many). No ticket status updates unless user specifies. Weekly stale report summarizes all inactive sessions.

**Notes:** Daily = active session progress comments on linked JIRAs. Weekly = inactive session summary only.

---

## Archive Behavior

**User's choice:** Use Hermes-native commands (`hermes sessions export` + `hermes sessions prune`).

**Notes:** Native Hermes tools exist — no custom scripting needed. Archive to `~/.hermes/archive/sessions/`. Dry-run mode first.

---

## Jira Integration Depth

**User's choice:** Active tickets get daily progress comments. Stale tickets get mentioned in summary only (no auto-comment). No auto status transitions.

**Notes:** User must explicitly ask for ticket status changes. 1-to-many session→Jira mapping.

---

## Deferred Ideas

- Auto-close tickets for archived sessions
- Teams gateway delivery
- Custom archive dashboard