bapung/ngn-agent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: create milestone v1.1 roadmap (4 phases)

Browse Source
This commit is contained in:
Bagas Purwa Sentika
2026-06-14 18:09:56 +08:00
parent 719fb1e07a
commit 99015d3327
4 changed files with 140 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

75
.planning/ROADMAP.md
View File

@@ -3,6 +3,7 @@
## Milestones
- ✅ **v1.0 MVP** — Phases 1-4 (shipped 2026-06-14)
- 🚧 **v1.1 Session Lifecycle, Memory & Reporting** — Phases 5-8 (in planning)
## Phases
@@ -16,11 +17,73 @@
</details>
### 🚧 v1.1 Session Lifecycle, Memory & Reporting (In Planning)
**Milestone Goal:** Productionize session workspace with default repos, upgrade to persistent cross-session memory (hindsight), and operationalize daily reporting with session lifecycle management.
- [ ] **Phase 5: Hindsight Memory Provider** — Enable cross-session persistent memory with entity-aware recall via Hindsight Cloud API
- [ ] **Phase 6: Default Repos & SSH Mount** — Auto-clone DEFAULT_REPOS into every new session with secure 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 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**: TBD
### Phase 6: Default Repos & SSH Mount
**Goal**: Default repos auto-cloned into every new session with secure 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**: TBD
### 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 loads DEFAULT_REPOS into workspace on session init
3. Agent creates a Jira ticket for the session task automatically
4. Agent loads relevant Confluence docs for context
5. Agent updates docs and Jira ticket at session end with results summary
**Plans**: TBD
### 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
## Progress
| Phase | Milestone | 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 |
| 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 | 0/TBD | Not started | - |
| 6. Default Repos & SSH Mount | v1.1 | 0/TBD | Not started | - |
| 7. Main Session Skill | v1.1 | 0/TBD | Not started | - |
| 8. Cron Reporting | v1.1 | 0/TBD | Not started | - |