Repository navigation
id: design: AI-over-notes cluster (from #5678) #5842
Description
Summary
Follow-on design ticket from #5678 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
Source-grounded Q&A over a user's corpus (à la NotebookLM): summarisation, citation-back-to-source requirements, audio/overview generation if in scope, and the privacy model — whose AI sees whose notes — under the parent's read-authority rules.
Context from the parent
The parent is a design-to-make-designs: a competitor feature-matrix programme over the #2048 zettelkasten layer whose deliverable is one follow-on design per cluster and per importer, filed and linked on the parent. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5678. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Activity
developing-today commentedon Nov 5, 2026
CODE-1525
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off
developing-today commentedon Nov 5, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 5, 2026
🤖 Agent note · picked up
Agent: queue worker (repo-worker-code), lane bf419306-c4ef-470f-a553-beabf93239de
Session / ID: task 10245
Found via: queue claim
Task: triage design issue #5842 against parent #5678 and the existing design deliverable.
Expectation: confirm whether scope is already defined and route through the existing design work without duplicating child issues or reopening parent decisions.
Links: #5842 · #5678
dezren39 commentedon Nov 5, 2026
🤖 Agent note · triage findings
Agent: queue worker (repo-worker-code), lane bf419306-c4ef-470f-a553-beabf93239de
Session / ID: task 10245
Finding: #5842 remains OPEN as a design deliverable; no matching implementation PR exists. Its scope is already concrete: source-grounded Q&A over a user's corpus, citations, summarisation/audio scope, and privacy under the knowledge layer's read-authority model. Parent #5678 is OPEN and already rules the default read resolution order (object → user default → server config → public), so this child must inherit it rather than re-decide it. The parent also calls for one design per cluster; #5842 is the AI-over-notes cluster under epic #2056.
Disposition: confirmed as ready for the existing design/research workflow. Keep #5842 open until its decision record meets the stated acceptance; if the design changes a parent decision, record that delta on #5678. No duplicate child task or implementation PR is needed.
Evidence: fresh REST reads of #5842 and #5678 at 2026-11-05T14:01:38Z; PR search found no implementation PR.
Links: #5842 · #5678 · #2056