Skip to content

Update Knowledge Edge

PATCH /knowledge-edges/{edge_id}

Confirm or reject a proposal, and record who ruled and when.

Confirming a contradicts relation demotes both items it touches, in the same request. A promoted claim that is now disputed must stop being served as settled, and “surface it in the health report and let somebody demote it later” is a design where the wrong answer is served for as long as the queue is (annex 10 §5.3).

Parameters

Name	In	Type		Notes
`edge_id`	path	string (uuid)	required	—

Request body — `KnowledgeEdgePatch`

Field	Type		Notes
`status`	`proposed` \| `confirmed` \| `rejected` \| null	optional	—
`criticality`	`low` \| `normal` \| `high` \| null	optional	—
`notes`	string \| null	optional	max length 2000

Responses

Status	Description	Body
`200`	Successful Response	`KnowledgeEdgeView`
`422`	Validation Error	`HTTPValidationError`

Example

curl -X PATCH https://your-deployment.example.com/knowledge-edges/{edge_id} \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — `KnowledgeEdgeView`

Field	Type		Notes
`id`	string (uuid)	required	—
`from_item_id`	string (uuid)	required	—
`to_item_id`	string (uuid)	required	—
`kind`	`part_of` \| `supports` \| `contradicts` \| `derived_from` \| `supersedes` \| `relates_to` \| `answers` \| `shares_topic`	required	—
`status`	`proposed` \| `confirmed` \| `rejected`	required	—
`criticality`	`low` \| `normal` \| `high`	required	—
`notes`	string \| null	required, nullable	—
`created_by`	`agent` \| `human` \| `maintenance`	required	—
`curated_by_id`	string (uuid) \| null	required, nullable	—
`curated_at`	string (date-time) \| null	required, nullable	—
`created_at`	string (date-time)	required	—
`updated_at`	string (date-time)	required	—