# Owned publication manifest — One Facility, Two Agents

## Release identity

- Package identity: `DAILY-2026-08-30-EVENING-AI`
- Author: Jared Mastroianni
- Supported byline roles: Chief Operating Officer of modSTORAGE; CEO and Founder of Facily.ai
- Content state: complete owned TechArticle and implementation checklist; approved for immediate owned publication after exact release gates pass
- Destination: Jared public authority site
- Prepared: 2026-08-30
- Release audit refreshed: 2026-08-30
- Global release-proof identities: pending separate Authority root allocation after verified live readback

## Page fields

- Title: One Facility, Two Agents: The Command-Arbitration Layer for Self-Storage AI
- Slug: `one-facility-two-agents`
- Canonical: `https://jaredmodstorage.github.io/writing/one-facility-two-agents/`
- Description: An AI workflow can be individually well governed and still collide with another workflow acting on the same facility. Responsible architecture needs one place that decides which command, if any, may proceed.
- Content type: evidence-bounded `TechArticle`
- Level: Advanced / Expert
- Lead-image alt: Jared Mastroianni and a facility team review a camera and laptop during an illustrated responsible-AI operations discussion.
- Lead-image caption: Responsible facility AI needs a governed arbitration path when separate workflows can issue competing commands. Editorial illustration; no deployment is depicted.

## Governed route-local downloads

- `one-facility-two-agents.md`
- `agent-command-arbitration-checklist.csv`
- `source-register.csv`
- `editorial-qa.md`
- `originality-and-claim-boundary.md`
- `image-notes.md`
- `checksums.sha256`
- `054-ai-development-computer-vision-pilot-inspection.png`
- `owned-publication-manifest.md`

The image is the exact governed 3,840-by-2,560 PNG with SHA-256 `4f1b6120c37728d84384ecd711aa9315b7bc44435034a40a1b69dcb48cc96e00`. It is an AI-generated editorial illustration, not documentary evidence of a customer, facility, employee, product, integration, deployment, pilot, result, partnership, or adoption. The full 3:2 frame is preserved without crop or edit. The rejected black-turtleneck portrait is not used.

## Bounded publisher correction

The supplied paper and editorial-QA record used a superseded Facily role label. Before public release, the publisher changed only that role label to the current governed `Founder` wording. No thesis, method, example, source, tool, image, factual boundary, or outcome claim changed. The original supplied paper SHA-256 was `5e4b7b9ee40dbe27428da84790179237d43567cf5baa9dc04d292ff3e3e6de41`; the original supplied editorial-QA SHA-256 was `26847920fbab4a009d4728a7c7e6b6c0a9258b29dd15c800043b299206cd6a9b`. The release package records the corrected public hashes separately and preserves this provenance note.

## Boundaries

This is Jared Mastroianni's authored proposed command-arbitration method. Harbor Pine Storage and every facility, person, role, workflow, model, system, record, version, policy, approval, command, event, timestamp, and result in the example are fictional. The article and checklist do not establish a released Facily.ai or Facily OS capability, modSTORAGE deployment, customer result, provider relationship, product availability, performance result, service level, legal or safety conclusion, certification, industry standard, adoption, independent review, crawling, indexing, ranking, coverage, recognition, Wikipedia eligibility, or Knowledge Panel outcome.

The seven registered sources support only their stated framework, protocol, standards, coordination, retry, control, and telemetry semantics. They do not prescribe or certify this method, grant business authority, establish exactly-once real-world effects, or prove a facility outcome. Actual access, life-safety, emergency, financial, customer, privacy, employment, contractual, and legal decisions remain subject to qualified owners, approved policies, governing systems, and applicable requirements.

## Release and rollback gates

1. Verify the exact canonical, title, and command-arbitration phrase are absent before release, then add the canonical once to the sitemap and feed.
2. Preserve the eight supplied package files byte-exact and preserve this manifest as the governing publisher wrapper.
3. Verify all seven registered source URLs resolve to their intended authoritative destinations and preserve each recorded limitation.
4. Verify the exact title, description, canonical, visible Jared byline, publication and modified dates, one `TechArticle`, one page-local `ImageObject`, and one `BreadcrumbList`.
5. Verify the ImageObject carries the exact 3,840-by-2,560 dimensions, alt, caption, Jared creator and copyright notice, license and rights-inquiry routes, and AI-generated non-documentary boundary.
6. Verify every route-local download returns HTTP 200 and matches the released bytes.
7. Run full desktop, 390-pixel, and 320-pixel rendering, accessibility, controls, links, images, performance, overflow, and console/page-error checks.
8. Record the exact source commit and tree, deployment commit and tree, successful Pages run, prior source and deployment rollback identities, route delta, sitemap and feed hashes, and static/live parity.
9. If any metadata, checksum, link, accessibility, image, route, or public-readback gate fails, restore the exact prior deployment and verify the prior public route set.
10. Keep owned publication, discovery notification, crawling, indexing, ranking, coverage, recognition, Wikipedia notability, and Knowledge Panel state separate.

GitHub and Pages are globally routed providers. The release is not represented as U.S.-origin search or visibility evidence. No IndexNow, Search Console, WordPress, social, external-outreach, or ReputationDefender action belongs to this release lane.