new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Temporal · all subjects

message-passing/updates

2 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Update mechanism for requesting changes with guaranteed processing

Updates are a message-passing mechanism that combines Signal and Query semantics. An Update has a validator phase (checked before acceptance) and a handler phase (execution guaranteed). In the approval pattern, the resubmit_document Update includes a validator that checks the update_id and new_content_url are non-empty, preventing duplicates by tracking processed update IDs and returning a duplicate flag if the same update_id is sent again. Updates allow idempotent resubmissions with full error feedback.

Duplicate update prevention using processed_update_ids set

The resubmit_document Update handler maintains a _processed_update_ids set to prevent duplicate resubmissions. When an Update arrives with the same update_id, the handler checks if update_id is already in the set and returns {"accepted": True, "duplicate": True, "reason": "Resubmission already processed"} without re-executing the resubmission logic. Only new update_ids are added to the set after processing. This provides idempotency at the Workflow level, complementing Activity-level idempotency.

Give your agent this brain