# Connected workflow evaluation: four checks
Reviewed 27 September 2026. This is an implementation/evaluation note, not a new benchmark.

Choose one question your application already answers. Record its expected answer, then use these checks:

| Check | Change | Inspect |
|---|---|---|
| Update | Correct one input | Answer, source version and derived-state refresh |
| Access | Remove permission | Actual read, alternate route and restored-state behavior |
| Evidence | Follow one conclusion | Exact source, relationship and derivation |
| Operations | Interrupt and recover | Records restored, manual work and remaining services |

Inspected 8DB source at revision d5d0f58e86064b410f1a0c424e9b7c1e06c545f2 includes the F3 record CRUD/batch checks, F5 blob lifecycle checks, F6 vector/spatial/DTW checks and F7 directed-edge/hyperedge round trips. These are distinct operations. The spatial/DTW examples are separate from the encrypted store examples; no uniform-protection or combined-workflow result is inferred. This editorial inspection did not execute those tests.

The application chooses domain identities, relevance, required authority and the acceptable recovery outcome. Count the work actually removed rather than only the number of products. A maintained specialist or extension may remain useful.

Use the separately published shipping-query methods for measured combined-query evidence: https://8braid.com/journal/j-9c61814e1125 . For a first discussion, send one non-sensitive question to hello@8braid.com; no diagram or data export is required.