Convex backend notes: seeded Identify reducers, session audio purge, and typed flow rules.
Clinicians read Identify as a spreadsheet. Engineers cannot prove it ends. I seed Convex, write a pure reducer, and replay the sheet paths in Vitest first.
When two movements stay yes after Compare, looping the same chips teaches nothing. I pause for a pick, hatch the losers, and end the run as a hypothesis.
Spreadsheet authors invent new words every week. I lock Identify to a typed Convex menu of metrics, scopes, and actions so the reducer stays boring.
A research product records session audio apart from chat. Deleting a thread must not wipe the rolls. Admin purge is terminal-only and deletes chunks first.