DJ Fiddlesticks
Public Roadmap

Public-safe status only

Ecosystem Roadmap Board

A public progress board for the DJ Fiddlesticks rollout. The showroom stays visible; private controls, tokens, callbacks, and service internals stay offstage.

Last sync: 2026-05-10

Done Test-Ready Pending Manual Gate
Public lanes

Guest-Facing Surfaces

  • djfiddlesticks.com: public brand hub
  • stage.djfiddlesticks.com: guest stage door
  • radio.djfiddlesticks.com: public radio signal layer
  • music.djfiddlesticks.com: public music ledger
  • EPK verification: complete
Private boundary

Locked Backroom

  • Private operational controls are not linked from public pages.
  • Access-gated work requires explicit human approval before runtime changes.
  • No tokens, cookies, current credentials, callbacks, or daemon internals belong here.

If it can steer the engine room, it does not get posted on the front door.

Remaining work

What is still on the board

Pending

Private Ops Hardening

  • Pending Complete secure configuration and runtime validation privately.
  • Pending Run allow/deny checks and rollback rehearsal.
  • Manual Gate Human approval required before any service start or switch.
Pending

Live Radio Activation

  • Pending Provision a verified stream backend.
  • Pending Replace mock metadata with live now-playing feed after validation.
  • Pending Confirm the canonical endpoint returns media, not a landing page.
Test-Ready

Governance

  • Manual Gate Align production branches only after owner review.
  • Test-Ready Dependency triage documented for public apps.
  • Pending Remediation branch after validation window.
House Law

Security Boundary Rules

  • Music, radio, and stage are public-safe status and guest lanes.
  • Private ops stay behind access control.
  • Do not publish tokens, cookies, current credentials, or callback secrets.
  • Do not move private controls onto public surfaces.