A generated artifact is a candidate.
The approved snapshot travels into venture analysis and the build dossier. Model review alone does not establish a working product.
CONNECTED WORKFLOW / 02
Keep the evidence.
Make the decision.
A reported problem becomes a bounded specification. Review what the prototype should do before a model builds anything.
01 XploreMore evidence02 Human scope review03 Pro2Pro build04 Tests & acceptance
The example is a historical XploreMore record, with a sample specification. Loading it performs local validation only. Source reports remain untrusted evidence; usefulness is unverified.
YOUR NEXT BUILD STARTS HEREA source, a scope,
A source, a scope,
and a reason to build.
Open the recorded example or bring a brief exported from XploreMore. The evidence stays beside the acceptance criteria throughout the review.
BROWSER EDITION
Review here. Build locally.
Brief validation, local decisions and JSON exports work in this browser. Authenticated imports, model generation and artifact acceptance require the local backend. No operator key is needed here.
Try Decision Desk → · Local setup guide ↗Inspect or edit the handoff JSON
What counts as done?
Test the promised behavior.
Check inputs, outputs, failure cases and browser interaction independently. Record what was exercised and what remains unknown.
Review the actual result.
Approval of a problem does not authorize publication of an unseen generated artifact. New bound-snapshot builds withhold automatic publication.