OV-1 — Operational Concept

Viewpoint: who uses channel-surf-tv and what flows between the big pieces.

channel-surf-tv is a surf-culture reference site: a worldwide surf-spot atlas, surfer profiles, quotes wall, video clips, and a curated Instagram feed. Content is curated offline (importer scripts propose candidates from OSM/Wikidata/Wikiquote/Commons; the operator reviews and seeds migrations) and served as a static Astro site backed by a read-only Worker API.

flowchart LR
  visitor([Site visitor])
  operator([Operator / curator])

  subgraph edge [Cloudflare edge]
    site[Static Astro site]
    api[Worker API - read-only]
    cron[6-hourly cron]
  end

  subgraph data [Data plane]
    d1[(D1: channel-surf-tv-spots)]
    r2[(R2: channelsurf-bucket)]
  end

  subgraph external [External sources]
    ig[Instagram Graph API]
    osm[OSM / Wikidata / Wikiquote / Commons]
  end

  visitor -->|browse pages| site
  site -->|fetch JSON| api
  api --> d1
  site -->|images, clips| r2
  cron -->|score accounts, refresh feed cache| ig
  cron --> d1
  operator -->|importer scripts → reviewed migrations| d1
  operator -->|image/clip sync scripts| r2
  osm -.->|candidates only| operator

Key operational rules:

• Read-only public surface. The Worker API serves GET only; all writes happen through reviewed D1 migrations and operator-run scripts.
• Importers propose, the operator disposes. External-source importers generate candidate data; nothing lands in D1 without review (additive migrations).
• The site works without Instagram. Feed and scoring are best-effort; endpoints degrade to cached or empty payloads.