batch-archival

Coordinate batch archival of artifacts with per-item approval gates before vault moves.

2|Updated Mar 9, 2026

Search Tags:#governance #vault #archive #batch #approval #audit-trails

Ready to run

npx skills add https://github.com/infinitegameplayer/sovereign-ecosystem --skill batch-archival

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: batch-archival
Source: https://github.com/infinitegameplayer/sovereign-ecosystem/tree/main/Council%20Chamber/Skills/Batch%20Archival
Command: npx skills add https://github.com/infinitegameplayer/sovereign-ecosystem --skill batch-archival

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables safe, auditable batch archival of multiple ecosystem artifacts by applying per-artifact approval gates before any vault movement.

Core Features & Use Cases

Batch selection and eligibility audit across artifacts
Per-item approvals controlling vault moves
Audit-ready reports and blockers by item

Quick Start

Initiate a batch archival run across eligible artifacts with explicit per-item approvals prior to vault moves.

Frequently Asked Questions about batch-archival

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I archive multiple artifacts in a batch while requiring approval for each item?▼

Batch archival coordinates vault moves across multiple artifacts by enforcing per-item approval gates, ensuring explicit permission is granted before each item is archived. This process produces audit-ready records and item-level blockers for governance compliance.

How does per-item approval work during a batch archival vault move?▼

Per-item approval gates require explicit permission checks before any vault move occurs within a batch archival run. The system applies input scanning and mapping logic to generate audit-ready reports and item-level blockers for governance.

Can I generate audit trails for batch archival that show which artifacts were blocked?▼

Yes, batch archival produces audit-ready reports that detail blockers by item. These records ensure governance compliance by documenting which artifacts failed eligibility or lacked explicit permission for vault moves.

What is the best way to ensure compliance when moving multiple artifacts to a vault?▼

The best way to ensure compliance during artifact vault moves is using batch archival with per-item approval gates. This enforces input scanning and explicit permission checks before any move, generating audit-ready records.

Do I need to scan artifacts for eligibility before starting a batch archival run?▼

Yes, batch archival enforces input scanning and eligibility audits across multiple artifacts before initiating vault moves. This ensures only eligible artifacts proceed to the per-item approval gate stage.