constructlisted

# construct — a product idea, grounded into a buildable SRD For engine evidence and coverage limits, read [engine-evidence](references/engine-evidence.md). `construct` turns a product idea into a **Software Requirements Document suite** whose requirements and decisions are **grounded in real research**, not the model's memory. The deterministic engine (`scripts/construct.mjs`, zero-dep Node) does the searching, dossier assembly, SRD rendering and validation **with code**; your job is to run the interview, drive the research, and enrich the rendered scaffold into a precise, well-grounded SRD. > **The core rule:** prefer a *grounded* requirement to a *guessed* one. Use the > research the engine retrieves (competitors, OSS prior art, tech docs, > StackOverflow) to justify scope, NFRs and architecture decisions, and cite the > evidence with `[E#]`. Grounding is **advisory by default**: `construct check` reports citation > coverage. Pass `--min-grounding <0-100>` to fail below a required coverage > threshold. Coverage counts references; use `review` and `check --semantic` > to verify that the cited evidence actually supports the claims. ## The loop, in one line ``` [brainstorm] → interview → research → analyze → drill → render → enrich → red-team → check → present → [build] ``` `construct status --out <run>` prints what exists **and the exact next command**. Use it whenever you resume a run, or lose the thread. ## When NOT to run construct Check the fit before question 1;