Record the generic project-family and cross-domain lifecycle model, including the rule that SCAD, Java, embedded and future domains should keep lifecycle naming/evidence/output structure equivalent where practical without forcing identical build mechanics.
Also correct the new Migration-006 documents so each starts by explaining why the document exists and when to use it.
With explicit user approval, use this documentation/status update to activate Migration 006 in parallel with the final non-conflicting Migration-005 SCAD library release closeout. Java implementation starts only in tool.java-project; template.java-project and 2026-010-02.java.event-timing-framework remain later qualification consumers.
Record the generic project-family and cross-domain lifecycle model, including the rule that SCAD, Java, embedded and future domains should keep lifecycle naming/evidence/output structure equivalent where practical without forcing identical build mechanics.
Also correct the new Migration-006 documents so each starts by explaining why the document exists and when to use it.
With explicit user approval, use this documentation/status update to activate Migration 006 in parallel with the final non-conflicting Migration-005 SCAD library release closeout. Java implementation starts only in
tool.java-project;template.java-projectand2026-010-02.java.event-timing-frameworkremain later qualification consumers.