Conversion
Packages conversation files. Do it yourself in the Archive & Evidence Studio, or request a human-checked archive. No content truth review either way.
Human archive review and project rescue. Routine preservation belongs to the Archive & Evidence Studio; this pathway is for work that needs judgment, from human-checked packaging through shallow diagnosis, evidence review, and controlled technical review. Each level answers a different question.
Packages conversation files. Do it yourself in the Archive & Evidence Studio, or request a human-checked archive. No content truth review either way.
Inventories gaps, complexity, and the responsible next tier.
Human review classifies documented, unsupported, contradictory, reproducible, and unknown items.
Implements agreed corrections only after diagnosis.
A person checks and validates the packaged archive when you want more than software output.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place.
Best for: Clean supported exports where someone needs a human to confirm the package is sound before relying on it.
Scope boundary: Bounded limits confirmed at preflight. Manual archive jobs are capped at 12 in the first full year.
Next step: Request a Readiness Scan if the archive turns out to be mixed or unclear.
The same human-checked packaging for a larger clean export, quoted after a compatibility preflight.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place.
Best for: Larger archives that are still clean and in a supported format.
Scope boundary: Quoted after preflight. Counts toward the 12 manual archive jobs available in the first full year.
Next step: Move to a Readiness Scan if the preflight shows mixed or damaged sources.
Best-effort reconstruction when an export is malformed, copied, mixed, or incomplete.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place.
Best for: Archives that failed a normal conversion, or sources assembled from several places over time.
Scope boundary: Best effort only, quoted after a paid preflight. Some sources cannot be recovered.
Next step: Decide, with the preflight in hand, whether recovery is worth doing at all.
A bounded diagnostic that tells you what shape your archive is actually in before anything larger.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place.
Best for: Projects where nobody can currently say what exists, what is current, or what conflicts.
Scope boundary: Bounded scope with a 2.5-hour internal cap. Limited to 15 scans per year while labor data is being validated.
Next step: Escalate to an audit only if the scan shows evidence problems that justify it.
A small, document-only first review offered at a founding price to build published case evidence.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place. Three founding openings only.
Best for: Small document-only projects willing to become a sanitized case study.
Scope boundary: Three external openings only, then retired or repriced. No code execution.
Next step: Move to a Core Rescue Audit if the review shows the project needs full evidence work.
The main evidence-led diagnostic: what is documented, unsupported, contradictory, reproducible, or still unknown.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place.
Best for: Projects where decisions have been made on an unclear record and someone needs to know what holds up.
Scope boundary: Bounded scope confirmed at intake. Founding pricing is limited and ends by condition, not by date.
Next step: Choose a decision sprint, a recovery sprint, or no further work at all.
Turns a reviewed record into one clearly documented decision with its evidence and alternatives.
Opens in stages
Opens in stages. Human archive work begins only after service and data terms, insurance, secure transfer, retention and deletion procedures, and independent QA are in place. Referral or follow-on only.
Best for: Teams stuck on a single consequential decision: continue, repair, rebuild, publish, or stop.
Scope boundary: One decision and one evidence set, both fixed at the start.
Next step: Proceed to implementation only if the decision calls for it.
Adds controlled execution and reproducibility review for code-heavy projects.
Opens in stages
Opens last. Technical work begins only after isolated execution controls, an approved-command policy, insurance review, and a signed independent technical reviewer are all in place.
Best for: Projects where generated code runs inconsistently or documentation conflicts with the repositories.
Scope boundary: Bounded repositories and source lines, confirmed at technical intake. Unexecuted code is never described as working.
Next step: Move to a recovery sprint if the audit produces a repairable backlog.
Duplicate matches, contradiction flags, unsupported claims, or anomalous files begin as candidates. Reports distinguish candidates from human-reviewed conclusions.
Secure archive transfer follows scope approval, agreement, and payment. The public form is for scope descriptions only.
A shallow diagnostic protects everyone from mis-scoping a mixed archive.