FAQ

Straight answers about the current Shipward scope

These answers reflect the current repo-backed launch posture and do not invent public claims outside the approved boundaries.

Is this only for AI-built software?

No. Shipward is for fast-built or under-engineered systems that now need reliability, clarity, and governed delivery.

What if my app is already live?

That is common. The first step is still the audit, so the next move is based on current risk rather than guesswork.

How do you decide whether to recover or rewrite?

By inspecting the codebase, delivery posture, and risk concentration, then reporting the most credible path with explicit reasoning.

Do you deploy into production?

Not in v1. Shipward is handoff-first, with governed follow-on work and explicit approval for risky actions.

What happens after the audit?

You receive the report, risk inventory, and scoped next phase. Governed hardening only starts if that next phase is approved.

Do I need to give full cloud access?

Not for the brochure stage. Access decisions belong to the governed delivery phase and stay bounded to the approved work.

Need a route-specific answer?

Use the service pages for the offer ladder, the supported-stacks page for intake limits, and the trust page for governance posture.