# Roadmap: v1.69 L0 Source Discovery Via DeepXiv MCP Integration

## Result

`v1.69` is complete.

## Overview

`v1.69` closed the missing pre-registration discovery gap in `L0` without
widening Layer 0 into a general literature-automation engine. It added one thin
search-first bridge, one durable discovery receipt family, one explicit
fallback chain, and one isolated acceptance lane.

**Phases:** 143
**Total Plans:** 1
**Total Tasks:** 2
**Shipped:** 2026-04-12

## Phase Details

### Phase 143: L0 Source Discovery Via DeepXiv MCP Integration

**Goal:** Close the pre-registration discovery gap in `L0` by adding one
bounded search -> evaluate -> register path before the existing arXiv
registration helper.

**Plans:** 1 plan

Plans:

- [x] `143-01`: bounded search -> evaluate -> register adapter, fallback docs,
  and isolated acceptance

**Outcome:**

- landed `source-layer/scripts/discover_and_register.py`
- extended `register_arxiv_source.py` so isolated/offline verification can
  still use the same registration path
- wrote durable discovery receipts under
  `source-layer/topics/<topic_slug>/discoveries/`
- aligned runtime docs and tests to the new discovery acceptance lane

## Milestone Summary

**Key Accomplishments:**

- one explicit pre-registration discovery bridge now exists in `L0`
- one explicit candidate-evaluation receipt now keeps the selected source
  inspectable
- one isolated acceptance lane now proves discovery still lands in the normal
  Layer 0 and Layer 1 projection path

**Issues Resolved:**

- closed the gap where Layer 0 registration assumed the operator already knew
  an exact `arxiv_id`
- closed the gap where search-tool fallback behavior was only implicit

**Issues Deferred:**

- broader literature triage and larger search-provider expansion
- `L1` follow-on work around assumption/depth visibility

**Technical Debt / Honest Gaps:**

- the bridge stays intentionally thin and does not claim full literature-
  scouting automation
- DeepXiv remains an external provider dependency rather than `L0` core state

---

For current planning state after `v1.69`, continue from the next active
milestone and fresh requirements definition.
