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: Interface Document.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,10 +52,14 @@ Audit flow:
52
52
53
53
- Scoped retrieval is now represented by `KnowledgeQueryRequest.scope` and `KnowledgeCorpusScope`.
54
54
-`AgentConversationResponse` remains backward-compatible: `assistantMessage` is still valid, while `answer`, `citations`, `memoryActions`, `trace`, and optional `assistantBlocks` provide richer grounded conversation state.
55
+
-`AgentConversationKnowledgePoint` may now carry grouped/document-augmented evidence fields such as `atomIds`, `documentId`, `sourcePath`, `citations`, `matchedSpans`, and `matchCount`, while preserving the original top-level title/summary/citation shape.
56
+
- Scoped query traces may now report `scopeSource: planner_scope_recovery` when title-like recovery intentionally switches from an incompatible explicit scope to a document-only recovery scope.
55
57
-`/api/knowledge/conversation` remains the conversation entrypoint and supports current stream/sync compatibility behavior.
-`POST /api/knowledge/export/workspace` exposes deterministic workspace export bundles backed by resource, index, workspace, session, workflow, memory, and render-materialization state.
58
60
- Runtime governance payloads expose graphdb/vector rollout context, including `rolloutProfile`, graphdb connector health, vector acceleration strictness, and runbook checks.
61
+
- The Knowledge Workspace frontend contract now also includes an in-pane scope selector, a compact conversation API status strip, file-first grouped hit rendering, and matched-span evidence rendering inside the focus pane. These are additive UI/runtime contracts over the existing backend payloads, not a replacement of public response fields.
62
+
-`assistantBlocks` are no longer only transport wrappers around the same legacy answer string. Current Tauri-capable clients should expect intent-aware overview / explanation / evidence / memory / action sections while still honoring `assistantMessage` as the compatibility fallback.
59
63
- Compatibility rule: new response fields must remain additive and optional; Godot/mobile paths must continue to use PNG-first materialized render artifacts instead of requiring direct SVG import.
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,9 +30,11 @@ Unlike traditional "network" views that show a messy web of links, NoteConnectio
30
30
## Current Mainline Architecture Status (2026-06-06)
31
31
32
32
- The current `main` branch has code-backed scoped retrieval, grounded conversation, durable resource/index/workspace/session/memory/export substrate, explicit export profiles, and PNG-first Godot/mobile render materialization.
33
+
- The Knowledge Workspace is no longer only a thin chat shell over the global folder selector: it now has an in-pane scope switcher, a compact `/api/knowledge/conversation` status strip, grouped knowledge-point hits rendered as file-first entries, matched-span rendering in the focus pane, and explicit recovered-source visibility when `planner_scope_recovery` is used.
33
34
- graphdb/sqlite and ANN/external connector paths are operational baselines, not production-closed release claims. Release closure still depends on repeated soak evidence, workload thresholds, recall/latency calibration, and strict rollout proof.
34
35
-`npm run verify:foundation:release-evidence` now audits the latest sqlite soak and ANN release-gate JSON reports for freshness and passing gates before current-host evidence is used as release context; `npm run verify:foundation:release-evidence:strict` additionally requires repeated fresh valid history reports, is exposed in foundation readiness as `foundation_release_evidence_history`, and now passes on the current Windows host with sqlite `3/3` and ANN `3/3`. `npm run verify:foundation:release-evidence:multi-host` is now available when a release window needs at least two host keys per component, but current Windows-host evidence remains single-host.
35
36
- Backward compatibility is preserved through additive response evolution: `assistantBlocks` can carry richer Tauri agent replies while legacy `assistantMessage` remains valid.
37
+
- Tauri agent replies are now materially richer than the old plain-text path: the backend emits intent-aware overview / explanation / evidence summary / memory notice / next-action sections, while still preserving the old `assistantMessage` field for legacy clients.
36
38
- The current architecture pressure is ownership reduction: `src/server.ts`, `src/learning/KnowledgeLearningPlatform.ts`, and large frontend host files remain the next simplification targets.
37
39
- Current code-vs-plan details are tracked in [Architecture Progress Alignment and Mainline Plan (2026-06-06)](docs/solutions/architecture-progress-alignment-2026-06-06.md) and [Development Progress Dashboard](docs/diataxis/en/explanation/development-progress-dashboard.md).
- optional `assistantBlocks` carries richer typed reply sections for clients that can render them.
59
+
-`AgentConversationKnowledgePoint` may now include grouped/document-augmented fields such as `atomIds`, `documentId`, `sourcePath`, `citations`, `matchedSpans`, and `matchCount`.
60
+
- Scoped query resolution may now expose `scopeSource: planner_scope_recovery` when a title-like recovery path intentionally leaves the original explicit corpus boundary and switches to a document-only recovery scope.
59
61
-`/api/knowledge/conversation` supports the current conversation path, including stream-first clients and sync fallback behavior.
-`/api/knowledge/workspace-readiness` exposes workspace/corpus readiness for scoped runtime decisions.
62
64
-`POST /api/knowledge/export/workspace` exposes deterministic workspace export bundles backed by resource, index, workspace, session, workflow, memory, and render-materialization state.
63
65
- Runtime governance endpoints and payloads expose graphdb/vector rollout context, including `rolloutProfile`, graphdb connector health, vector acceleration strictness, and runbook checks.
66
+
- The Knowledge Workspace frontend contract now also includes an in-pane scope selector, a compact `/api/knowledge/conversation` status strip, grouped file-first hit rendering, and matched-span evidence rendering in the focus pane.
67
+
-`assistantBlocks` are no longer only thin transport wrappers around the same plain answer string. Tauri-capable clients should now expect intent-aware overview / explanation / evidence / memory / action sections while still treating `assistantMessage` as the compatibility fallback.
Copy file name to clipboardExpand all lines: docs/en/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,10 @@ Unlike traditional "network" views that show a messy web of links, NoteConnectio
28
28
## Current Mainline Architecture Status (2026-06-06)
29
29
30
30
- Current `main` has code-backed scoped retrieval, grounded conversation, durable resource/index/workspace/session/memory/export substrate, explicit export profiles, and PNG-first Godot/mobile render materialization.
31
+
- The Knowledge Workspace now includes an in-pane scope switcher, a compact conversation API status strip, grouped file-first knowledge-point hits, matched-span rendering in the focus pane, and explicit recovered-source visibility when `planner_scope_recovery` is used.
31
32
- graphdb/sqlite and ANN/external connector paths are operational baselines. Production closure still requires repeated soak evidence, workload thresholds, recall/latency calibration, and strict rollout proof.
32
33
- Compatibility remains additive: rich `assistantBlocks` can be used by newer clients while legacy `assistantMessage` stays valid.
34
+
- Tauri reply organization is now intent-aware and section-based: overview, explanation, evidence summary, memory notice, and next-action guidance are emitted as structured blocks rather than one flat answer string.
33
35
- The next architecture work is ownership reduction in `src/server.ts`, `src/learning/KnowledgeLearningPlatform.ts`, and large frontend host files.
34
36
- Current code-vs-plan details: [Architecture Progress Alignment and Mainline Plan (2026-06-06)](../solutions/architecture-progress-alignment-2026-06-06.md) and [Development Progress Dashboard](../diataxis/en/explanation/development-progress-dashboard.md).
| Governance and CI | Strong but not complete | docs gates, route/agent contracts, runtime verifiers, SBOM/sidecar gates | Keep evidence freshness and host-specific release gates separate from implementation-complete claims. |
81
81
82
+
### Follow-Through on Current `main`
83
+
84
+
The current local `main` has already moved beyond the initial 2026-06-06 documentation-only alignment slice.
85
+
Subsequent local mainline commits, still preserving public runtime compatibility, added four concrete execution follow-through tracks:
86
+
87
+
1.**Foundation release evidence**
88
+
- default freshness audit,
89
+
- strict repeated-evidence audit,
90
+
- opt-in multi-host audit,
91
+
- readiness-exposed release aliases and repeated-evidence checks.
92
+
2.**Frontend/runtime auth recovery**
93
+
- stale sidecar settings authentication recovery in the frontend runtime bridge path.
94
+
3.**Knowledge Workspace grounded-answer UX**
95
+
- compact API health/status strip,
96
+
- grouped document-level knowledge hits with `matchedSpans`,
97
+
- direct evidence-first top-level answers instead of the old repeated “strongest match” template.
98
+
4.**Scoped-retrieval recovery and workspace-local scope UX**
99
+
-`planner_scope_recovery` when title-like hits exist outside the originally selected scope,
100
+
- in-pane scope switching inside the Knowledge Workspace,
101
+
- explicit recovered-source visibility when recovery is used.
102
+
103
+
These do not change the main planning order.
104
+
They do change the current progress reading:
105
+
106
+
- P1 is no longer only “release evidence exists”; it now includes freshness, strict repeated evidence, and opt-in multi-host audit tooling.
107
+
- P3/P4 are no longer only “assistant blocks exist”; they now include intent-aware section composition plus knowledge-workspace scope and grouped-hit UX that makes scoped grounded conversation materially usable in Tauri.
108
+
- P2 and deeper ownership reduction are still the next structural pressure point, because these newer capabilities remain largely orchestrated through `src/server.ts`, `src/frontend/agent_workspace.js`, `src/frontend/workspace_panes.js`, and `KnowledgeLearningPlatform.ts`.
0 commit comments