Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
T
Tidal
  • Overview
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • PLN
  • Tidal
  • Repository

Switch branch/tag
  • Tidal
  • TODO.d
  • 2026-09-25-go-live-wizard.md
Find file
BlameHistoryPermalink
  • PLN (Algolia)'s avatar
    design: the Go Live wizard, and where an alert has to land · 34c5974d
    Detection stopped being the problem at 6a94b47b. What failed on 2026-09-24 is
    that every dot was green and nobody was looking at any of them: at T-2 the
    eyes are on Pulsar and the hands are on the LCXL, and neither surface said a
    word. So this is attention routing, not checking.
    
    Three principles, then the shape. One source of truth (check-gig --json; no
    surface grows its own check). An alert lands on the surface the eyes are
    already on, which is a different surface at T-30, T-5 and T-2. And a wizard
    is ordered and blocking where a dashboard is neither: one blocker, its fix,
    a re-check of that ONE probe because the full gate costs 16 s and a
    16-second wait per fix is how a wizard gets skipped.
    
    It never converges on its own. Arming a track, raising a fader and saving are
    things only PLN's hands in Ardour can do, and a tool that edits the session
    he is performing from is a tool that fights him.
    
    Also records the one alert that earns the right to interrupt a set - Ardour
    not recording while Tidal plays - and pins it to the FILES lens, because the
    OSC surface claimed arm:false for all 76 minutes it was actually recording.
    
    Three open questions left for PLN rather than answered here: which surface
    the T-2 alert lands on, whether an at-my-own-risk skip is acceptable, and
    how long the during-set silence window is. The last one needs one rehearsal,
    not an opinion.
    
    Retention and the Mix audit are marked done in the belt-and-braces list, and
    Tidal 08 is ticked: PLN armed it at 17:38 and the saved session now reads
    rec-enable=1 on all twelve.
    PLN (Algolia) authored Sep 25, 2026
    34c5974d
2026-09-25-go-live-wizard.md 6.26 KB
EditWeb IDE
×

Replace 2026-09-25-go-live-wizard.md

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.