A connector should recover without losing the authority change.
This bounded diagnostic tests reference connector behavior through restart, rejection, replay, and scoped change impact. It provides exact accounting for the tested path. Generalization across enterprise connectors remains outside the claim.
Recorded result
Restart safely. Reject bad events. Revalidate only what changed.
The diagnostic ran from clean installed wheels at the recorded source revision. All 15 declared checks passed.
Read-only SQL
100,000 / 100,000
Every fixture row was accounted for across a forced restart. No row was skipped or duplicated, and repeated processing produced the same result.
Signed event feed
100,000 / 100,000
Every signed event was processed under the recorded checks. Invalid signatures and stale events were rejected, while duplicate and out-of-order delivery remained safe.
Replay and impact
Exact
All 1,001 authority objects replayed to the same result. Change impact remained scoped, an unrelated workflow stayed current, and an affected prior decision returned to review.
What the run establishes
The reference path converged on the same governed state.
The recorded source path resumed after interruption, invalid events were rejected, and complete replay matched the original result. The change scenario remained scoped to affected governed use and returned a prior decision to review without changing an unrelated workflow.
Recorded resource envelope: 17.47 seconds, 116.812 MB peak process RSS, and no less than 69% system memory available on the test machine. These measurements describe this run only; they are not a production capacity or latency commitment.
The scale path scanned and normalized all 100,000 SQL rows and signature-verified and normalized all 100,000 signed events. A configured subset of 1,000 SQL records plus two adversarial event-feed updates exercised Authority State projection, replay, ordering, and impact. The 200,000-row input scale does not represent 200,000 end-to-end governed state transitions.
The public projection contains aggregate scope, verified properties, resource observations, a claim boundary, and a checksum manifest. Detailed samples, internal identifiers, schemas, implementation paths, and state representations remain outside the public site.