You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(graph): require evidence on manual concept creation, add evidence endpoint
Manually created concepts were born with zero evidence instances, making them
ungrounded. Now evidence_text is required when creating concepts via API/CLI/MCP
(except match_only mode and LLM extraction). Evidence is stored as an Instance
node linked to the concept's synthetic source.
Also adds:
- POST /concepts/{id}/evidence endpoint for adding evidence to existing concepts
- add_evidence action on the MCP concept tool
- evidence_text parameter on the MCP graph tool (create concept + queue)
- Missing @types dev deps that were causing pre-existing TS build failures
description: 'Operation: "details" (get ALL evidence), "related" (explore neighborhood), "connect" (find paths), "add_evidence" (attach evidence text to a concept)',
447
447
},
448
-
// For detailsand related
448
+
// For details, related, and add_evidence
449
449
concept_id: {
450
450
type: 'string',
451
-
description: 'Concept ID (required for details, related)',
451
+
description: 'Concept ID (required for details, related, add_evidence)',
452
+
},
453
+
evidence_text: {
454
+
type: 'string',
455
+
description: 'Evidence/rationale text to attach to a concept (required for add_evidence, min 10 chars)',
452
456
},
453
457
include_grounding: {
454
458
type: 'boolean',
@@ -1064,6 +1068,7 @@ Queue executes sequentially, continues past errors by default (set continue_on_e
thrownewError('evidence_text is required when creating a concept (min 10 characters). Provide the rationale or supporting evidence for why this concept exists.');
0 commit comments