Files
ngn-agent/.planning/milestones/v1.0-ROADMAP.md

2.8 KiB

Milestone Archive: v1.0 MVP

Shipped: 2026-06-14 Phases: 4 | Plans: 4 | Tags: v1.0

Phase Details

Phase 1: Hermes Install & Provider Setup

Goal: Hermes Agent installed, Docker backend configured with security hardening, Bedrock + OpenRouter providers configured, limited AWS role mounted, dangerous command approval active. Requirements: AUTH-01 through AUTH-05, CONT-01 through CONT-06 Status: ✓ Complete

Phase 2: Memory, Git & Session Management

Goal: Hermes persistent memory operational, session search working, git worktree isolation enabled, infrastructure facts auto-saved. Requirements: MEM-01 through MEM-04 Status: ✓ Complete

Phase 3: Telegram Gateway

Goal: Telegram gateway operational with pairing-based authorization, scheduled tasks working. Requirements: GATE-01 through GATE-04 Status: ✓ Complete

Phase 4: Skills & Integrations

Goal: Skills system operational, Jira/Confluence/Bitbucket API integration, read-only infra diagnostic skills. Requirements: SKIL-01 through SKIL-03 Status: ✓ Complete

Key Decisions

Decision Rationale Outcome
Hermes Agent over NanoClaw Superior memory system (auto-learning, session search, 8 external providers) ✓ Good
Bedrock primary + OpenRouter fallback Zero additional API cost for primary (uses existing AWS SSO); OpenRouter as reliability layer ✓ Good
Docker backend Container isolation is the security boundary; dangerous command checks skipped ✓ Good
Project-local ./.aws/config Prevents privileged credentials from entering container ✓ Good
CLI-only install Desktop not needed; minimal surface area ✓ Good
Git worktree isolation Prevents branch contamination across sessions ✓ Good
dev_Restricted SSO role Limited IAM prevents infrastructure mutations ✓ Good
curl wrappers for Atlassian APIs Simpler than MCP for Jira/Confluence/Bitbucket ✓ Good

Accomplishments

  1. Hermes Agent v0.16.0 installed and configured with Bedrock + OpenRouter
  2. Docker terminal backend with security hardening and limited AWS SSO role
  3. Telegram gateway running as launchd service with DM pairing
  4. 4 custom platform engineering skills (AWS diagnostics, Jira, Confluence, Bitbucket)
  5. Persistent memory + session search + git worktree isolation enabled
  6. Custom Atlassian API wrapper scripts mounted into Docker container
  7. 7 research documents covering all Hermes capabilities
  8. Full GSD project structure with planning artifacts

Known Gaps

  • No automated stale session archive (30d cleanup from initial-plan.md) — deferred
  • Memory provider not yet scaled (using built-in MEMORY.md/USER.md)
  • JIRA_API_TOKEN configured manually — no rotation automation