Memory conflict check
wever_memory-conflict-checkAgent Memory: submit a memory update flow: the rule for a new fact that contradicts a remembered one (when the contradiction is noticed: as the new fact is written, only when both are read, or never; which fact wins: what the principal stated over what was observed, inferred or imported, the principal decides, the newest, the oldest, or both stay; whether the principal is asked, told, only logged or not told; and whether the old fact is retired with its date, kept and marked superseded, deleted or kept as if current), plus optionally the contradictions seen, each with its subject, the old and new facts and their sources, which fact the agent now acts on, whether the principal heard and whether the old fact was retired. The signed report says which fact wins, whether the contradiction reaches the principal and whether the stale version is retired or silently kept, and names a contradiction never noticed, both facts kept, the oldest fact winning, the old fact kept as if current and, among the contradictions seen, every older fact that won, every pair left both current, every inference that replaced what the principal stated and every old fact left unretired, then noticing only on read, a principal not told, a deleted old fact with no trail and the newest fact always winning, with the fix for each. This reads contradictions between remembered facts: cached context that outlives a change at its source is wever_cache-staleness-check, where each memory came from is wever_memory-provenance-check and the agent’s view checked against the system’s record after an interruption is wever_state-reconciliation-check. Verdict stale_facts_win, conflict_gaps, conflict_unverified or conflicts_resolved. POST /api/memory-conflict-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-memory-contract. Human page: https://weverlabs.com/agent-memory/.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "wever_memory-conflict-check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| flow | No | The memory update flow, such as preference updates. | |
| rule | No | ||
| label | No | Optional name recorded in the report. | |
| conflicts | No | Contradictions seen, with which fact won. |