sovereign-sync

To sync a local git repository without losing customizations, the workflow diffs files against HEAD and categorizes changes as FRAMEWORK, SEEDED, or USER. This classification allows you to selectively review and apply upstream updates while preserving your personalized vault configurations.

The best way to review upstream framework updates is to run a diff check that categorizes changes into FRAMEWORK, SEEDED, and USER groups. This prompts per-file review, ensuring you only apply approved updates to your local repository.

Categorizing git diffs as FRAMEWORK, SEEDED, or USER helps repository sync by creating clear decision points for each file. It separates core upstream updates from seeded templates and personal user changes, guiding safe and selective application.

Yes, you need a configured upstream remote and a local vault path to review and apply selective git updates. The workflow requires this remote to fetch changes and run the node-based scripts that perform the check, diff, and apply operations.

Yes, you can use node-based scripts to automate a monthly git workflow sync. The scripts perform check, diff, and apply operations on demand, allowing you to compare your local vault against the upstream remote and apply categorized updates safely.

When applying upstream framework updates, your SEEDED and USER files are protected through the categorization process. The workflow reads the diffs, identifies these personalized changes, and prompts you for per-file review so you can skip or selectively apply updates.