coulomb/evidence-source
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
evidence-source/workplans/ESRC-WP-0004-citation-recovery.md
tegwick df6acad828
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details
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

1.4 KiB
Raw Blame History

id type title domain repo status owner topic_slug created updated spec_refs state_hub_workstream_id
ESRC-WP-0004 workplan Local citation recovery and external source discovery hooks infotech evidence-source proposed codex citation_evidence_mvp 2026-07-08 2026-07-08
INTENT.md
README.md
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

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.

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).