From docs/THOUGHTS.md.
"Safe content" made sense from the inside (never-dead-air safety net) but conveys nothing to a new operator — safe from what? It's really station-maintenance audio. Consider renaming (Patter? Station audio? Standby content?) and generalizing the authoring page to other kinds: station IDs, jingles, sweepers — same render→measure→catalog pipeline, different kind tag.
Naming note: whatever wins must stay coherent with the taste-exclusion law (gh-#99: safe content is functional audio, never rateable) — the name should make THAT rule feel obvious too.
From docs/THOUGHTS.md.
"Safe content" made sense from the inside (never-dead-air safety net) but conveys nothing to a new operator — safe from what? It's really station-maintenance audio. Consider renaming (Patter? Station audio? Standby content?) and generalizing the authoring page to other kinds: station IDs, jingles, sweepers — same render→measure→catalog pipeline, different kind tag.
Naming note: whatever wins must stay coherent with the taste-exclusion law (gh-#99: safe content is functional audio, never rateable) — the name should make THAT rule feel obvious too.