القائمة
Use when archiving several ecosystem artifacts at once with per-artifact approval gates before any vault move executes.
التثبيت باستخدام 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 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.
Use when you need to scrape pages, extract structured data or interact with web interfaces via headless browser automation without using screenshots.
| name | batch-archival |
| description | Use when archiving several ecosystem artifacts at once with per-artifact approval gates before any vault move executes. |
| status | draft |
| version | 0.1 |
| tier | foundational |
| contrast_not | null |
| false_twins | null |
| anti_patterns | null |
| boundary_conditions | null |
| clarity_triggers | null |
Purpose: Execute Batch Archival Protocol with explicit approval gates.
Inputs:
Outputs:
Constraints:
complete for non-plan artifacts and implemented for Pending Plans. May also include object-specific terminal statuses (e.g., retired for Quest notes) when approved.Tier: 1 (foundational).
(Empty, populated when execution mistakes occur during sessions.)