diff --git a/docs/notebook-implementation-plan.md b/docs/notebook-implementation-plan.md
index 6802170..dda4f97 100644
--- a/docs/notebook-implementation-plan.md
+++ b/docs/notebook-implementation-plan.md
@@ -219,6 +219,22 @@ The next practical Didactopus sequence should be:
 3. upgrade `notebook_page` to summarize hub, neighborhood, and secondary lanes
 4. expose secondary-product and distinction views in learner/workbench flows
 5. enforce explicit public citation and quote-marking contracts
+6. keep a `.groundrecall/work-map` in active projects so source roots,
+   temporary builds, exports, and deployment targets remain easy to locate
+
+## Related modernization tasks
+
+The Notebook work now clearly depends on adjacent modernization tasks:
+
+- expand bibliography keyword/keyphrase coverage so CiteGeist and TOA
+  bibliography support reflect Notebook terminology
+- harvest terminology from book indexes as a separate authoritative signal
+- ingest opposition-index terminology as a salience signal with lower authority
+  weight
+- attach citation-block fallbacks to pages that are not yet citation-complete
+- schedule citation expansion for pages that already have some citations
+- keep a timeline framework in scope for rollout even if the fuller timeline
+  graph is a later phase
 
 ## What the pilot changed
 
diff --git a/docs/roadmap.md b/docs/roadmap.md
index 75a8bfc..93c0833 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -232,6 +232,58 @@ Immediate next steps:
   incidental metadata
 - connect Notebook concept neighborhoods more directly to learner-session
   grounding and practice generation
+- add a project-level `.groundrecall/work-map.{json,md}` convention so active
+  source roots, export roots, temp builds, and deployment targets stay easy to
+  find across long-running modernization work
+- extend Notebook-related terminology work into bibliography/index workflows:
+  - expand TOA/CiteGeist keyword and keyphrase coverage for Notebook concepts
+  - use book-index terminology as an authoritative signal for concept ranking
+  - allow opposition-index terminology to raise salience without raising
+    authority score
+- add citation-coverage triage for public-facing pages:
+  - `citation_missing`
+  - `citation_thin`
+  - `citation_rich`
+- use visible citation blocks for pages that do not yet have full citation
+  support
+
+### 8a. Timeline framework for Archive modernization
+
+Status: planned
+
+Why it matters:
+
+- The Archive needs a structured chronology path for publications, court cases,
+  educational milestones, and controversy events.
+- A timeline is useful even before the full citation graph and Notebook link
+  structure are complete.
+- A timeline framework is realistic for rollout, even if deep expansion is a
+  post-rollout task.
+
+Near-term scope:
+
+- support timeline entry types:
+  - `publication`
+  - `case`
+  - `event`
+- support multiple time granularities:
+  - exact date
+  - year
+  - date range
+  - decade
+  - century
+  - deep-time epoch
+- seed a small set of high-value entries for public launch
+- connect timeline entries to Notebook concepts, citation status, and later
+  evidence-docket expansion
+
+Longer-term scope:
+
+- add aggregate entries for years, decades, and centuries
+- add deep-time scientific chronology back through geological eras and major
+  life-history milestones
+- connect publications to open-access links, cites/cited-by expansion, and
+  opposition-response dockets
 
 ### 9. Pack quality, review, and concept-graph curation improvements