Roadmap and status

Roadmap and status

Four phases. Status is taken from what exists in the repository: "draft" means written but not reviewed, "skeleton" means the structure and clause map exist, and nothing is called complete before its review. This table mirrors the roadmap in the README; a status changes here only when the owning work product changes its document-control header.

Phase	State
1 · Foundation	Active
2 · Safety engineering	Active
3 · Build and verify	Planned
4 · Validate and release	Planned

Where each phase stands

Phase	Work	Status
1 · Foundation	Assurance strategy, safety plan, confirmation measures, regulatory strategy	Draft
	Baseline gap assessment, GAP-01…GAP-36	Draft
	Work product register, process model, decision register	Draft; checked by CI
	Project plan, QA plan, risk register, cybersecurity and ML plans, upstream and supplier management, impact analysis, capability baseline	Skeleton
	Living Safety Case records and dashboard	Draft: records at BL-001, validated and drawn by CI
2 · Safety engineering	Item definition, operating envelopes, risk assessment, safety functions and PLr, human-robot interaction and misuse	Draft, seeded from the concept-phase package
	Risk reduction concept, insufficiency analysis, cybersecurity threat assessment, ML component definition	Skeleton
	Test operations hold point	Draft; the bench safety hardware waits on the lead (DQ-006)
3 · Build and verify	Bench safety hardware, the forked software and its safety layer, chain architecture, stopping and separation budget and PL calculation, stopping and holding tests, fault injection	Planned
4 · Validate and release	Safety validation, assessment, technical documentation, release record, field monitoring	Planned

What the next gate needs

G0 needs the plans approved, the roles assigned and configuration control running. Today every plan is a draft or a skeleton, the verification reviewer and QA roles are open, and the software that moves the arm is not yet forked and pinned (DQ-007). The generated G0 readiness section lists what is missing, and the G0 gate skeleton is the pre-filled review record. The questions that wait on the project lead are in the decision register; the ones that shape everything below G0 are which arm to assess first, the regulatory frame, whether to fork the software, and the assessor.

Sources

• README, Roadmap
• WP-M-00 work product register: every work product, its gate and status
• WP-M-01 §7: phases, gates and hold points