01
Save
ConfirmedExpected
The record persists.
Observed
The record persisted.
Observation in a synthetic workflow
Does the workflow work after the form saves?
The record saved, but it did not appear in the connected list. After an edit added the delivery-date field, new records still did not participate in sorting.
01 / The finding
What the benchmark checked
A completed save was only the first check.
02
Read back
Gap observedExpected
The connected list shows the record.
Observed
The list omitted it.
03
Sort after editing
Gap observedExpected
New records sort by delivery date.
Observed
The field existed, but new records did not participate in sorting.
Scope: the tested renderer and synthetic fixtures.
- Save
Verify that the submitted record persists.
- Read back
Open the connected list and match the record by identity.
- Use
Check that the new record participates in sorting after the edit.
Question
Can a user complete a workflow from submission through to finding and using the new record?
Method
The Allegory benchmark used a synthetic browser workflow. The checks followed a valid form submission through to the connected list and then exercised an edit that introduced a delivery date.
Observation
The record persisted after the save, but the connected list omitted it. After the edit, the delivery-date field existed, but new records still did not participate in sorting.
Limits and next check
These observations cover the tested renderer and fixtures. They do not establish a model ranking. A follow-up should seed a known record, submit a new one, reload the connected view and assert both record identity and sort position.
Source study · Allegory benchmark, 26 and 27 October 2026
Evidence and next check
Public evidence review is pending. Repeat the check with a seeded record, then reload the list and verify the new record’s identity and sort position.