Skip to content

Wire generalization: multi-vertical reactive content engine (festival_wire → +indie/new-music). Park New Music Radar as first candidate vertical #3

Description

@chubes4

Strategic concept (not an immediate build)

The wire is conceptually a multi-vertical reactive content engine, not just festivals. Today it is festival_wire (blog 11, ~3,774 posts, Data Machine-fed daily, proven and chugging). The long-term goal is for the wire to also cover indie music, new releases, and other recurring/reactive verticals — the same DM-fed reactive pattern, different subject.

This issue captures that direction so it isn't lost, and the explicit decision to NOT build it yet.

Evidence the wire wants to generalize: "New Music Radar"

Surfaced during a 404-flood investigation (May 2026). /new-music-radar still gets ~23 hits/week as a 404. It was a recurring weekly playlist series — effectively a wire that predated the wire:

  • Canonical post: blog 1, ID 63182, slug new-music-radar, currently draft/unpublished.
  • Dozens of dated instances exist as revisions (e.g. new-music-radar-april-24, new-music-radar-1-7, new-music-radar-2-6, ...).

It is not a broken URL to patch — it is a placeholder for a future wire vertical. Redirecting it arbitrarily would bury the signal; rebuilding the series now would be premature.

Decision (May 2026): PARK IT

  • Do not redirect /new-music-radar to an unrelated destination.
  • Do not rebuild the playlist series yet.
  • Restraint rule: festival_wire must be polished and discovered first before adding a second wire vertical. festival_wire is still under-discovered (~0.8% of network search clicks; only just made crawlable after the sitemap-404 fix landed). Expanding to a second vertical now is premature.
  • Data Machine already fully supports the model (festival_wire proves it end to end), so when the time comes a second vertical (indie / new-music wire) is a config/pipeline addition, not new infrastructure.

Revisit criteria

Reopen this for action when:

  1. festival_wire is polished (templates, schema, internal linking, cross-site bridges) and showing meaningful discovery/traffic growth, AND
  2. There is a clear editorial commitment to a recurring indie/new-music stream.

At that point: decide /new-music-radar's destination (republish as the first instance of the new vertical, or redirect to the new vertical's archive) as part of standing up vertical #2.

Related

No code change requested now. This is a tracked strategic placeholder.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions