What you can say
All four required checks passed against the configured mocks, and the run recorded cleanup. The result is tied to the recorded revision and time.
Worked example · synthetic reference
What a useful result looks like.
This example comes from our retained API → function → table reference test on 17 October 2026. It uses synthetic mocks and is not a customer success story.
4 required checks passed
Configured behaviour confirmed.
Execution method: contract simulator. Original application code did not run. This historical example does not describe today’s AWS estate.
- Tested
- 17 October 2026, 17:06 UTC
- Workload revision
- 5
- Cleanup recorded
- Destroyed
- Evidence digest prefix
08b5a67a14ef
- Entry pointAPI GatewayConfigured to invoke the function.
- ApplicationLambda functionConfigured with write authority to the table.
- StateDynamoDB tableIncluded in the reviewed workload boundary.
| Check | Condition | Result |
|---|---|---|
| HTTP response is valid | Response contains status | Passed |
| Speed is acceptable | Measured simulator execution is below 1000 ms | Passed |
| Function returns success | Function result statusCode equals numeric 200 | Passed |
| Function returns JSON | Function result contains application/json | Passed |
What still needs proof
Original application execution, target compatibility, live dependencies, data migration, production latency, load, availability and cutover.
What to share
Carry the execution method and limitations alongside the outcome. The public JSON is a redacted teaching example, not a signed customer evidence bundle.
Download example JSON →Start with one workload you understand.
Request early access, then confirm coverage and the test you want before connecting a live environment.