---
log: 008
title: "The catalog becomes a calendar"
date: 2026-06-05
task: "#8 Draft release manifeste"
tags: [release, manifeste, cadence, triage]
shareable: true
---

## Cap (what & why)
DSP releases froze in 2024-10. Turn the triaged backlog into a concrete year of
monthly singles to relaunch presence and feed the "when new music?" crowd.

## Manœuvre (how)
Ingested the `triage.html` export (48 confirmed calls) → 36 DSP-able originals/light.
Noticed the track NAMES are seasonal, so scheduled each single in its namesake
season — the discography sorts itself into a calendar.

## Prise (findings / artifacts)
- `tide-table/release_candidates.json` (36) + `manifeste/calendar.md` (12-month plan,
  2026-07→2027-06, + 24-track year-2 pool).
- Month 1 = **I come from Cyberspace** (relaunch flagship); Aug ties to CosmicFest v1;
  Dec = Deck the (Dance) Hall on a Bandcamp Friday.

## Sel (the shareable learning)
- **The artist already organised the calendar — in the song titles.** *Premier
  Septembre, Octobre Jaune, Vie Hivernale, Battements Printaniers*… release each in its
  season and the schedule writes itself, on-brand.
- **"Frozen distribution" was really "stopped releasing."** 36 finished-enough tracks
  sat un-shipped. The catalog turned an invisible 21-month gap into a visible 3-year plan.
- Triage tooling proposes; the artist's ear confirms (48 calls) — then code turns calls
  into a calendar.

## Hameçon (hook)
"I hadn't released on Spotify in nearly two years — turns out I had three years of
finished tracks waiting, and they'd already named their own release dates."

## Sillage (what it unlocks)
A monthly cadence the `sémaphore` (POSSE) + content engine can run on. Each release:
master (tidal-ears) → CD Baby + Bandcamp → announce + a sampling-story post.
