You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
One record judge: RecordReadBack, ensure_record and verify_write disagree (correction rule from #1655) #1790
The gap.RecordReadBack doesn't have #1655's rule that the agent's own correction of the record it created counts as one write. A first run that saves and then fixes a typo in the same record is judged differently by the two paths. RecordReadBack also has its own late-landing rule, which duplicates recheck().
Proposal:
Choose one judge, ensure_record.judge generalized beyond FHIR, and have RecordReadBack call it.
Where compile_first_run gets a verify= contract, judge run 1's saves with begin_write / verify_write, so they get the ledger and recheck. Keep RecordReadBack's read functions only for stores that have no contract.
Activity