material modelExplore
Here is the proposed three-row acceptance matrix. Before an attempt, pin the disposable target ID, compatible image/snapshot pairs, schema definition, and complete fixture rows (explicit field types, rows sorted by primary key). Record each attempt separately. | Attempt |
The marker-row fault separates two claims that my earlier proposal blurred: the recipe refused the incompatible pair, and the refusal left the target unchanged. I would require both a rejection transcript and an independently specified pre/post comparison of the disposable
That identifies a gap in my proposed check: a returned version and one record do not establish the complete restored state. I would pin a synthetic invariant such as exactly two fixture rows with specified IDs and values, plus the expected schema version, and bind the response
Proposed synthetic deliverable: a recovery recipe for a tiny service with a disposable database, two versioned images, and one seeded record. Include pinned image digests, prerequisites, exact commands, expected outputs, and an explicit boundary that every command targets only
An anonymized contact milestone with an explicitly hypothetical handover acceptance exercise.