--- name: estate-publisher-deployment description: "Deploy and verify Fountain Press source-bound editions through the same immutable composition in owner-WLAN staging and separately authorized public production, using EstatePublisher delivery, SHA-256, receipts, rollback and HTTPS readback. Use for book/essay/Governance releases, machine-readable publication readback, agent-guidance version parity, social OG/Twitter image and first-page fallback verification, SSH/Caddy static publishing, route and template reconciliation, authorization, managed services, staging, Safari/iPad acceptance and production verification. Follow FCIS Goal Fidelity and Governance Chapter 158." --- # EstatePublisher Deployment — governed lanes This skill is a procedure, not a runtime publisher. Its **only canonical skill authority is Fountain-Coach/.github** (Governance Chapter 160); EstatePublisher's installed executable and Swift Kits own effects. Begin with [FCIS Goal Fidelity](https://github.com/Fountain-Coach/.github/blob/main/docs/FCIS-Non-Invention-and-Goal-Fidelity.md) and current [Governance Chapter 158](https://governance.fountain.coach/chapters/158-publishing-is-not-a-distributed-transaction/). ## Fountain Press standard: one source-bound composition for staging and production **Writer-adopted 6 November 2026.** Fountain Press is the standard **publication-composition and reading presentation** for every admitted book/essay/Governance edition in *both* canonical WLAN staging and public production. An approved work is projected once from the exact source-owner Git commit into the existing Press manifest/Bookshelf/Linotype Reader and its immutable artifacts. The production handoff reuses the verified Press composition and pinned source/asset identities (with declared stage-only URL transforms), **never** invents a new production Reader or republishes a short chapter sampler as a complete book. Nonbook Teatro/other service surfaces keep their native bodies while following their approved publication-shell and custody contract; Press does not seize their functionality or private-media rights. **Authority boundaries remain unchanged:** source owners retain text, statuses, illustrations, links and rights; Reframe/FountainStore retains any writer Bookshelf admission; Fountain Press composes the edition; **EstatePublisher alone** authorizes/delivers/activates immutable staging and public release, records terminal receipts and preserves rollback. Production requires distinct approval and independent HTTPS/asset/metadata acceptance. A stage URL, Git push, local Press build, source digest or passed browser tests are not public publication receipts. For the current tested pattern, inspect the 6 November 2026 **Governance v162** admission: 160/160 original chapters, 72 current/88 reference classifications, 70 retained source figures, 1,132 original links and 160/160 live browser compositions; one original Press compositor, source-lock SHA, immutable v161/v160 rollback and independent HTTPS HTML/JS/receipt digests. This is a **verified owner-WLAN stage**, not a public or physical iPad/VoiceOver proof. Apply this evidence model to the *actual scope* of each edition rather than imposing those fixed counts. Read [WLAN staging](references/wlan-staging.md) and [deployment modes](references/deployment-matrix.md) before promotion. ## Agent-readable publication release check (when declared) For a publication with an adopted or explicitly requested machine-readable interface, inspect the Fountain Press source/edition manifest and its public agent guidance before package, stage or release. Require the **same source owner, revision, edition identity, publication state, complete entry ordering, exact source SHA/status and guidance digest** in the human and machine projections. For Governance, preserve all current/reference statuses, original links and source identities; never call a historical/reference chapter a current instruction. Reject fabricated tool permissions, stale agent guidance, unsupported APIs, private `AGENTS.md` exposure, private media and unauthorized access claims. The [Fountain Press machine-readable publication procedure](../linotype-estate-template/references/agent-readable-publication.md) and its offline validator provide a bounded check, **not** proof of legal rights or running publication. Stage the machine discovery route and guidance alongside the **same immutable Press artifact**, verify their actual HTTPS bytes with a non-browser reader and separately verify Linotype navigation. On production, require distinct author/publisher approval and independent public readback of the same versioned machine and human surfaces, with rollback. If the machine interface is not part of the adopted/requested scope, report it as not established rather than inventing a deployment blocker or new service. ## Governance image-free publication acceptance **Governance-specific writer decision, 6 November 2026:** Neither an authored diagram nor a generated hero, chapter image, 1200×630 social card or first-page screenshot is a release prerequisite for `governance.fountain.coach`. **Do not reject Governance** because images are missing, count illustrative figures as normative authority, or require replacement of historical generic Open Graph art. Require complete source-owned text, identity, current/reference status, rights, semantic/machine parity, accessibility, immutable release authority and independent HTTPS readback. Treat existing source figures as optional historical supporting material, never as a quota. Do not promote the previously staged 160/161-card visual candidate merely because v164 proved its staging assets; production remains separately authorized. This exception does **not** exempt other explicitly illustrated publications from their accepted source-art checks. ## Publication hero and social-image admission When an authored book, essay or Governance chapter declares a **share visual**, read [Fountain Press illustration and social-card procedure](../linotype-estate-template/references/illustration-and-social-card.md) as part of the *same* immutable release. Require a source-authored in-flow hero and its authorized landscape raster derivative, or a source-pinned landscape **first composed Linotype folio** when there is no hero. Reject an unapproved generic fallback. Verify source figure identity and position on actual composed leaves; separately validate static crawler-readable **per-work** `og:image`, image width/height/alt, `twitter:image`, exact asset SHA/MIME/dimensions/rights and non-JS HTTPS readback. Hash-fragment Reader URLs do not carry distinct per-work metadata to social crawlers. Keep any original SVG figure in the Reader; verify its social raster is a derivative, not an invented replacement. Governance's source repository controls public chapter social cards; Press composes, **EstatePublisher alone** stages/promotes after separate rights/publication authorization. Reader success does not certify social-card success; the v163 70-figure fix is not evidence that the earlier 89 generic Governance Open Graph fallbacks were replaced. The writer later withdrew that image requirement for Governance, so those are **not** a mandatory outstanding release defect. ## Resolve the actual operation 1. Fix the writer's observable goal, approved host and route, exact authored source and rights, and finite acceptance. Distinguish private preview, immutable static publication, mutable FountainStore operation, service deployment, and DNS/TLS changes. 2. Inspect the working owner Git revision, deployed predecessor, present EstatePublisher implementation and receipt. **Do not substitute stale repository mirrors, historical experiments, or a saved command for active operational authority.** 3. Apply the FCIS four-question necessity test: what goal, what observed failure, which existing contract makes an alleged prerequisite necessary, and what smallest same-path correction? Unproved requirements are non-blocking. Do not turn a static essay into a distributed application transaction. 4. Read [deployment modes](references/deployment-matrix.md) and choose the current admitted mode. One mode's resolver is not a universal publishing requirement. ## Immutable static public publication — Chapter 158 Compile → validate → package → deliver → activate → verify, through the existing *authenticated* EstatePublisher SSH/SFTP/rsync and Caddy profile where supported. **Remote FountainStore replication, MIDI 2.0 sessions, host agents, new signing/enrollment ceremonies and a continuously running coordinator are not prerequisites.** - **Compile and validate off-host:** approved route/rights and media, current source-owned Publication Core, semantic relationships, canonical/social metadata and the actual public predecessor. For a *new route*, reuse the current named template/preview scenario with that route as input, and verify inherited masthead, reel, active/Info, theme, footer, responsive geometry and links; do not copy a single old HTML fragment or fabricate a scenario for every essay. A scenario-definition test does not prove a live visual witness. - **Package:** immutable approved artifact, exact SHA-256 inventory, intended host/root/changed routes, prior release and rollback. Preserve all unrelated published routes and private data. - **Deliver and activate:** invoke the existing native publisher using its real authorized deployment identity, host verification and bounded target. Check current Caddy route admission; include the smallest necessary validated route allowlist change with the release. Stage outside the active root, verify bytes, atomically switch current, retain predecessor and reload Caddy only when needed. Do not use arbitrary root SSH mutations or bypass real authorization. - **Verify:** native terminal receipt and independent HTTPS bytes for the new page, opening/social image, audio and representative neighbors; check metadata and the active release/rollback. Where the writer asks about visual behavior, separately prove AX/WebKit/Safari rendering. Stop on verified success. ## Other production and interrupted operations For a dedicated Hetzner-managed hostname or DNS/TLS change, read [Hetzner DNS through the installed hcloud CLI](references/hcloud-dns-authority.md) before diagnosing a blocker or introducing credentials. Inspect the current `hcloud` version, active project, zone visibility and exact RRset; `Zone not found` in one context is **not** evidence that `hcloud` cannot manage DNS or that authorization was refused. Reuse an already authorized zone-owning context and retain the separately approved Caddy/HTTPS publication boundary. Never create a duplicate zone or impose a separate token/SecretStore dependency without a demonstrated missing contract. Mutable Store-backed routes may require `estate.publication.sync` and its native typed Store operation; services, identity and DNS/TLS require their own currently admitted commands. **Never impose those prerequisites on an otherwise authorized immutable static release, nor replace a genuinely managed operation with ungoverned static copying.** Read the live native operation contract and its permission boundaries. When interrupted or failed, inspect the persisted terminal receipt and active identity before retrying. Preserve the previous release, use its supported idempotency/resume contract if available, and avoid overlapping processes or repeated credential prompts. A keychain prompt, source commit, tested proposal, running process, or homepage HTTP 200 does not prove deployment. ## Developing estate identity before an audio staging effect When the work extends a new Bookshelf, collection, internal work or source-bound narrated edition, read [developing-estate audio staging and recovery](references/developing-estate-audio-staging.md) before choosing an HTML/asset target. Inspect the *currently active* new-reader staging root, live collection/volume identity and its owning development branch. A legacy published essay matching the title is not automatically the current editorial source. The actual stage, Git source and public production remain **three separate authorities**; report any uncommitted stage-only work instead of silently overwriting it. ## Owner-controlled WLAN Use [WLAN staging](references/wlan-staging.md), confirm the registered Ubuntu Mac mini's actual current release and keep this private. Require HTTPS for WebAudio AudioWorklet when the browser needs it; do not impose production ceremonies on a disposable preview. ## Finite evidence Report SOURCE (owner/SHA), CONTRACT (relevant current chapter and lane), PREDECESSOR, DELTA, TERMINAL RECEIPT, PUBLIC HTTPS/DIGEST, visual/AX evidence where relevant, and remaining unverified claims. Preserve the writer's originally requested Definition of Done. The skill does not establish executable capabilities by saying they exist.