# Owned publication manifest

## Release target

- Route: `/writing/safe-action-unsafe-batch-self-storage-ai/`
- Canonical: `https://jaredmodstorage.github.io/writing/safe-action-unsafe-batch-self-storage-ai/`
- Publisher: Jared Mastroianni personal authority site only
- Publisher owner: Jared Mastroianni
- Schema: `TechArticle`, `ImageObject` and `BreadcrumbList`
- Author: Jared Mastroianni
- State: publication-ready local package only; no publisher handoff or public mutation
- Excluded owned publisher: modSTORAGE WordPress must reject the same complete article, title, slug, body, fictional Copperline example and practical tool as a duplicate

## Required public package

- `a-safe-action-can-become-an-unsafe-batch.md`
- `ai-consequence-budget-register.csv`
- `source-register.csv`
- `057-ai-development-ai-rollout-staff-training.png`
- `image-notes.md`

## Presentation requirements

- Preserve the title, deck, byline, editorial disclosure and source limitations.
- Place the governed image after the byline with the exact alt text and caption from `image-notes.md`.
- Present the CSV as a downloadable operator tool and retain its blank-template and explicitly fictional row labels.
- Preserve reserved, consumed, unknown and available capacity as separate states.
- Preserve request rate, concurrency, unique intended effects and cumulative consequence as separate limits.
- Do not describe the proposed budget layer as a Facily capability, deployed control, legal conclusion, compliance result, certification, audit, safety guarantee or measured operating result.

## Separate release gates

1. Reconfirm the title, route, slug, fictional Copperline example and register are absent immediately before any publisher mutation.
2. Verify every governed hash against `checksums.sha256`.
3. Build and test the source locally; verify structured data, internal links, source links, download and image.
4. Commit source with a known rollback parent.
5. Deploy once through the established personal-authority-site workflow.
6. Read back the canonical, H1, byline, disclosure, image, download, metadata, sitemap and feed at desktop and mobile widths.
7. Record source, deployment, rollback and provider-run identities separately.
8. Keep publication, crawling, indexing, ranking, coverage and recognition as separate states.