# Owned publication manifest — Jared personal authority site only

## Release identity

- **Title:** *When a Lock Is Missing: A Preserve-and-Escalate Playbook for Self-Storage Managers*
- **Author:** Jared Mastroianni
- **Proposed slug:** `missing-lock-incident-response-self-storage`
- **Proposed canonical:** `https://jaredmodstorage.github.io/writing/missing-lock-incident-response-self-storage/`
- **Description:** `A practical response for a missing lock or suspected unit tampering that preserves observations, access records, customer communication and release authority without inventing a conclusion.`
- **Schema type:** `Article`, with one bounded `ImageObject` and one `BreadcrumbList` if supported by the current site architecture.
- **Destination:** Jared Mastroianni personal authority site only.
- **Publisher owner:** Master Personal Site Authority.
- **State:** Publication-ready local package pending final exact QA and one internal publisher handoff. No source commit, deployment, publication or active canonical is established by this manifest.

## Frozen publisher inputs

- Article: `when-a-lock-is-missing.md`
- Practical tool: `missing-lock-incident-record.csv`
- Featured image: `031-facility-lobby-manager-conversation.png`
- 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, five source links, fictional Lakeview Row example and complete CSV.
- The site must not imply that a missing lock proves theft, forced entry, a suspect, loss, liability or an insurance outcome.
- The method is an authored operational playbook, not law-enforcement, forensic, legal, lease, insurance, safety or privacy advice.
- Keep the image's editorial/non-documentary classification in the visible caption or image notes.
- The same article and tool must not be published to modSTORAGE WordPress.

## Duplicate and release gates

1. Recheck 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 and 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 one self-canonical URL; exact title, H1, Jared byline, complete body and all five 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.