القائمة
Use when syncing your local ecosystem against the upstream Sovereign Ecosystem repo to review framework changes file by file and apply only what you approve.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when running the weekly intelligence review. The AI briefs each engagement from live ecosystem data, the Sovereign speaks freely across 3 this-week and 2 next-week engagements, and the session closes with a Sovereign Command update.
Use when starting a session to initialize the AI interface with continuity checks, a live ecosystem orientation and approval-gated support sweep before any session work begins.
Use when archiving several ecosystem artifacts at once with per-artifact approval gates before any vault move executes.
Use when checking for published updates from the Sovereign Ecosystem GitHub repo and selectively applying only what you explicitly approve.
Use when a long-form manuscript (book chapter, ebook, multi-chapter playbook, long-form digital product) needs an editing pass to identify and remove AI writing tells against the Anti-AI Writing Patterns Codex. Triggered by the Sovereign after draft completion, by a Pending Plan handover map naming this skill at the edit phase, or by any post-draft state where AI-assisted prose needs the anti-pattern sweep before final review.
Use when updating a Pending Plan mid-arc with breadcrumbs, applicability changes, partial implementation notes and reconciliation-ready context.
| name | sovereign-sync |
| description | Use when syncing your local ecosystem against the upstream Sovereign Ecosystem repo to review framework changes file by file and apply only what you approve. |
| status | active |
| tier | foundational |
| contrast_tier | 1 |
Purpose: Keep your ecosystem current with upstream improvements while leaving your personalized surfaces untouched.
Trigger: Run whenever you want to check for upstream changes. Monthly is a reasonable default, or whenever an update note surfaces.
Inputs: Local git repo with an upstream remote configured. scripts/framework-manifest.json for path classification.
Outputs: A reviewed change list, applied files for approved items, a git commit bookending the sync.
Related: scripts/se-update.mjs (the underlying tool this skill orchestrates). scripts/framework-manifest.json (path classification authority).
Commit any unsaved work in your vault. The sync applies upstream files via git checkout, which stages changes in your working tree. A clean working tree makes the diff readable and the commit unambiguous.
git -C "<your-vault-path>" status --short
If anything is uncommitted, commit or stash it first.
node scripts/se-update.mjs --check
The script:
If no upstream remote is configured, the script prints the one-line fix and exits. Run that command, then re-run --check.
The output groups changes into three classes.
FRAMEWORK changes are upstream-maintained files. These are offered for your review and optional application. Each is safe to apply independently.
SEEDED changes are informational only. These files shipped from upstream as starting points and are now yours. Applying a seeded update overwrites your personalization. The script will not apply them with --apply. They require --force-seeded and an explicit decision.
USER changes are informational only. These are files you created. Upstream does not own them. No action is needed.
Present the framework change list to the Sovereign. Group by added, modified and removed. For each file, read the description aloud so the decision has context.
For any file the Sovereign wants to see before deciding:
node scripts/se-update.mjs --diff "<path>"
Read the diff together. Note what changed. Note whether the file has been locally modified (the diff shows both directions).
The Sovereign decides per file: apply, skip or defer to next session.
For each approved framework file:
node scripts/se-update.mjs --apply "<path>"
The script applies the upstream version and stages the file. Confirm each one before moving to the next.
After all approved files are applied, confirm the staged set:
git -C "<your-vault-path>" diff --cached --stat
Create a single commit that records the sync:
git -C "<your-vault-path>" commit -m "Sovereign Sync: apply upstream framework updates" -m "Applied: <list applied files>. Skipped: <list or 'none'>. Upstream ref: <upstream-remote>/<branch>."
The commit body is the sync record. It names what was applied, what was skipped, and the upstream ref. This is enough context for a future review.
If the Sovereign wants to bring in upstream changes to a seeded file (Humor Codex, Primer, To-Do Dock, hook scripts or other seeded surfaces), that is a separate explicit decision. The skill does not surface seeded file updates as part of the standard flow.
If the Sovereign requests a seeded file update:
node scripts/se-update.mjs --diff "<path>"node scripts/se-update.mjs --force-seeded "<path>"The five dual-distribution skills (Source Harvest, Self-Healing, Session Closeout, Playwright, Manuscript Anti-AI Edit Pass) also ship as standalone plugins in the Infinite Game OS public library. A Sovereign can update just one of those skills through the marketplace instead of running a full sync.
/plugin marketplace add https://www.infinitegameos.io/marketplace.json
/plugin install <skill-name>@igos-library
This refreshes that one skill independently of the vault copy. It does not touch the git-tracked version this skill manages. The two copies update on separate schedules by design.
--apply. Seeded files require --force-seeded and a separate decision. User files are never touched."No upstream remote found": Run the command the script printed, then re-run --check.
Fetch fails: Confirm internet access and that the upstream repo URL is reachable. The remote URL is in scripts/se-update.mjs (constant UPSTREAM_REPO_URL).
Apply fails with a git error: Surface the error. Do not retry without understanding the cause. A common reason is a locally locked file or a path that does not exist in upstream (was removed upstream). The removal is informational; the file stays local.
Diff is very large: Apply files individually rather than in batch. The per-file flow keeps the staged set readable.
This skill is orchestration-light. The AI reads diff output and presents it to the Sovereign. No subagent dispatch required. Sonnet handles the flow. Haiku is appropriate if the only task is parsing the --check output.
(Empty. Populated when execution mistakes occur during sessions.)
Tier: 1 (foundational).