STRANDS EVALS __SDK_VERSION__ / RECORDED STATE REVIEW
The mean improved.
One rule regressed.
The retry wrote the same note twice. Inspect the expected state beside both observed outcomes, using the native report’s case and evaluator identities.
Four saved scripted Docker cases · two deterministic state rules · no account, installation or model key needed to browse.
This is the equally weighted mean of eight native state-rule rows. EvalArc’s original 90% → 93.75% uses five weighted dimensions. These are different scoring scopes; the notes regression appears in both.
CASE + EVALUATOR / EVERY CHECK RETAINED
Find the change in the state.
ticket.notes compares the complete ordered list, including duplicates. ticket.status expects “closed” for a resolved ticket and “open” otherwise.
All __ROW_COUNT__ checks are available below. Expand a check to inspect its state.
KEEP THE EVIDENCE
A review you can hand off.
Download the HTML, both native reports and original EvalArc inputs together. Extract the ZIP and open strands-review/index.html; all checks and filters work offline.
Download Strands review (ZIP)This extracted review already contains the evidence files below.
Native report fingerprints
__SOURCE_HASHES__
Check links identify the case, evaluator and both native report files. File hashes establish content identity, not the identity of the producer.
The site build rechecks the saved rule outcomes against the original state. CI separately runs the real SDK with network attempts rejected. Neither process reruns an agent or calls AWS. Strands already includes per-row verdicts; this independent companion displays them.
Reproduce with the pinned SDK ↗ · Share a first-use finding ↗