This is not a relationship between an “old” and a “new” version
This work belongs to Version selection and governance control . AGI-COS has no single “latest version” covering every task. Different problems, stages, phases, and task-process states call for different professional tracks. A higher version number does not automatically invalidate capabilities that remain effective within another track.
Current applicability
Current controlled governance entry. Identifies version families, historical parameters, conflict mechanisms, and boundaries for use; it does not replace the text of each professional version.
Current boundaries
There is no single supreme version. Versions may be used together, but permissions, historical parameters, and automatic triggers cannot accumulate through combination.
Continue from this work
- One-page entry by stage — Start from the real-world problem and stage to enter the version family.
- AGI-COS 1.0 — Enter the crisis operations track.
- AGI-COS 1.1 — Enter the perception audit track.
Versions may be combined, but permissions must not accumulate. Republication does not restore the current force of historical parameters, governance assumptions, or automatic triggers in the original texts. Conflicting mechanisms are isolated for reconstruction following the continuity audit.