Qiao-yq commented on issue #1539: URL: https://github.com/apache/dubbo-admin/issues/1539#issuecomment-6384456151
## Proposed Core MVP Plan After Phase 1 passes G1, the next milestone will deliver the issue’s three core capabilities: prompt templates, long-conversation summarization, and cross-session memory, through a unified Context Compiler. | PR | Status | Scope | Acceptance | | --- | --- | --- | --- | | 1. Compiler and Templates ([#1610](https://github.com/apache/dubbo-admin/pull/1610)) | Completed | Unified Source contracts, versioned templates, tool-call/result records, and request budgeting | Every Act/Answer call uses the compiler; roles, tool pairs, and budgets remain valid | | 2. Conversation Summaries ([#1611](https://github.com/apache/dubbo-admin/pull/1611)) | Completed | Structured rolling summaries, bounded recovery, and history fallback | Earlier goals survive beyond the recent window; failures and deletion do not corrupt or revive summaries | | 3. Cross-Session Memory | Planned | Explicit user-scoped memory APIs, project/task matching, and update/delete consistency | Relevant facts carry across Sessions; isolation holds and invalidated facts are not reinjected through tracked dependencies | | 4. User Controls and Validation | Planned | Simple memory editor, chat project/task selection, and end-to-end tests | Users can save, recall, correct, delete, clear, and disable memory through the UI | **Status:** PRs 1 and 2 are completed; PRs 3 and 4 remain planned. Delivery follows PR 1 → 2 → 3 → 4, targeting `ai`. All changes retain Phase 1 security and lifecycle guarantees. Automatic memory extraction, page-context integration, dynamic plugin management, and advanced retrieval are deferred. Completion requires all three capabilities to work end to end, including failure recovery and isolation checks. This milestone delivers the core capabilities within the issue’s scope, with the remaining G2/G3 requirements to be completed in subsequent work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
