Blog
Shipping notes: two hosts, one checklist
How Meteoric ships Zeal and the studio site together—DNS, ads.txt, policies, and the calm-product checks we refuse to skip.
Why two hosts stay separate
Meteoric Creates (meteoriccreates.com) explains the studio. Zeal (zeal.meteoriccreates.com) explains the journal and hosts educational guides. Shipping them as one undifferentiated blob made ownership fuzzy for readers and for advertising reviewers. Keeping the hosts separate is a product decision, not a vanity DNS trick.
When we cut a release, both hosts must still answer the same ownership questions: who publishes this, how do I email you, where are Privacy / Terms / Disclaimer, and does ads.txt match the live publisher ID?
The checklist we run before calling it shipped
Click primary nav on both hosts. Open an empty journal at /app/. Confirm contact@meteoriccreates.com still resolves. Confirm ads.txt lists pub-1659652114567733 on hosts that declare AdSense. Confirm policy pages still describe features that actually shipped—no orphan claims about HealthKit, ads inside /app/, or clinics we do not run.
We also spot-check a guide page for byline, updated date, related links, and a Try this in Zeal deep link. Thin public pages without authorship are how YMYL sites fail review; we treat that as a release blocker.
What we measure (and what we ignore)
We care that a stranger can verify the publisher without creating an account. We care that the private journal stays ad-free. We do not optimize for engagement theater—forced notifications, fake urgency, or miracle health claims.
If a deploy looks green locally but CDN cache serves yesterday’s disclaimer, we treat that as a failed ship. Calm products still need operational discipline.
How this series continues
Shipping notes will stay practical: what broke, what we fixed, and which promises we kept small on purpose. Wear pairing stories live in a sibling series so hardware anecdotes do not drown publishing craft.
If you are a policy reviewer, start with Zeal’s How Zeal works / FAQ page, then return here for how the studio thinks about release quality.
DNS and cache gotchas we keep hitting
A green local build is not a live site. CDN caches have served yesterday’s disclaimer while today’s commit looked fine in CI. When we ship, we hard-refresh policy pages on both hosts and compare ads.txt bytes to the publisher ID we claim in meta tags.
Subdomain rewrites also deserve a click. zeal.meteoriccreates.com must land on the Zeal public tree, games.meteoriccreates.com on the arcade, and the studio apex on brand pages—not a confused 404 that looks like an abandoned property to reviewers.
We keep a short post-deploy note in the README for exactly this reason: tired humans skip steps, and calm products still need dull ops.
What “done” means for privacy messaging
Consent banners must not block reading. Personalized ads load only after an affirmative choice. Limited ads and reject paths have to remain available. FAQ, Privacy, Terms, Disclaimer, Advertising, About, Contact, author pages, and the journal never host AdSense units.
If Funding Choices messaging is enabled for a region, it should not contradict our banner copy. Reviewers notice when two consent systems disagree.
We also refuse patterns that look like forced engagement: fake system dialogs, download bait, or “support us by clicking ads” language. Those fail both taste and program policy.
Connecting shipping notes to Wear stories
Hardware pairing anecdotes live in the wear-pairing series so this shipping series can stay about hosts, checklists, and public trust. Cross-links are fine; mixing voices into one undifferentiated feed is how we confused readers before.
If a release includes Wear changes, we still run the two-host checklist first. A perfect watch handshake does not excuse a missing contact email on the studio site.
Return next time for more shipping notes—or jump to Zeal’s FAQ if you are evaluating the product for advertising or privacy review.
Field appendix 1 · shipping-notes-two-hosts-one-checklist
This appendix expands Shipping notes: two hosts, one checklist for reviewers who want more operational detail without leaving the studio voice. Meteoric Creates ships Zeal as a calm journal: public pages explain ownership; /app/ stays private and ad-free; educational guides stay labeled as non-medical.
We measure release quality by whether strangers can find Privacy, Terms, Disclaimer, FAQ, Contact, and a working email—not by how loudly we announce features. Wear pairing, guides newsletters, and games seasonal habits are optional layers around that core.
If something on a live host contradicts this essay, trust the live policy page and email contact@meteoriccreates.com with the URL. Shipping notes exist to shrink that gap over time, not to paper over it.
Field appendix 2 · shipping-notes-two-hosts-one-checklist
This appendix expands Shipping notes: two hosts, one checklist for reviewers who want more operational detail without leaving the studio voice. Meteoric Creates ships Zeal as a calm journal: public pages explain ownership; /app/ stays private and ad-free; educational guides stay labeled as non-medical.
We measure release quality by whether strangers can find Privacy, Terms, Disclaimer, FAQ, Contact, and a working email—not by how loudly we announce features. Wear pairing, guides newsletters, and games seasonal habits are optional layers around that core.
If something on a live host contradicts this essay, trust the live policy page and email contact@meteoriccreates.com with the URL. Shipping notes exist to shrink that gap over time, not to paper over it.
Related studio notes
Disclaimer: Educational studio writing only—not medical advice. Zeal AI meal photos are optional model estimates and are not lab measurements. Read the full Disclaimer and Zeal Privacy before relying on any health-adjacent wording.