Every phase. Every deliverable. One map.

Scope the problem, screen for regulatory applicability, and commit to a documented business case before any design work begins.

Source, assess, and document the data this system will actually run on — quality, bias screening, and provenance and lineage, before a single feature is engineered.

Turn the approved business case into an architecture — schematics, tech stack, API contracts, and the human-oversight design that can't be retrofitted later.

Build, train, and document the model — with a full record of what was tried, what was kept, and why.

Independently prove the system works — functional, security, AI/model, and formal GxP qualification testing, all traced back to source requirements.

Go live — cutover, readiness confirmation, and hypercare, approved as one plan before any of it starts, alongside the regulatory documents that must exist before the system is placed in use.

Hypercare stabilizes the system after go-live; from there the phase keeps governing for as long as it runs — monitoring, periodic review, change control, and incident response, with revalidation triggered when change warrants it.

Governance, risk, and compliance documents that span the whole lifecycle rather than belonging to a single phase — plus Retirement, run as its own dedicated track when a system reaches end of life.