# Originality and claim-boundary review

## Final identity

- **Title:** *Temporary Is Not a Portfolio Standard: Put an Expiration Date on Every Facility Exception*
- **Slug:** `facility-standard-exception-expiration-self-storage`
- **Thesis:** A facility-specific deviation from a portfolio standard needs a controlled lifecycle with exact scope, authority, compensating controls, evidence, review and expiry times, deterministic expiry behavior, restoration or replacement tests, and downstream reconciliation.
- **Practical tool:** 37-field `facility-standard-exception-register.csv` with one blank template and four explicitly fictional Copper Ridge records.

## Duplicate screen refreshed September 8, 2026

- The September 8 midday directory was absent before this run. The current-date morning lane contains the distinct operator article *Thunder Ends the Outdoor Task*, a lightning stand-down method. No current-date evening package existed at preflight.
- Authority Control Room `main` commit `e9dadc0be26a9218aec459a52c563b711a7b6a85` and its 46-record editorial calendar, 347-record published-asset register, 362-record submission tracker, 75-record editorial/media register and 555-record evidence register were inspected without checking out or changing the user's older working branch.
- Both other daily-lane memories, prior daily packages and active, assigned, accepted, prepared or submitted manuscripts were screened.
- *When Automation Should Stop* governs stopped automated work in an exception queue. This article governs the authorization lifetime and closeout of a facility-specific departure from a portfolio standard.
- *The Multi-Location Policy Compiler* governs creation of site-specific controls from a portfolio rule. This article begins after a site needs permission to deviate from its approved control and governs that deviation through expiry and reconciliation.
- *The Facility Change-Impact Graph* governs dependencies and tests before a planned change. This article governs a temporary operating difference after a bounded exception is proposed or activated.
- *The Portfolio Handoff Audit* governs transfer of work between owners. *The Continuity Pair* governs alternate ownership during absence. This article requires an owner but does not reuse either handoff method.
- The IFMA FMJ manuscript governs cross-facility metric comparability. The Inside Self-Storage manuscript governs event-bus and source-of-truth failure modes. The Modern Storage Media work governs facility-identity cutover and a separate oversight-load topic. No title, structure, fictional example or practical tool was reused.
- Local exact searches found no unrelated use of the final title, slug, Copper Ridge Storage Group example or Facility Standard Exception Register.
- Live owned-site sitemaps returned HTTP 200 and contained 62 Jared authority-site URLs and 139 modSTORAGE post URLs; neither contained the selected title or slug.
- Both proposed owned URLs returned HTTP 404. The public WordPress exact-slug REST query returned HTTP 200 with `[]`. These checks cannot exclude unknown private CMS drafts.
- Exact web searches for the final title, subtitle phrase and slug found no matching article.

## Bounded originality screen

- Corpus: 402 other Markdown files under the editorial-execution workspace, excluding the current package and dependency, Git, distribution, build, archive, cache and render paths.
- Method: lowercase Unicode normalization; exact normalized sentence comparison for sentences of 14 or more words; unique six-word-shingle comparison.
- Eligible article sentences: 48.
- Exact normalized matches of 14 or more words: **0**.
- Unique article six-word shingles: 1,707.
- Maximum shared six-word shingles: **0**.
- Maximum overlap: **0.000000%**.
- This screen does not prove worldwide originality, patentability or absence from inaccessible private drafts. It provides a reproducible bounded local screen plus current public checks.

## Claims and rights boundary

- Copper Ridge Storage Group, CR-01 through CR-04, every system, person, date, control, evidence item, action and outcome are explicitly fictional teaching material.
- No customer, facility deployment, partnership, product availability, service level, performance result, revenue, occupancy effect, adoption, certification, award, independent coverage or recognition is claimed.
- NIST configuration and cybersecurity publications and the GAO Green Book support bounded concepts about baselines, change control, policy, roles, monitoring and remediation. None defines a self-storage exception lifecycle, validates the authored tool or establishes authority for a specific operating deviation.
- The article expressly warns that a completed register does not establish legal, technical, safety, financial, privacy or employment authority and that expiry should not blindly trigger an automated reversal.
- Research synthesis, drafting and QA were AI-assisted. The package does not claim Jared personally reviewed or approved the draft.
- Local draft, publisher handoff, CMS or repository creation, publication, canonical activation, sitemap/feed inclusion, crawling, indexing, ranking, independent coverage and recognition remain separate states.