archetype-selection

The best way to determine your production archetype is applying a decision tree to the site brief, choosing between brochure, editable_brochure, or app_lite. This evaluates requirements to select a starter kit and outputs a structured site plan highlighting open questions and risks.

You need an editable_brochure or app_lite archetype when the site brief specifies dynamic requirements like a CMS, database, authentication, or payments. A basic brochure archetype applies when the project lacks these dynamic data or interactive user features.

The decision tree translates a site brief into a site plan by applying selection rules and upgrade triggers from canonical configuration. It processes brief requirements to return structured fields like site-plan.archetype, site-plan.chosenStarter, and related openQuestions and risks.

Yes, you can use a starter kit if your brief requires database and authentication features by selecting the app_lite archetype. The decision rules map these dynamic requirements to a compatible starter kit, ensuring the chosen stack supports necessary data and auth functionality.

Limitations include strict refusal rules that may reject unsupported feature combinations. The process surfaces open questions and risks for auditable planning, but complex briefs requiring custom integrations outside the brochure, editable_brochure, or app_lite scope may not map cleanly to a predefined starter.