Approve or reject a detected edge
Changed onA curator decision on one supersedes edge. Other edge types are refused. validated lets the repeal retire the older fact and bypasses the Supported floor: a curator may let a weaker fact retire a stronger one. auto-approved (verification skipped, or the second pass passed) does not bypass that floor. rejected leaves the older fact current. The caller and the time are stored on the edge. Other fields of EdgeUpdate are refused: this is the decision, not an editor.
With verification skipped (the production default) a detected repeal is already auto-approved. When verification runs and rejects it, the edge stays pending, and a later rejection demotes an earlier auto-approved repeal to pending. A curator's validated or rejected is not overwritten. Pending repeals are listed on POST /pots/{pot_id}/query (edges_context.pending_supersedes) when edges are included. An auto-approved repeal the Supported floor or an axiom stops is listed as edges_context.blocked_supersedes (and on GET /edges as blocked_supersedes) with a reason, so a curator can still validated it past the floor. Saving a repeal also stores a contradicts edge in the same direction unless the pair already has one, so contradiction surfaces show the conflict.
Request
- Base URLhttps://api.scipot.ai (the document declares no server; this is the origin it was published from)
- Authnone declared
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Request body
Response
Edge updated
Changes
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info
- warning
added the new
restatesenum value to theresponse property for the response status - info
added the new
restatesenum value to the request property/ - info
added the optional property
to the response with the status
- warning