How Issue 001 was researched

Source method

Discovery starts with a date-bounded scan across every active Grisons destination, using English, German, Italian and Romansh place-name variants where useful. Search results are leads, not evidence. Material facts are checked on the original municipal, cantonal, transport, lift, event-organiser, appointed-agent or accommodation-operator page.

Every selected claim receives an exact article-level citation with page title, URL, publication date when available, access time and a short note describing what the page proves. A publisher homepage does not replace the exact page. First-party property pages can establish facilities and operator terms; they cannot supply independent endorsement, measured performance unless they publish the measurement, image permission or live availability for dates that were not checked.

One article per category

Each listing-led category is written as one substantive article, not a stack of property cards. It must combine one or two current, place-specific news threads with a comparative review of every attached shortlist entry. For each stay, the article identifies the exact product and location, the evidence-based distinction, a meaningful trade-off, the reader it may suit and the important point that remains unverified.

Images

Destination and article lead images show the place itself: village, lake, valley, mountain, street or ski landscape. Bedrooms and hotel façades do not stand in for a destination. Issue 001 uses reusable Wikimedia Commons landscapes for its place imagery; each destination record stores the creator, source page and licence in Pulse. A listing card may show the selected property only when its reuse rights, licence and required credit are cleared and recorded. Otherwise it uses an attributed, licensed image of the destination or omits the image.

A publicly reachable hotel CDN or press page is not proof of reuse permission. If property-image permission is unresolved, the image must be licensed or replaced before it is treated as publication-safe.

Body and relation parity

The rendered article and its Pulse relations must describe the same evidence set. Every substantive external link in the body has a matching article-source record using the exact canonical page, and each material place appears in the article’s destination relations. Every accommodation discussed as a selection is attached to the issue, assigned to the correct section and represented by the same name, location, price basis and evidence limits in both places.

Before publication, links and relations are compared in both directions. The complete issue is then read back through the same Pulse projection used by the website to catch missing permissions, ordering and rich-text errors.

Sunday general issue

1. 05:30 Europe/Zurich: run the seven-day news scan and the category-specific 30-day accommodation and development scan for every active destination.
2. 06:30: open the original pages, remove duplicates, classify by destination and section, and rank by recency, practical consequence and evidence quality.
3. 07:30: draft the seven ordered articles. Lead with date, place and practical consequence; preserve unknowns instead of filling them with sales language.
4. 08:00: reopen every selected URL and verify dates, access constraints, price basis, availability wording, accommodation category and image rights.
5. 08:30: update draft Pulse records, attach ordered articles, destinations, listings and exact citations, then perform the body-and-relation parity check and API readback.
6. 09:00: publish articles first and the general issue last. Verify the homepage, full issue, article, destination and listing routes as a logged-out reader.

Future Friday personal issue

This workflow is planned, not currently promised as a live service. It begins only when a signed-in reader asks for an issue and chats with AlpeanGlow to define a usable search brief. Once requested, that brief is reviewed for every Friday edition until the reader pauses it, using the requested dates, party size, budget, destinations, accommodation type and practical constraints.

1. Search approved property platforms and owned Pulse records without bypassing portal controls or treating search-result availability as confirmed inventory.
2. Record exact candidate URLs, retrieval time, date span, occupancy, currency and price basis, then verify decisive claims with the operator or appointed source.
3. Human-review the shortlist, evidence limits, citations and image rights; reject weak matches rather than padding the issue.
4. Create the private issue and articles for the authenticated user, run the same parity and website checks, and exclude them from public routes, indexing and sitemaps.
5. Publish the issue to the reader’s account and email it every Friday only after verification, until the reader pauses it. An incomplete run remains a draft.

Principal operational sources

• Graubünden police: Arosa ClassicCar
• Graubünden police: SlowUp Albula
• Engadin Bus service notices
• Rhätische Bahn: Zuoz station refurbishment
• LAAX hunting-period trail restrictions
• SGRAIL78 programme
• Sils Autumn Festival
• StradivariFEST programme
• Flimserstein alp descent

Research for this issue closed on 4 September 2026. “Source checked” means that the cited page resolved and supported the recorded claim at the cut-off; it does not mean independent inspection, reusable image rights or live availability.