answer-collector

Product assessments in JSON use a schema with metadata (product_name, timestamps in ISO 8601 format), 17 questions organized into WHY, WHO, WHAT, and GO/NO-GO sections, and computed fields like answered_questions and completion_percentage. You build the JSON incrementally, validating required fields as you progress.

Yes. The assessment schema supports GO/NO-GO decision logic with a computed go_no_go_result field, enabling teams to evaluate new product ideas systematically, document their reasoning across all four sections, and maintain audit trails for collaboration and future reference.

Validation rules enforce required metadata (product_name, ISO 8601 timestamps) and track completion status through answered_questions and completion_percentage fields. The schema validates incrementally as responses are collected across the 17-question assessment, catching missing or malformed data before finalization.

Use incremental JSON assembly to gather responses progressively from team members across WHY, WHO, WHAT, and GO/NO-GO sections. The schema maintains consistent structure and validation, allowing multiple contributors to input answers while preserving metadata and computing real-time completion metrics.

Computed fields answered_questions and completion_percentage automatically reflect progress as responses are added to the JSON. This enables teams to see at a glance how many of the 17 questions have been answered and monitor incremental completion across assessment phases.