Menu
Use when running the end-of-week vault backup ritual to verify setup, run the backup script, confirm the log entry and report results.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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 | weekly-backup |
| description | Use when running the end-of-week vault backup ritual to verify setup, run the backup script, confirm the log entry and report results. |
| status | active |
| tier | foundational |
| contrast_not | null |
| false_twins | null |
| anti_patterns | null |
| boundary_conditions | null |
| clarity_triggers | null |
Purpose: Execute the end-of-week vault backup ritual with connective visibility - run the backup, confirm the log entry was written, and report results to the Sovereign.
Trigger: End of week (Friday preferred). Also invokable on demand.
Inputs: None required. Local backup configuration lives in scripts/backup.config.json, created from scripts/backup.config.example.json.
Outputs: Terminal output from backup script, confirmed log entry in Vault (Archive)/Sovereign Ecosystem Backup Log.md, summary report to user.
Status: active
Related Protocols/Codices: [[Council Chamber/Protocols/Archival/Backup Protocol]]
scripts/backup.config.json exists. If it does not, copy scripts/backup.config.example.json to scripts/backup.config.json and set BACKUP_PATH before proceeding.BACKUP_PATH is non-empty and no longer set to the example placeholder.node scripts/backup-vault.mjs from the vault root. Capture terminal output.Vault (Archive)/Sovereign Ecosystem Backup Log.md by reading the last log entry and verifying today's date is present.git status in the vault root and surface any untracked or modified files as a brief note - not a gate, just ambient awareness.Status is active. Execution is authorized without additional approval.
Steps 1 and 2 are hard gates. Do not proceed to Step 3 until the local backup configuration is complete.
Tier: 1 (foundational).
(Empty, populated when execution mistakes occur during sessions.)