Evidence Ledger - surface contradiction and certainty per motif #125

New issue

Closed

opened 2026-07-15 20:35:36 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-15 20:35:36 +00:00

Contributor

Feature idea (Fable ideation, rank #2) · Effort: S · Value: High

Pitch
A per-motif "how solid is this?" panel: contradicted entries, certainty mix, and unresolved contradicts edges - plus a project-wide list of open contradictions.

Why it matters
The app records certainty (confirmed/likely/speculative, 002_entries_tags_audit.sql) and typed contradicts connections (005_motifs_connections.sql) - but nothing consumes those semantics. A motif resting on 14 speculative entries and 2 contradicted ones should look different from one built on confirmed observations, especially before it's published. This is the difference between a note pile and a defensible research claim.

How it fits
Pure read-side: new endpoints in api/src/routes/analytics.ts (today only counts/prevalence/co-occurrence) joining connections WHERE type='contradicts' with entry_motifs and entries.certainty, scoped by ACTIVE_PROJECT_SQL (lib/projectAccess.ts). Optionally a resolved_at/resolution_notes column on connections so a contradiction can be closed with a verdict. Badge on motif detail and (opt-in) public motif pages (routes/public.ts).

Why it was likely missed
The connection-type taxonomy was designed as data-model richness in Phase 5; every later feature (graph, suggestions, export) treats all six types as interchangeable edges.

Acceptance criteria

Motif detail shows certainty breakdown and any contradicted/contradicting entries.
A project-wide "open contradictions" view lists unresolved contradicts edges.
(If added) a contradiction can be marked resolved with a note.

From the 2026-07-15 codebase audit - Fable feature-ideation pass. Companion report: docs/.internal/report-2026-07-15.md (gitignored).

**Feature idea** (Fable ideation, rank #2) · **Effort:** S · **Value:** High **Pitch** A per-motif "how solid is this?" panel: contradicted entries, certainty mix, and unresolved `contradicts` edges - plus a project-wide list of open contradictions. **Why it matters** The app records `certainty` (`confirmed`/`likely`/`speculative`, `002_entries_tags_audit.sql`) and typed `contradicts` connections (`005_motifs_connections.sql`) - but *nothing consumes those semantics*. A motif resting on 14 speculative entries and 2 contradicted ones should look different from one built on confirmed observations, especially before it's published. This is the difference between a note pile and a defensible research claim. **How it fits** Pure read-side: new endpoints in `api/src/routes/analytics.ts` (today only counts/prevalence/co-occurrence) joining `connections WHERE type='contradicts'` with `entry_motifs` and `entries.certainty`, scoped by `ACTIVE_PROJECT_SQL` (`lib/projectAccess.ts`). Optionally a `resolved_at`/`resolution_notes` column on `connections` so a contradiction can be closed with a verdict. Badge on motif detail and (opt-in) public motif pages (`routes/public.ts`). **Why it was likely missed** The connection-type taxonomy was designed as data-model richness in Phase 5; every later feature (graph, suggestions, export) treats all six types as interchangeable edges. **Acceptance criteria** - [ ] Motif detail shows certainty breakdown and any contradicted/contradicting entries. - [ ] A project-wide "open contradictions" view lists unresolved `contradicts` edges. - [ ] (If added) a contradiction can be marked resolved with a note. --- _From the 2026-07-15 codebase audit - Fable feature-ideation pass. Companion report: `docs/.internal/report-2026-07-15.md` (gitignored)._

claude-bot added this to the v10.0.0 - Research workflow enhancements milestone

2026-07-15 20:35:36 +00:00

claude-bot added the

enhancement

label

2026-07-15 20:35:36 +00:00