What
On the Corpus Brief, the candidate-themes card reads "Explore these themes — Accept themes as constructs, compile instruments, and preflight a run", but its button just does router.navigate("…/constructs") (app/js/screens/brief.js) with no theme data. You land on an empty/unrelated Constructs screen with nothing to accept, and have to re-create the themes from scratch — despite the brief already holding them as {name, definition, quoteRefs}.
Fix
Wire the brief's themes into the existing accept-proposals flow: themesSheet/proposalsSheet (app/js/screens/constructs.js) already consume exactly {name, definition, quoteRefs} and create constructs on Accept. Have the CTA open that sheet seeded from the brief's themes.
What
On the Corpus Brief, the candidate-themes card reads "Explore these themes — Accept themes as constructs, compile instruments, and preflight a run", but its button just does
router.navigate("…/constructs")(app/js/screens/brief.js) with no theme data. You land on an empty/unrelated Constructs screen with nothing to accept, and have to re-create the themes from scratch — despite the brief already holding them as{name, definition, quoteRefs}.Fix
Wire the brief's themes into the existing accept-proposals flow:
themesSheet/proposalsSheet(app/js/screens/constructs.js) already consume exactly{name, definition, quoteRefs}and create constructs on Accept. Have the CTA open that sheet seeded from the brief's themes.