drive-recovery-2026-05
Cross-vendor batch view for May 2026. Drives flow first to dtown-tech (local, default tier — triage + wrangling) who catalogues which are extractable vs dead. A rare subset escalates to Data Recovery NJ (escalation tier — actual recovery on dead drives). Cohort routing from data-recovery-shortlist. Per-vendor activity (events, costs, outcomes) lives on each vendor's job page.
Batch context
- Opened
- 2026-05-29
- Project
- data-recovery · data-wrangling
- Cohort
- per data-recovery-shortlist
- Owner
- Dan
- Outcome target
- full catalogue of which drives are extractable; recovered data from drives worth recovering
Vendors in this batch
Disposition vocabulary
Each drive carries a disposition code on the handoff PDF + faceplate label. New-hope-guy reads it and acts without needing to call. Dan pre-sets planned based on what he knows; dtown-tech logs called after triage (they may differ — the gap is the diagnostic).
- TRIAGE
- Initial classification action. Every drive starts here on arrival.
- MINE
- Drive spins, reads cleanly. Pull the data, full extract.
- RESCUE
- Struggling drive. Recover what's recoverable; partial extract OK; spend extra cycles if value warrants.
- PRUNE
- No value or already extracted elsewhere. Destroy or return as-is. Don't waste cycles.
- TRANSFER-OUT
- Escalate to Data Recovery NJ (or backup tier). Drive is worth the deep-recovery cost.
Items
| Item | Identity | Current vendor | Planned disposition | Called disposition | Date out | Date back | Outcome |
|---|---|---|---|---|---|---|---|
| seed-drive-01 | 2TB · WD Elements | dtown-tech | TRIAGE → MINE | — | |||
| seed-drive-02 | 4TB · Seagate Backup Plus | dtown-tech | TRIAGE → MINE | — | |||
| seed-drive-03 | 1TB · LaCie Rugged | dtown-tech | TRIAGE → TRANSFER-OUT | — |
All items start at dtown-tech with TRIAGE as the first action. The planned disposition is the call Dan expects; the called disposition is what dtown-tech decides after the physical inspection. Mismatches are evidence to refine the pre-handoff process next batch.
Handoff package
What ships with the drives to dtown-tech — printed together as one package per the "unify artifacts that travel together" pattern from print.gf.cx:
- Cover letter — job summary · contact · return address · billing notes
- Drives manifest PDF — this page rendered for print, vendor copy and Dan copy
- Per-drive faceplate labels — small-rigid label per drive with QR (→ id.gf.cx/<slug>) + disposition code + slug
- Disposition vocabulary card — single-page legend the vendor pins next to the work bench
Print bundle: → open print package — 4-page A4 layout (cover · manifest · disposition legend · faceplate labels with QRs). Browser Print → Save as PDF produces the handoff document.
Routing rules
- Default path: all drives ship to dtown-tech for triage + wrangling. Most items finish here.
- Escalation trigger: drive is non-functional AND the data is worth professional recovery (rare per drive · evaluate per-item).
- Escalation hand-off: dtown-tech returns the dead drive; Dan ships it on to Data Recovery NJ with a fresh manifest entry referencing both jobs.
- Backup tier: from shortlist, held in reserve if dtown-tech can't take the volume or Data Recovery NJ can't take a rare drive.
- Replace placeholder drive records with real S/N + capacity + spin-state guess
- Register drive slugs in
~/Code/id-gf-cx/manifest.json+ deploy id-gf-cx - Print drive-faceplate labels (print.gf.cx, new tier) encoding id.gf.cx URLs
- Create
pa.gf.cx/contractors/dtown-tech/page +/jobs/drive-triage-2026-05/ - Create
svc.gf.cx/dtown-tech/stream - Data Recovery NJ contractor + job pages can be deferred until first escalation
Closing notes
Populated when the batch closes. Will include: count extractable vs dead, recovered/lost outcomes per escalation, vendor performance vs shortlist expectations.