docs: start milestone v1.1 Session Lifecycle, Memory & Reporting
This commit is contained in:
@@ -27,7 +27,12 @@ The agent must NEVER mutate real infrastructure beyond what the limited IAM role
|
||||
|
||||
### Active
|
||||
|
||||
(Next milestone goals to be defined)
|
||||
- [ ] **REPO-01**: Every new Hermes session auto-clones DEFAULT_REPOS (rai-ops, rai-deployment, rai-devtools)
|
||||
- [ ] **REPO-02**: User can request additional repos to clone on demand during a session
|
||||
- [ ] **MEM-05**: Long-term memory upgraded to hindsight (persistent cross-session recall)
|
||||
- [ ] **CRON-01**: Daily report summarizing active sessions sent via Telegram gateway
|
||||
- [ ] **CRON-02**: Stale sessions (inactive >30d) auto-archived with history preserved
|
||||
- [ ] **CRON-03**: Daily report updates Jira with session progress
|
||||
|
||||
### Out of Scope
|
||||
|
||||
@@ -67,6 +72,18 @@ The agent must NEVER mutate real infrastructure beyond what the limited IAM role
|
||||
- **Git**: Worktree-based isolation; pushes only to feature branches
|
||||
- **Gateway**: Telegram as primary messaging channel
|
||||
|
||||
## Current Milestone: v1.1 Session Lifecycle, Memory & Reporting
|
||||
|
||||
**Goal:** Productionize session workspace with default repos, upgrade to persistent cross-session memory (hindsight), and operationalize daily reporting with session lifecycle management.
|
||||
|
||||
**Target features:**
|
||||
- Default repos auto-cloned into every new Hermes session
|
||||
- On-demand repo cloning during sessions
|
||||
- Hindsight long-term memory provider
|
||||
- Daily cron report (session summaries via Telegram)
|
||||
- Stale session auto-archive (30d)
|
||||
- Jira integration in daily reporting
|
||||
|
||||
## Key Decisions
|
||||
|
||||
| Decision | Rationale | Outcome |
|
||||
@@ -96,4 +113,4 @@ This document evolves at phase transitions and milestone boundaries.
|
||||
4. Update Context with current state
|
||||
|
||||
---
|
||||
*Last updated: 2026-06-14 after v1.0 milestone*
|
||||
*Last updated: 2026-06-14 — v1.0 shipped, v1.1 in planning*
|
||||
@@ -1,3 +1,18 @@
|
||||
---
|
||||
gsd_state_version: 1.0
|
||||
milestone: v1.1
|
||||
milestone_name: Session Lifecycle, Memory & Reporting
|
||||
status: planning
|
||||
last_updated: "2026-06-14T05:46:37.415Z"
|
||||
last_activity: 2026-06-14
|
||||
progress:
|
||||
total_phases: 0
|
||||
completed_phases: 0
|
||||
total_plans: 0
|
||||
completed_plans: 0
|
||||
percent: 0
|
||||
---
|
||||
|
||||
# Project State
|
||||
|
||||
## Project Reference
|
||||
@@ -15,14 +30,23 @@ See: .planning/PROJECT.md (updated 2026-06-14)
|
||||
- **Next action**: User sets JIRA_API_TOKEN, then all 22 requirements are met
|
||||
|
||||
## What's Running
|
||||
|
||||
- Hermes v0.16.0 CLI (Bedrock + OpenRouter fallback)
|
||||
- Telegram gateway (launchd service, PID in logs)
|
||||
- Docker terminal backend (config + SSO cache mounted)
|
||||
- 4 custom ngn-agent skills registered
|
||||
|
||||
## Notes
|
||||
|
||||
- .aws/config: mounted ro, SSO cache: mounted rw
|
||||
- ngn-* scripts at ~/.hermes/scripts/ mounted to /usr/local/bin:ro in Docker
|
||||
- JIRA_EMAIL and JIRA_API_TOKEN forwarded into Docker via docker_forward_env
|
||||
- Telegram paired user 474440517 (Bapung)
|
||||
- Research docs: 7 files in .planning/research/hermes/
|
||||
|
||||
## Current Position
|
||||
|
||||
Phase: Not started (defining requirements)
|
||||
Plan: —
|
||||
Status: Defining requirements
|
||||
Last activity: 2026-06-14 — Milestone v1.1 started
|
||||
|
||||
Reference in New Issue
Block a user