ngn-agent/.planning/ROADMAP.md

Roadmap: ngn-agent

Milestones

• ✅ v1.0 MVP — Phases 1-4 (shipped 2026-06-14)
• 🚧 v1.1 Session Lifecycle, Memory & Reporting — Phases 5-9 (in progress)

Phases

✅ v1.0 MVP (Phases 1-4) — SHIPPED 2026-06-14

• Phase 1: Hermes Install & Provider Setup — completed 2026-06-14
• Phase 2: Memory, Git & Session Management — completed 2026-06-14
• Phase 3: Telegram Gateway — completed 2026-06-14
• Phase 4: Skills & Integrations — completed 2026-06-14

🚧 v1.1 Session Lifecycle, Memory & Reporting (In Planning)

Milestone Goal: Productionize session workspace with default repos, upgrade to persistent cross-session memory (hindsight), operationalize daily reporting with session lifecycle management, and provide portable setup script with essential tools.

• Phase 5: Hindsight Memory Provider — Cross-session persistent memory with entity-aware recall via Hindsight local_embedded
• Phase 6: Default Repos & SSH Mount — DEFAULT_REPOS mounted via host filesystem + SSH credential mounting
• Phase 7: Main Session Skill — Session lifecycle orchestration skill covering init-to-close workflow
• Phase 8: Cron Reporting — Daily session summaries, stale session archiving, and Jira integration
• Phase 9: Tooling & Portable Setup — Custom Docker image with AWS CLI, Terraform, Helm, kubectl, Datadog CLI + portable setup script

Phase Details

Phase 5: Hindsight Memory Provider

Goal: Cross-session persistent memory with entity-aware recall via Hindsight Cloud API Depends on: Nothing (independent config change) Requirements: MEM-01 Success Criteria (what must be TRUE):

1. Agent recalls facts across sessions without user prompting (cross-session semantic recall)
2. Agent detects similar previous sessions via hindsight similarity search on session start
3. Memory provider is set to hindsight (verifiable in config and agent state)
4. No memory provider conflicts — only one external provider registered (Hindsight, not MEMORY.md+user) Plans: 1 plan

Plans:

• 05-01-PLAN.md — Hindsight Memory Provider: Create config.json, set env var, activate provider, verify

Phase 6: Default Repos & SSH Mount

Goal: Default repos mounted directly from host filesystem into every new session workspace with secure SSH credential mounting for git operations Depends on: Nothing (independent from Phase 5) Requirements: REPO-01, REPO-02 Success Criteria (what must be TRUE):

1. New Hermes session has DEFAULT_REPOS (rai-ops, rai-deployment, rai-devtools) available at /workspace/repos/
2. Container restart doesn't lose cloned repos (host-mounted volume persists across container lifecycle)
3. User can request additional repo cloning mid-session and agent clones it via git command in Docker
4. SSH credentials are mounted read-only inside Docker (verified by container inspection)
5. Session init script completes within 30s timeout and doesn't block agent startup Plans: 1 plan

Plans:

• 06-01-PLAN.md — SSH key + repo volume mounts, session-init.sh, DEFAULT_REPOS config

Phase 7: Main Session Skill

Goal: Full session lifecycle orchestration skill covering the initial-plan.md workflow — init to close Depends on: Phase 5 (hindsight for session similarity detection), Phase 6 (repos in workspace) Requirements: SKIL-04 Success Criteria (what must be TRUE):

1. Agent detects similar previous sessions via hindsight on session start
2. Agent prompts for Jira ticket creation (Task type, configurable project, optional epic)
3. Agent loads relevant Confluence docs for context (searched by tag)
4. Agent prompts for Jira/Confluence updates at session end
5. Session summary auto-saved to hindsight (no prompt) Plans: 1 plan

Plans:

• 07-01-PLAN.md — Main Session Skill: create session/SKILL.md with full init→work→close lifecycle

Phase 8: Cron Reporting

Goal: Daily operational reporting with stale session archiving and Jira integration Depends on: Phase 7 (needs SKIL-04 session lifecycle to produce meaningful sessions to report/archive) Requirements: CRON-01, CRON-02, CRON-03 Success Criteria (what must be TRUE):

1. Telegram receives daily session summary report at 09:00
2. Daily report lists active sessions, last activity, token usage
3. Daily report includes Jira ticket status for active sessions via ngn-jira skill
4. Sessions inactive >30d are archived to JSON with no data loss (export-before-delete verified)
5. Archive script supports dry-run mode for safe initial testing before activating cron Plans: TBD

Phase 9: Tooling & Portable Setup

Goal: Custom Docker image with essential platform engineering tools (AWS CLI, Terraform, Helm, kubectl, Datadog CLI) and a portable setup script that can configure a fresh machine with all ngn-agent config in one invocation Depends on: Phase 5, Phase 6, Phase 7, Phase 8 (captures final state) Requirements: TOOL-01, SETUP-01 Success Criteria (what must be TRUE):

1. Custom Hermes Docker image includes aws-cli, terraform, helm, kubectl, and datadog CLI
2. Custom image is buildable with a single command
3. Portable setup script (setup-ngn-agent.sh) recreates all config (hindsight, repos, SSH, skills, cron) on a fresh machine
4. Setup script accepts SSH key path and repo paths as parameters (no hardcoded paths)
5. After running setup script + gateway restart, a new session has all tools, repos, and skills working Plans: TBD

Progress

Phase	Milestone	Plans Complete	Status	Completed
1. Hermes Install & Provider Setup	v1.0	—	Complete	2026-06-14
2. Memory, Git & Session Management	v1.0	—	Complete	2026-06-14
3. Telegram Gateway	v1.0	—	Complete	2026-06-14
4. Skills & Integrations	v1.0	—	Complete	2026-06-14
5. Hindsight Memory Provider	v1.1	1/1	Complete	2026-06-14
6. Default Repos & SSH Mount	v1.1	1/1	Complete	2026-06-14
7. Main Session Skill	v1.1	1/1	Complete	2026-06-14
8. Cron Reporting	v1.1	0/TBD	Not started	-
9. Tooling & Portable Setup	v1.1	0/TBD	Not started	-