Decisions
- Pending: Which vault content to export to NotebookLM?
- Pending: Manual export or automated sync?
- Pending: What NotebookLM outputs to bring back into Opus?
User Tasks
Summary
Connect Opus vault content to Google NotebookLM for AI-powered audio summaries, Q&A, and alternative perspectives on the system’s knowledge.
Problem / Motivation
Opus accumulates knowledge, feature specs, and decisions — but consuming all of it requires reading markdown files. NotebookLM can ingest documents and generate audio “Deep Dive” overviews, answer questions conversationally, and surface connections across sources. This gives a different (audio, conversational) interface to Opus knowledge.
Proposed Solution
Export selected vault content to NotebookLM as sources. Optionally bring insights back into Opus.
Potential value:
- Audio briefings — NotebookLM Deep Dive podcasts summarizing Opus state, feature progress, or knowledge areas
- Alternative Q&A — ask NotebookLM questions about your system from a different AI perspective
- Knowledge review — feed
20_knowledge/and feature specs to spot gaps or contradictions
Open Questions
1. Which vault content to export?
Question: What parts of the vault should be fed into NotebookLM?
| Option | Description |
|---|---|
| A) Curated subset | Feature specs (in-progress), knowledge base, dashboards — manually selected |
| B) Full vault export | Everything in vault/ as a bulk upload |
| C) Topic-based notebooks | Separate NotebookLM notebooks per domain (features, knowledge, daily) |
Recommendation: Option A — start small, see what’s useful before scaling.
Decision:
2. Sync method
Question: How to get vault content into NotebookLM?
| Option | Description |
|---|---|
| A) Manual upload | Export markdown files, upload to NotebookLM manually |
| B) Google Drive sync | Sync vault to Google Drive, NotebookLM reads from there |
| C) API integration | Use NotebookLM API (if available) for programmatic upload |
Recommendation: Option A for now — NotebookLM’s API access is limited.
Decision:
3. What to bring back?
Question: Should NotebookLM outputs feed back into Opus?
| Option | Description |
|---|---|
| A) Nothing — consume only | Use NotebookLM as a read-only consumption layer |
| B) Save audio links | Store links to generated Deep Dives in vault |
| C) Capture insights | Manually note useful insights back into 20_knowledge/ |
Recommendation: Option A initially, Option C if it proves valuable.
Decision:
Phase Overview
| Phase | Description | Status |
|---|---|---|
| Phase 1 | Research & manual test | — |
| Phase 2 | Structured export workflow | — |
| Phase 3 | Automated sync (if API available) | — |
Phase 1: Research & Manual Test —
Goal: Verify NotebookLM works well with Opus markdown content.
| File / Feature | Details | Owner | Status |
|---|---|---|---|
| Test upload | Upload 5-10 vault files to NotebookLM manually | mv | — |
| Deep Dive test | Generate audio overview of feature specs | mv | — |
| Q&A test | Ask NotebookLM questions about Opus architecture | mv | — |
| Evaluate quality | Is the output useful enough to continue? | mv | — |
Phase 2: Structured Export —
Goal: Create a repeatable process for exporting vault content to NotebookLM.
| File / Feature | Details | Owner | Status |
|---|---|---|---|
| Export script | Script to bundle selected vault files for upload | opus | — |
| Notebook structure | Define which NotebookLM notebooks to maintain | opus | — |
| Update cadence | How often to refresh sources | opus | — |
Phase 3: Automated Sync —
Goal: Automate the export pipeline (only if API becomes available).
| File / Feature | Details | Owner | Status |
|---|---|---|---|
| API research | Check NotebookLM API availability | opus | — |
| Sync script | Automated upload via API or Google Drive | opus | — |
Prerequisites / Gap Analysis
Requirements
| Requirement | Description |
|---|---|
| REQ-1 | Google account with NotebookLM access |
| REQ-2 | Vault content in a state worth exporting (some maturity) |
Current State
| Component | Status | Details |
|---|---|---|
| NotebookLM access | unknown | Need to verify account access |
| Vault content | WIP | ~46 FRs, knowledge base, dashboards exist |
| API availability | unknown | NotebookLM API may be limited or unavailable |
Gap (What’s missing?)
| Gap | Effort | Blocker? |
|---|---|---|
| API research | Low | No — can start manually |
| Export script | Low | No |
Test
Manual tests
| Test | Expected | Actual | Last |
|---|---|---|---|
| … | … | pending | - |
AI-verified tests
| Scenario | Expected behavior | Verification method |
|---|---|---|
| … | … | … |
E2E tests
| Scenario | Assertion |
|---|---|
| … | … |
Integration tests
| Component | Coverage |
|---|---|
| … | … |
Unit tests
| Component | Tests | Coverage |
|---|---|---|
| … | … | … |
History
| Date | Event | Details |
|---|---|---|
| 2026-03-11 | Created |
References
- FR-037 (Daily Briefings) — audio briefings could complement written ones
- FR-025 (Atlas Vault Integration) — similar “connect external tool” pattern