# Owned publication manifest — Jared personal authority site only

## Release identity

- **Title:** *When Unit 214 Becomes Two: The Identity Cutover for Self-Storage Inventory*
- **Author:** Jared Mastroianni
- **Proposed slug:** `unit-identity-cutover-self-storage`
- **Proposed canonical:** `https://jaredmodstorage.github.io/writing/unit-identity-cutover-self-storage/`
- **Description:** `A practical self-storage systems method for retiring one unit identity, creating successors and reconciling every release-critical surface after a split, merge or renumbering.`
- **Schema type:** `TechArticle`, with one bounded `ImageObject` and one `BreadcrumbList` if the current site architecture supports them.
- **Destination:** Jared Mastroianni personal authority site only.
- **Publisher owner:** Master Personal Site Authority.
- **State:** Publication-ready local package; no source commit, deployment, publication or active canonical is established by this manifest.

## Frozen publisher inputs

- Article: `when-unit-214-becomes-two.md`
- Practical tool: `unit-identity-cutover-register.csv`
- Featured image: `052-ai-development-ai-engineering-design-review.jpg`
- Image fields and provenance: `image-notes.md`
- Source scope: `source-register.csv`
- Originality and claim boundary: `originality-and-claim-boundary.md`
- Editorial and visual decision: `editorial-qa.md`
- Validation record: `validation.json`
- Exact byte manifest: `checksums.sha256`

## Release boundaries

- Preserve the exact title, article, four source links, fictional Willow Row example and 42-field CSV.
- The site must not suggest this method is a standard, certification, product capability, deployed workflow or customer result.
- Do not expose the fictional identifiers as real facility records or structured entity facts.
- Keep the image's editorial/non-documentary classification in visible caption or image notes.
- The same article and tool must not be published to modSTORAGE WordPress.

## Bounded publisher correction

The supplied paper used a superseded Facily role label outside the governed article body. Before public release, the publisher changed only that label to the current governed `Founder` wording. No title, thesis, method, fictional example, source, tool, image, factual boundary or outcome claim changed. The original supplied paper SHA-256 was `e2365910bef7bf5320c5005bc146b78439566641fb0e044542b44066500bc2fe`; the original supplied manifest SHA-256 was `4fc3f07ee549a57aad1725618cf3965347774b3a2dedc1dba3ef1a3f81cd7aac`. The release package records the corrected public hashes separately and preserves this provenance note.

## Duplicate and release gates

1. Recheck the exact title, slug and canonical against the live site, source tree, deployment tree, sitemap and feed.
2. Reconcile an exact existing route rather than creating a duplicate.
3. Preserve package bytes and record exact source/deployment/rollback identities.
4. Validate title, H1, Jared byline, canonical, description, structured data, image, alt, caption and tool download.
5. Run complete desktop, 390-pixel and 320-pixel browser and accessibility checks before release.
6. Publish only to the assigned personal authority site and report exact live readback.

## Live gates

Do not claim publication until fresh public readback proves HTTP 200 at the one self-canonical URL; exact title, H1, Jared byline, complete body and all four source links; exact tool and image bytes; correct alt, caption, Open Graph and Twitter image; expected one-route sitemap and one-item feed delta; bounded schema; no broken links, accessibility violations, horizontal overflow, console errors or page errors at 1,280, 390 and 320 pixels; and exact source/deployment parity.

Source handoff, source commit, deployment, successful Pages run, publication, crawling, indexing, ranking, independent coverage and recognition remain separate states.

## Rollback

Preserve the exact pre-release source and deployment commits. If live verification fails materially, restore the previous deployment through the established reversible release path, keep the package and failed-release evidence, and verify the defective canonical is no longer active. Do not alter unrelated routes, repositories, domains, credentials, billing or security controls.