You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/diataxis/en/explanation/development-progress-dashboard.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,9 @@ The key result is that the current code has moved further than the old plan word
15
15
- workflow-artifact review follow-up is part of the runtime surface,
16
16
- graph focus can render original markdown with matched-span highlighting,
17
17
- a dedicated evidence pane now carries grounding inspection plus durable `knowledge_run` and `flashcard_batch` inspection,
18
-
- grouped conversation knowledge points now retain relation-path and temporal-validity signals, and the composer uses them in structured explanation/next-action text.
18
+
- grouped conversation knowledge points now retain relation-path and temporal-validity signals,
19
+
- the composer now materializes an explicit `graphContext`,
20
+
- and that `graphContext` now survives through conversation trace, snapshot persistence, and workspace export.
19
21
20
22
At the same time, the product surface is still behind the intended final behavior:
21
23
@@ -34,12 +36,12 @@ Code-vs-plan reconciliation for this slice:
34
36
| Answer area contraction to a single targeted answer |`agent_workspace.js` now keeps the full conversation result in runtime state while only rendering user-facing answer blocks (`structured_answer`, `main_markdown`, `html_artifact`) in the main chat surface. | Implemented current slice |
35
37
| Hide developer-heavy evidence from the primary hit list |`workspace_panes.js` no longer renders inline knowledge previews or visible typed capability buttons in the left-side hit list; those flows now route into graph focus or the dedicated evidence pane. | Implemented current slice |
36
38
| Durable evidence/claim inspector |`workspace_panes.js` now exposes a dedicated evidence pane for grounding metadata, `knowledge_run`, `knowledge_run_history`, `knowledge_run_compare`, and `flashcard_batch`; `agent_workspace.js` wires the API status strip into grounding inspection. | Implemented current slice |
37
-
| DAG-native answer planning |`AgentConversationKnowledgePoint` now carries grouped `relationPath`, `relationKinds`, `relationPathAtomIds`, and `temporalValidity`, and `conversationComposer.ts` now uses those signals in overview, explanation, and next-action guidance. | Implemented partial slice |
39
+
| DAG-native answer planning |`AgentConversationKnowledgePoint` now carries grouped `relationPath`, `relationKinds`, `relationPathAtomIds`, and `temporalValidity`; `conversationComposer.ts` now materializes an explicit `graphContext`; `KnowledgeLearningPlatform.ts` and `WorkspaceExportBundle.ts` now preserve it through trace, persistence, and export surfaces. | Implemented partial slice |
38
40
39
41
Immediate next direction from this point:
40
42
41
-
1. Extend the new DAG-aware conversation slice into a dedicated graph-conditioned context-assembly layer instead of relying on grouped relation hints alone.
42
-
2. Preserve the new primary answer / right-pane-first interaction contract while growing the evidence pane toward a broader durable evidence ledger.
43
+
1. Extend the new DAG-aware conversation slice into a dedicated graph-conditioned context-assembly layer instead of relying on grouped relation hints and a thin `graphContext`alone.
44
+
2. Preserve the new primary answer / right-pane-first interaction contract while growing the evidence pane and `graphContext`toward a broader durable evidence ledger and graph explanation surface.
43
45
3. Continue ownership reduction across `src/server.ts`, `KnowledgeLearningPlatform.ts`, `agent_workspace.js`, and `workspace_panes.js`.
44
46
45
47
Verification for the current code-backed alignment:
@@ -50,6 +52,7 @@ Verification for the current code-backed alignment:
0 commit comments