Open Questions
Technical and sandbox questions that still need answers before the mock interview. Resolved questions stay here for reference.
Still open
Three things need to be true when the call starts: REQ-35 shows 1950 W (not the 2150 W written during testing), REQ-35 is in Draft stage, and no open Change Request exists on REQ-35. The exchange icon should not be visible on REQ-35 before Beat 5b, since Beat 5b is where the governance moment happens for the first time live.
If a stale CR from sandbox testing is still attached, it will show the exchange icon in Beat 2 before governance has been introduced, which confuses the story. Can Robert or the team close it? Or can it be done directly in the UI?
When a Change Request is rejected through the UI, the requirement still shows an open CR at the API level. A subsequent stage change proposed via the API silently deduplicates against the rejected one and never opens a fresh CR. Robert said he would check with the engineering team and reply. No answer yet.
Need to know: is this intentional (a rejected CR is a soft hold, not a close) or a known gap? This directly affects whether Beat 5b governance moment will work cleanly, since the whole point is that Flow intercepts the stage transition and opens a fresh CR.
Resolved
Answered by Robert on 2026-04-29. The sandbox is on V2 of the AI feature, which has less AI. V3 is the full version. Flow is rolling it out with a goal of most customers on V3 by end of quarter.
Beat 5 framing is therefore: Claude Code plus the Flow MCP, not the native V3 panel. Robert agreed this is a strong value prop: if a customer already uses Claude, they do not have to adopt a new interface.
TestEquity 123H is a container node with no requirements scoped directly to it. “Empty System” means zero direct requirements. The “20” in the sidebar is a roll-up from all children. Expected behavior.
Confirmed via testing: it appears on requirements that have an open Change Request.
Hierarchy view organizes requirements by parent-child decomposition (which requirement decomposes from which). Systems view organizes by hardware subsystem. The demo uses Systems view; can explain the difference if asked.