| 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 |
Batch Archival Skill
Purpose: Execute Batch Archival Protocol with explicit approval gates.
Inputs:
- Scan criteria (status, tags, age)
- Domain/object mapping rules
- Approval preferences
- Library eligibility audit results (proposal-only)
- Optional object-specific readiness checks (e.g., related strategy-note link scan for Scriptorium artifacts)
Outputs:
- Approval list by domain/object
- Readiness audit notes / blockers by item (proposal-only)
- Proposed Vault moves
- Library audit candidate list (proposal-only)
Constraints:
- No moves without explicit approval.
- No status changes without explicit approval.
- Library audit is proposal-only and requires Sovereign approval.
- Default status scan should include
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.
Contrast Layer Integration (Mandatory)
Tier: 1 (foundational).
- Contrast fields required.
- Footer internal contrast block required.
Refinements
(Empty, populated when execution mistakes occur during sessions.)
