Skip to content
NutsNews chestnut logoNutsNews Wiki

Simple guide · Overview

Page status: Active

NutsNews Worker-Uplift Operation Map

This page links the shared documentation hub to the backend-owned operation map

Visual overview

Primary diagram

System map

This page links the shared documentation hub to the backend-owned operation map

Render the repository-owned system map when you need it.

Diagram is not rendered yet.

View as text
NutsNews Worker-Uplift Operation Map

This page links the shared documentation hub to the backend-owned operation map

flowchart TD
  accTitle: NutsNews Worker-Uplift Operation Map
  accDescr {
    This page links the shared documentation hub to the backend-owned operation map
  }
  subgraph "Target Ownership Boundaries"
    subgraph "Backend-host operations"
      B1["Backend deploy + restart + status"]
      B2["Smoke, health, queue, and DLQ checks"]
      B3["Broker drain, reconcile, backup/restore, and cutover"]
      B4["Owner: ramideltoro/nutsnews-backend"]
    end

    subgraph "Worker-uplift data plane"
      WQ["RabbitMQ capacity, queue type, security envelope"]
      W1["Provisioning, topology, probe, restart verification"]
      W2["Rollback and broker recovery workflow"]
      W3["Telemetry scope & budgets"]
      W4["Owner: ramideltoro/nutsnews-backend"]
    end

    subgraph "Stage runtime services"
      S1["Scheduler service"]
      S2["Fetcher service"]
      S3["Canonicalizer service"]
      S4["Enrichment service"]
      S5["Approval service"]
      S6["Translation service"]
      S7["Persistence service"]
      S8["Publication service"]
      S9["Owner: stage repos in backend ADR"]
    end

    subgraph "Infra"
      I1["Grafana folders, dashboards, alerts, synthetics"]
      I2["Cloudflare DNS failover controller"]
      I3["Owner: ramideltoro/nutsnews-infra"]
    end

    L1["Legacy Worker script set (rollback posture)"]
    T1["Tracking issue execution order"]
    T2["Owner: ramideltoro/nutsnews-worker"]
  end

  B4 --> B1 --> B2 --> B3 --> W3
  W4 --> WQ --> W1 --> W2 --> W3
  W3 --> S1
  S1 --> S2 --> S3 --> S4 --> S5 --> S6 --> S7 --> S8 --> L1
  I3 --> I1 --> I2
  I1 --> W4
  I2 --> B2
  L1 -.->|legacy runbooks only; no new calls from worker-uplift runtime| S1
  T2 --> T1

NutsNews Worker-Uplift Operation Map

Fullscreen diagram view.

NutsNews Worker-Uplift Operation Map

Section titled “NutsNews Worker-Uplift Operation Map”

This page links the shared documentation hub to the backend-owned operation map for ramideltoro/nutsnews-worker#70.

Canonical source of truth:

ramideltoro/nutsnews-backend/docs/worker-uplift-operation-map.json

Backend runbook:

ramideltoro/nutsnews-backend/runbooks/WORKER_UPLIFT_OPERATION_MAP.md

Validator:

Terminal window
python3 scripts/validate_worker_uplift_operation_map.py

Operating Boundary

Section titled “Operating Boundary”

The map assigns one owner for each retained operation without changing production. It does not mutate servers, legacy Cloudflare Workers, Cloudflare DNS records, or Grafana Cloud resources.

New worker-uplift deployment, smoke, health, queue, DLQ, broker, reconciliation, and cutover operations must not require a checkout of ramideltoro/nutsnews-worker. The legacy Worker repo remains a rollback source until cutover retirement, but the new backend runtime must not call or source legacy Worker scripts.

Owners

Section titled “Owners”
SurfaceOwnerSource of truth
Backend host deploy, restart, status, logs, smoke, health, queue/DLQ, drain, broker, reconciliation, backup, restore, and cutover operationsramideltoro/nutsnews-backendbackend workflows, runbooks, and operation map
Worker-uplift RabbitMQ release, queue type, capacity, and security enveloperamideltoro/nutsnews-backend plus shared docsWorker-Uplift RabbitMQ Capacity And Security
Worker-uplift RabbitMQ provisioning, health probe, restart verification, and rollbackramideltoro/nutsnews-backend plus shared docsWorker-Uplift RabbitMQ Provisioning
Worker-uplift stage codeStage service repos listed in ramideltoro/nutsnews-backend/docs/worker-uplift-architecture-adr.jsonindividual service repositories
Grafana folders, dashboards, alert rules, synthetics, quotas, and resource driftramideltoro/nutsnews-infraterraform/grafana-cloud and Grafana Cloud workflows
Worker-uplift telemetry scope, budget, labels, and trace/exemplar decisionramideltoro/nutsnews-infra plus ramideltoro/nutsnews-docsterraform/grafana-cloud/catalog/worker-uplift-telemetry-scope.json and Worker-Uplift Telemetry Scope
DNS failover controller operationsramideltoro/nutsnews-infraCloudflare DNS failover controller workflows and runbooks
Tracking issue orderramideltoro/nutsnews-workertracking issues only

Legacy Worker Classification

Section titled “Legacy Worker Classification”

The backend map audits these legacy Worker surfaces and classifies each as copyable behavior, current API reuse, or intentional retirement:

  • shard deploy and generated Wrangler configs;
  • public smoke, post-deploy verification, and edge snapshot health;
  • backend shadow smoke;
  • feed health;
  • translation quality audit;
  • backpressure and lock safety;
  • database provider switch;
  • Supabase backup and restore validation;
  • DNS failover controller alerts and Analytics Engine evidence.

DNS failover is separate from ingestion. Backend-host routing for backend.nutsnews.com does not replace public apex/www failover ownership, and worker-uplift services must not call legacy failover scripts.