Call the product open[flow], and the env vars OPENFLOW_ The suite was renamed; the manual follows. References to the legacy bsv.json sidecar file stay, because that really was its name and the import path from it still exists. Co-authored-by: Codex <noreply@openai.com> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P5mLf7B2kE7jYXiNgihDWQ
The chart: the dot is about the bass, not the roll
The chart: one octave from the low E, and the five-string dot
The chart: the degree colours are roygbiv now
The chart: the roll sits on the part, and the wheels hold their space
The chart: the roll sits an octave up, and nothing is dimmed
The chart: the degree colours, and labelling every white key
The chart: the roll's two octaves do not move
The chart: the roll is the bass part, copied
The chart: spotting a kit that does not say it is one, and how long the roll is
The chart: the progression is a piano roll now Time across with bar numbers, notes up the side against a keyboard, a playhead sweeping through. Adds the CHORDS / BASS toggle — the same progression drawn as every note of each chord or as the root alone, remembered per phone so the bass player and everyone else can each see the one they want. Co-authored-by: Codex <noreply@openai.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F2Y71YLAtCi2PcTxuEPrJr
The chart: the chord strip The progression, read out of the MIDI of what is playing, with the current bar lit. Covers what it reads and what it leaves out, that drums would misspell every chord, why a bar can show a dash, the two cases that leave it blank entirely, and that notes are read when a clip is launched rather than continuously. Co-authored-by: Codex <noreply@openai.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F2Y71YLAtCi2PcTxuEPrJr
The chart: the section list is off for now It was too small to read down the side and it was taking room the tempo and the wheels needed. Notes that the key now follows the section you are in, rather than each section stating its own, and lists the section list under what is not there yet rather than leaving the page describing something nobody can see. Co-authored-by: Codex <noreply@openai.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F2Y71YLAtCi2PcTxuEPrJr
The chart: the tempo buttons and the loop wheels The tempo is now the middle of the page with a button either side, and the wheels along the bottom show which bar of how many each playing track is on. Covers what the amber "named 100" means, why wheels hold still when the transport is stopped, and that the tempo buttons are the one thing on a phone that reaches the set. Co-authored-by: Codex <noreply@openai.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F2Y71YLAtCi2PcTxuEPrJr
Add The chart The page the band reads off a phone: the playing song, its key and bpm, and its sections with the current one lit. Covers getting it onto everyone's phones, why a key or bpm moves from the heading down onto the sections when a song modulates or speeds up, that nothing on a phone can reach the set, and what each state on the top line means. Co-authored-by: Codex <noreply@openai.com> Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F2Y71YLAtCi2PcTxuEPrJr