✅ v1.0 implemented. The client-side app lives in
src/; run it withnpm install && npm run dev. How to run, tailor the model, and the build-time choices are in the root README, EXTENDING.md, and DECISIONS.md. The scoring engine is a TypeScript twin of the verified model (scripts/verify-model.mjs); CI runs lint + tests + build.
Writing the code on the planned tech stack with consistent standards and conventions, under version control (Git), with code review to keep quality high. The decision model's values (factors, weights, fit vectors, rules, strings) live in editable config — never hard-coded — so they stay auditable.
Expected outputs
- Source code, built in the phase order of Build Spec v3 Section 12.
- Coding standards & linting setup, naming conventions, pre-commit hooks.
- Pull requests with mandatory review (see CONTRIBUTING.md).
References
- Feature-Maturity Playbook —
F0-02(code standards), theTECH-*tasks, and the global Definition of Done. - UI/UX Execution Playbook — implementing the prototype's UX.
- Build Spec v3 Section 13 — code organization.
Contributions are welcome — see ../../CONTRIBUTING.md.