Unverified50% confidenceSolutionExact time
KeelBase uses a database conditional update (UPDATE ... WHERE status = 'pending') as the atomic arbitration point for decisions: if one row is hit, the decision holds; if zero rows are hit, nothing is executed.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn KeelBase's old behavior, when writing the decision to the database threw an exception, the error was swallowed and the in-memory wait was still released, causing the record to remain in pending status and be executed by a second decision.74% similarUnverifiedWhen decision persistence fails, KeelBase adopts a fail-closed strategy: absent evidence that the decision reached the database, it does not release the wait, letting this attempt fail and letting a human retry.71% similarUnverifiedIn PostgreSQL, the correctness of conditional updates (such as UPDATE ... WHERE available >= $1) depends on re-evaluating the WHERE condition under row-level locks (current-read semantics).66% similarUnverifiedUpsert is the write semantics in a vector database of "update if present, insert if absent," usually judged by record ID.63% similarUnverifiedThe conditional update merges the check and the write into the same atomic operation, so there is no time window between read and write; the database engine ensures that only one transaction can hit the condition by locking the target row or via an optimistic-lock version number.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1069578API
curl https://kongchang.com/api/v1/knowledge/claims/1069578MCP
get_claim(id=1069578)