Resource

What a recoverability audit covers

A recoverability audit is the bounded assessment Shipward uses before recommending hardening work. It answers whether the codebase is recoverable, where the risk is concentrated, and what the next step should be.

Inputs

  • Repository source via GitHub or an approved .zip archive.
  • Context about goals, constraints, deployment posture, and current pain points.
  • Supporting docs that help clarify architecture, delivery risk, or business criticality.

Outputs

  • Recoverability decision: A direct recommendation on whether to recover, contain, rewrite, or treat the repo as unsupported.
  • Risk inventory: A map of the risky areas, fragile workflows, and delivery bottlenecks that are driving current incidents or release anxiety.
  • Architecture and delivery-readiness summary: A plain-English summary of the current system shape, boundary problems, and how ready it is for safer change.
  • Test and deployment gap analysis: An evidence-backed view of what is missing in verification, release discipline, and rollback safety.
  • Fixed-scope remediation estimate: A bounded quote for the smallest credible next slice when recovery is still honest.
  • Evidence bundle: Findings, assumptions, exclusions, and proof references tied to the current repo and engagement scope.