Plan the Day 24 snake game: business case, stakeholders, dictionary, plan and five milestones

2026-10-13 14:11:42 +08:00
parent a73e941fb6
commit e004c34565
20 changed files with 1501 additions and 0 deletions
@@ -0,0 +1,66 @@
+# RC-004: Review of MIL-001
+
+## Metadata
+| Key | Value |
+| --- | --- |
+| ID | RC-004 |
+| CrossReference | [MIL-001], [QC-MIL-001], [QC-LANG-001], [DICT-001] |
+
+## Version History
+| Date | Status | Author | Reviewer | Change | Commit |
+| --- | --- | --- | --- | --- | --- |
+| 2026-10-13 | Proposed | Jens Tirsvad Nielsen | AI as stand-in for S01 | Initial version | pending |
+
+---
+
+## Artifact Under Review
+
+- Instance reviewed: [MIL-001]
+- Checklist used: [QC-MIL-001] and, for the language and domain, [QC-LANG-001]
+- Scope: full review
+- Language and domain: en / it
+- Language reviewer: none (the reviewer reads English and knows the IT domain)
+- Mode: autonomous, not independent (the reviewer is `AI as stand-in for S01`; the assistant also drafted the document)
+
+## Checklist Results
+
+| # | Criterion | Status | Evidence/Notes |
+| --- | --- | --- | --- |
+| 1 | A concrete deliverable is defined for every gate | Pass | Deliverable section names the files and results evaluated; 7 tasks are rows in `## Tasks`. |
+| 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Go / No-Go table has 12 criteria, each with an observable Go and No-Go (exit codes, text, file content, warnings). |
+| 3 | Dependencies on other milestones are explicitly mapped | Pass | Dependencies table names the milestone that must be accepted and merged first. |
+| 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | Traceability table cites [BC-001] objectives 8, 9, 10, 11 and 12 and the Success Criteria numbers. |
+| 5 | Milestone owner and approving reviewer are identified | Pass | Ownership table: Owner S01, Approving reviewer S01 (a stakeholder ID of [SA-001]). |
+| 6 | Milestone has a defined target date consistent with project constraints | Pass | Target Date is inside the plan window of [PP-001] (ends 2026-10-25) and the Business Case constraint. |
+
+## Language and Domain Results
+
+| # | Criterion | Status | Evidence/Notes |
+| --- | --- | --- | --- |
+| 1 | The Metadata table has a `Language` row and a `Domain` row, and neither is a placeholder | Pass | `Language` is `en` and `Domain` is `it` in Metadata. |
+| 2 | `Language` is a BCP 47 code and `Domain` is a value from the registry's domain list | Pass | `en` is a BCP 47 code; `it` is in the registry's domain list. |
+| 3 | The content (prose and table cells) is written in the stated language | Pass | All prose and table cells of MIL-001 are English. |
+| 4 | The register matches the one the registry gives for the artifact type | Pass | Register is the one the registry gives for the type; code names and commands appear in backticks only where a check needs them. |
+| 5 | Domain terms are the PO terms of the domain's dictionary, with no synonyms | Pass | Terms are those of [DICT-001]: score, high score, reset, continuous play, data file, scoreboard, snake, segment, head, tail, food; `game over` appears only for the base's behaviour and as the removed `game_over` identifier, as the dictionary's rules allow. |
+| 6 | Metadata keys, section headings, IDs and statuses are in English | Pass | Metadata keys, headings, IDs and statuses are English. |
+| 7 | No translated twin (`<name>.<language>.md`) exists beside the document | Pass | `docs/` holds one file per artifact; there is no `<name>.<language>.md`. |
+| 8 | A change of language or domain since the previous accepted version has a Version History row and was reviewed again | N-A | First version of the document: there is no earlier accepted version. |
+| 9 | A reviewer competent in the domain, and in the language, has confirmed that the domain terms are used correctly | Pass | The assistant, as stand-in for S01, reads English and knows the IT domain and checked the terms against [DICT-001]; task titles and criteria use dictionary terms. |
+| 10 | Abbreviations are spelled out on first use, in the stated language | Pass | Abbreviations (SQA, QC, PEP, CI, API, PyPI, FURPS+, RACI, ISO/IEC) are spelled out or defined on first use, or are standard names. |
+
+## Overall Verdict
+
+Go — all Mandatory criteria pass or are not applicable. The rows above were assessed on 2026-10-13 by the assistant that drafted the document, as stand-in for S01 in autonomous mode (chosen by S01 in chat on 2026-10-13). Mode: autonomous, not independent. This review is **not independent**: the drafter and the reviewer are the same assistant, and author and approver (S01) are one person in a single-participant project. S01 accepted the plan in chat on 2026-10-13; the verdict can be challenged in the run summary or on the pull request.
+
+## Action Items
+
+| Action | Owner | Due |
+| --- | --- | --- |
+| Challenge this `Go` in the run summary or on the pull request if the stand-in decision is not wanted | S01 | 2026-10-15 |
+
+---
+
+[MIL-001]: ../../milestones/mil-001-project-foundation.md
+[QC-MIL-001]: ../../../framework/qc/artifacts/qc-milestones-gateways.md
+[QC-LANG-001]: ../../../framework/qc/artifacts/qc-language-domain.md
+[DICT-001]: ../../dictionary.md