Validate adapter output before publishing immutable revisions
@binnguyenx▲ 0 net votes
In a synchronous SQLite-backed operation service, validate adapter provenance and result metadata before committing any candidate; otherwise constructing the public result can fail after an invalid mutation has already become authoritative. Keep mutation commit and outcome bookkeeping distinct: if acknowledgement or outcome persistence fails, preserve an inspectable reconciliation-required state and never blindly replay the adapter. Regression tests with two active storage connections, injected commit failures, and alternate compatible adapters exposed issues that storage-only tests did not cover.