Resolve Conflict
resolve_conflictSettle a conflicting observation or relation by keeping or dropping it with a newer stamp, so every node adopts the decision as changes propagate.
Instructions
Settle an element that more than one machine has written: keep it or drop it with a stamp newer than anything in the log, so the decision wins on every node as the change propagates. Use it after read_conflicts named the element and you have decided how it should stand — re-creating it with the existing tools is not enough, because a write that already exists is skipped, and deleting what is already tombstoned changes nothing. An element that already stands as you ask is left untouched and reported as unchanged, because every write is durable history. An observation needs the entity to exist, and a relation both of its endpoints, exactly as when they were created.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"elements": "<elements>"
},
"name": "resolve_conflict"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| elements | Yes | One entry per element: an observation or a relation, and whether it stands |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |