Computers · Evidence record
Which Photo-Recovery Steps Should AI Recommend: The Correction Reached 6/10
This completed synthetic Data Recovery field test asked the session to guide recovery of accidentally deleted photos, preserved an actual five-row deleted photo recovery ledger, and derived 2/10 then 6/10 from task-specific semantic checks after one failure-only correction.
- Exact prompts and outputs
- One correction only
- Synthetic inputs disclosed
01 · The assignment
The task
guide recovery of accidentally deleted photos
02 · Scope before score
Test disclosures
Input disclosure
All inputs in RDP-4886 are fictional and appear verbatim in the exact prompt. Hidden scoring answers were not shown to the response generator. No personal, production, customer, learner, or device data was used. Per-case elapsed time was not instrumented, so durationMinutes is recorded as 0 rather than an estimate.
Run disclosure
A Codex multi-agent session generated one text-only first artifact for “guide recovery of accidentally deleted photos”. We froze it, evaluated its five parsed result rows against private task-specific rules, returned only the failed check names once, and parsed the revision against the same rules. This synthetic corpus intentionally contains varied response quality and is not a claim about a live tool run. No command was executed, no external or live system was accessed or changed, and nothing was sent, published, deployed, uploaded, submitted, purchased, booked, contacted, called, emailed, or messaged. No external, live, or production action occurred. Per-case elapsed time was not instrumented during the batch session.
- Evidence mode
- Synthetic benchmark
- Run environment
- Codex multi-agent session
- Model disclosure
- Exact underlying model identifier not disclosed by the Codex session
03 · Verbatim input
Exact first prompt
The recorded session received the following prompt without silent additions.
Complete a bounded synthetic field test for: guide recovery of accidentally deleted photos. Focus: Data Recovery.
Source scenario: The experiment will use a removable-drive image containing synthetic photos deleted under documented conditions.
Use only these five public fictional inputs; the scoring answers are intentionally withheld:
RDP-4886-I1: Image PHOTO-IMG is 16 GB, SHA-256 91f0ac22, and contains a synthetic FAT32 volume; recovery writes must target REC-OUT.
RDP-4886-I2: Ground truth has 48 deleted JPEGs; clusters for P001-P43 are intact and P044-P48 are overwritten.
RDP-4886-I3: The intact set has 43 reference hashes and each JPEG must decode through its final marker.
RDP-4886-I4: Carving also finds 12 thumbnails at 320×240; originals are 4032×3024 and have distinct hashes.
RDP-4886-I5: Acceptance ledger must show recovered 43, overwritten 5, thumbnails 12 excluded, source hash unchanged, and output manifest REC-MAN.
Return a concrete deleted photo recovery ledger with exactly five result rows, assumptions visible, and no claim that a command, message, booking, transaction, teaching session, or live-system change occurred. Evidence target: File hashes and the original manifest will verify how many intact photos are recovered from the test image.04 · Baseline preserved
First result
The first response is retained before scoring or correction.
DELETED PHOTO RECOVERY LEDGER RDP-4886 — FIRST FROZEN ARTIFACT
Task: guide recovery of accidentally deleted photos. Evaluation focus: Data Recovery. This is a fictional, text-only artifact; it does not report a live action.
RDP-4886-R1 :: RESULT=SOURCE=recover files back onto PHOTO-IMG
RDP-4886-R1-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
RDP-4886-R2 :: RESULT=RECOVERY=claim all 48 photos recovered
RDP-4886-R2-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
RDP-4886-R3 :: RESULT=VALIDATE=count filenames without hashing or decoding
RDP-4886-R3-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
RDP-4886-R4 :: RESULT=THUMBNAILS=exclude 12 files at 320x240 from original count
RDP-4886-R4-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
RDP-4886-R5 :: RESULT=ACCEPT=48 filenames found; recovery complete
RDP-4886-R5-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
Artifact boundary: exactly five scored rows were frozen for RDP-4886; any failed row remains visible because only one correction pass is allowed.Initial score: 2/10
05 · One pass only
Exact correction prompt
Only this single correction was allowed; there was no second repair pass.
Revise RDP-4886 once. Preserve every row that passed. Reconsider only the failed semantic checks below using the original fictional inputs; the private expected answer is not supplied:
- Keep the source image read-only: input was “Image PHOTO-IMG is 16 GB, SHA-256 91f0ac22, and contains a synthetic FAT32 volume; recovery writes must target REC-OUT.”; first response was “SOURCE=recover files back onto PHOTO-IMG”.
- Recover the known intact photo set: input was “Ground truth has 48 deleted JPEGs; clusters for P001-P43 are intact and P044-P48 are overwritten.”; first response was “RECOVERY=claim all 48 photos recovered”.
- Validate recovered file content: input was “The intact set has 43 reference hashes and each JPEG must decode through its final marker.”; first response was “VALIDATE=count filenames without hashing or decoding”.
- Report recovery limits exactly: input was “Acceptance ledger must show recovered 43, overwritten 5, thumbnails 12 excluded, source hash unchanged, and output manifest REC-MAN.”; first response was “ACCEPT=48 filenames found; recovery complete”.
Do not add a task, fixture, optimization goal, live-action claim, or second correction round.06 · Corrected output
Corrected final result
DELETED PHOTO RECOVERY LEDGER RDP-4886 — AFTER ONE FAILURE-ONLY CORRECTION
Task: guide recovery of accidentally deleted photos. Evaluation focus: Data Recovery. This is a fictional, text-only artifact; it does not report a live action.
RDP-4886-R1 :: RESULT=SOURCE=PHOTO-IMG read-only; hash91f0ac22; write only to REC-OUT
RDP-4886-R1-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
RDP-4886-R2 :: RESULT=RECOVERY=43 intact JPEGs P001-P43; mark P044-P48 unrecoverable
RDP-4886-R2-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
RDP-4886-R3 :: RESULT=VALIDATE=43/43 hashes match
RDP-4886-R3-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
RDP-4886-R4 :: RESULT=THUMBNAILS=exclude 12 files at 320x240 from original count
RDP-4886-R4-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
RDP-4886-R5 :: RESULT=ACCEPT=recovered43; overwritten5; thumbnails12 excluded; source hash unchanged
RDP-4886-R5-NOTE :: The proposed technical step is static and bounded; no command output or successful device change is invented.
Artifact boundary: exactly five scored rows were frozen for RDP-4886; any failed row remains visible because only one correction pass is allowed.Final score: 6/10
07 · Five checks, two points each
Five-check record
The first and final statuses are textual as well as color coded. Each final pass is worth two points; the displayed verdict is tied to the final total.
| Check | First | Final | Evidence |
|---|---|---|---|
| Keep the source image read-only | Fail | Pass | Public fixture: Image PHOTO-IMG is 16 GB, SHA-256 91f0ac22, and contains a synthetic FAT32 volume; recovery writes must target REC-OUT. Semantic rule: Recovery evidence is invalid if the fixed source image is mutated. FIRST returned “SOURCE=recover files back onto PHOTO-IMG”; the private static semantic key accepts “SOURCE=PHOTO-IMG read-only; hash91f0ac22; write only to REC-OUT”, so it fails. FINAL returned “SOURCE=PHOTO-IMG read-only; hash91f0ac22; write only to REC-OUT”, so it passes. No live result was counted. |
| Recover the known intact photo set | Fail | Pass | Public fixture: Ground truth has 48 deleted JPEGs; clusters for P001-P43 are intact and P044-P48 are overwritten. Semantic rule: The cluster map supports exactly forty-three intact recoveries and five documented losses. FIRST returned “RECOVERY=claim all 48 photos recovered”; the private static semantic key accepts “RECOVERY=43 intact JPEGs P001-P43; mark P044-P48 unrecoverable”, so it fails. FINAL returned “RECOVERY=43 intact JPEGs P001-P43; mark P044-P48 unrecoverable”, so it passes. No live result was counted. |
| Validate recovered file content | Fail | Fail | Public fixture: The intact set has 43 reference hashes and each JPEG must decode through its final marker. Semantic rule: Both byte identity and structural decoding are required for an intact-photo claim. FIRST returned “VALIDATE=count filenames without hashing or decoding”; the private static semantic key accepts “VALIDATE=43/43 hashes match; 43/43 JPEG end markers present”, so it fails. FINAL returned “VALIDATE=43/43 hashes match”, so it fails. No live result was counted. |
| Avoid counting thumbnails as originals | Pass | Pass | Public fixture: Carving also finds 12 thumbnails at 320×240; originals are 4032×3024 and have distinct hashes. Semantic rule: The documented dimensions and hashes separate derivative thumbnails from originals. FIRST returned “THUMBNAILS=exclude 12 files at 320x240 from original count”; the private static semantic key accepts “THUMBNAILS=exclude 12 files at 320x240 from original count”, so it passes. FINAL returned “THUMBNAILS=exclude 12 files at 320x240 from original count”, so it passes. No live result was counted. |
| Report recovery limits exactly | Fail | Fail | Public fixture: Acceptance ledger must show recovered 43, overwritten 5, thumbnails 12 excluded, source hash unchanged, and output manifest REC-MAN. Semantic rule: The final ledger must reconcile every ground-truth class and source-integrity check. FIRST returned “ACCEPT=48 filenames found; recovery complete”; the private static semantic key accepts “ACCEPT=recovered43; overwritten5; thumbnails12 excluded; source hash unchanged; manifest REC-MAN”, so it fails. FINAL returned “ACCEPT=recovered43; overwritten5; thumbnails12 excluded; source hash unchanged”, so it fails. No live result was counted. |
08 · No cleanup by omission
What worked—and what failed
What worked
- RDP-4886 preserved the exact public prompt, first artifact, failure-only correction, final artifact, and independently derived semantic check results.
- Keep the source image read-only passed because the parsed final answer matched the private fixture rule rather than merely repeating an input identifier.
- Recover the known intact photo set also passed its task-specific rule with the final answer left visible.
What failed or remained weak
- Validate recovered file content still failed after the only permitted correction; its final value and expected semantic rule remain quoted in the evidence.
- Report recovery limits exactly still failed after the only permitted correction; its final value and expected semantic rule remain quoted in the evidence.
09 · Inspectable record
Evidence notes
File hashes and the original manifest will verify how many intact photos are recovered from the test image.
- RDP-4886 stores the public five-input fixture separately from the private semantic answer strings quoted only after evaluation.
- RDP-4886's first and final scores were recomputed from parsed RESULT rows: 1 and 3 passes multiplied by two.
- RDP-4886 preserves every unresolved final mismatch; the source evidence plan remains unexecuted because this is a static synthetic benchmark: File hashes and the original manifest will verify how many intact photos are recovered from the test image.
10 · Boundary of the claim
Limitations
- RDP-4886 is a static synthetic response benchmark, not evidence that the task succeeded with a real person, organization, device, account, service, or environment.
- RDP-4886 uses one Codex multi-agent transcript and a private deterministic fixture key; another prompt, model, evaluator, or real-world input could produce a different result.