Upgrading

Upgrading an adopted project

The checked-in upgrade guide is the detailed migration reference. Establish the intended checkout and local changes, preserve a recoverable copy, and review the changes before merging.

From 1.1.0 to 1.2.0

Preserve project configuration, task IDs/history, registry, Global context, Master Plan, project memory, worker notes, and session checkpoints. Merge new tooling and guidance around those records. Add the blank WORK/FOCUS.json only if absent. If the project already owns a hand-written CURRENT.md, retain it as a dated checkpoint before adopting the new generated view and review its links.

Then run:

bash .SYSTEMX/SYSTEMX.sh refresh-work
bash .SYSTEMX/SYSTEMX.sh validate

Select the existing objective and task IDs with focus, optionally linking the preserved checkpoint. Inspect context --agent agent.0. The task schema remains version 1 and no renumbering is required. The validator now also checks history chronology and consistent current fields; reconcile old manual edits against their original evidence instead of fabricating timestamps or erasing history.

Use ordinary validate for real project records. The public --template check should reject a populated project.

Other layouts

Older projects may have different directories, identifiers, receipt formats, controllers, and domain-specific acceptance rules. This CLI is not a lossless importer for those systems. Preserve the existing authority and original IDs while adopting useful written guidance. Any later migration needs a reviewed mapping that retains dependencies, original evidence, and unfinished obligations.

Keep project-specific extensions in their chosen directories and reference them from Global context. A template update should not introduce another editable completion ledger, copy historical private memory, or overwrite active runtime data.