evidence-source/workplans/ESRC-WP-0004-citation-recovery.md
tegwick df6acad828
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
chore(consistency): write back state-hub workplan/task IDs [auto]
fix-consistency C-06/C-11 registered ESRC-WP-0002..0004 and the
ESRC-WP-0001 tasks; IDs written back into the workplan files.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-08 20:56:39 +02:00

50 lines
1.4 KiB
Markdown

---
id: ESRC-WP-0004
type: workplan
title: "Local citation recovery and external source discovery hooks"
domain: infotech
repo: evidence-source
status: proposed
owner: codex
topic_slug: citation_evidence_mvp
created: "2026-07-08"
updated: "2026-07-08"
spec_refs:
- INTENT.md
- README.md
state_hub_workstream_id: "2ce8b799-d67c-4dbf-aac5-0ff1f0363d62"
---
# ESRC-WP-0004 — Citation recovery and source discovery hooks
`evidence-source`'s original intent includes recovering citations when a stored
selector goes stale and discovering the external source a document was drawn
from. This is the largest deferred strand and depends on the anchoring layer's
selector model.
## Open questions
- What is the recovery contract — does this repo *detect* stale selectors, or
only provide the re-ingest/re-fingerprint primitives the anchor layer calls?
- Where does external source discovery (URL/DOI resolution) belong relative to
`citation-engine` and the umbrella?
## Sketch
```task
id: ESRC-WP-0004-T01
status: todo
priority: low
state_hub_task_id: "e7ff29b9-f04f-44f5-a23a-b028fc20a80b"
```
Design the recovery boundary with the anchor layer: define what
`evidence-source` owns vs. what stays in anchoring.
```task
id: ESRC-WP-0004-T02
status: todo
priority: low
state_hub_task_id: "88a512d1-70e0-4bfa-b6b0-c1e4e31abb97"
```
Prototype re-ingest/re-fingerprint recovery primitives and a discovery hook
interface (no network coupling baked into the core).