David debugged: Lecture workspace documents opened as empty during live generation

Kerra generates lecture notes workspaces asynchronously — sequential agents write one document at a time. David tested the flow and found that clicking the candidate while generation was in progress opened a workspace that appeared completely empty.

i clicked on that preparing workspace, which became preparing without me even clicking on it. why? was it because of the auto promotion by the canvas distribution system? anyways, i clciked on it, and it opened the workspace, but its empty

Further investigation revealed that the frontend was navigating the user to the workspace before the backend had synced any template documents into the opened task. David then debugged the sequence of events:

now it says that workspace is ready and i clicked on it from the university app home page and it loaded successfully each document was populated. but the original chrome tab where i clicked on it while it was still generating, that one is still empty

David pushed back on the read-only design decision for in-progress workspaces:

but shoudlnt they be editable because they arent changed by any agents after the point that that lecture notes step has compelted? so why keep them read only?

He commissioned six sub-agents to investigate whether the live generation architecture actually exposed documents only once each sequential step finished, or whether it exposed them immediately on creation.