Plans the visible-colours change: a contrast cut-off that removes faint colours from the palette. Documents only; no code changes.
Why. Drawing the first painting from the reference photograph showed colours that pass the white-shade rule (SC3) but are still faint on the white background. Measured with the WCAG contrast ratio against white, the 30 palette colours range from 1.22 to 15.85. The eight palest lie between 1.22 and 1.96 and the next one is at 2.56. Raising the white threshold or keeping fewer colours would not fix it: even "all channels at or above 220" removes none of them, and the palest colours are among the most common in the photo.
What changes
Business Case: new objective O6 (every dot clearly visible: drop palette colours whose contrast with white is below 2.0) and criterion SC8, the WCAG contrast standard, an In Scope item, a risk row, and a Problem Statement sentence. SC3 is unchanged and still holds. Review: RC-007, a delta re-review (verdict Go).
New milestone MIL-003 Visible Colours, due 2026-10-10: a contrast measure and a faint-colour filter applied when the palette is extracted, with their tests, a real run that rechecks SC1 to SC8, and the code review. Five Go criteria, six plain technical tasks, no use cases. Review: RC-008 (verdict Go).
Project Plan: the MIL-003 gateway in the schedule and the Gantt chart, the new scope item, the dependency on MIL-001 and MIL-002, and a plan risk. Accepted by S01 in chat.
The limit of 2.0 was chosen by S01: it removes 8 of the 30 colours and keeps 22, in the natural gap of the data.
Commit links in the Version Histories are resolved in the last commit.
Not in this PR
The issues for MIL-003 are not created yet (sync-project.sh --apply is S01's call), and no code under src/ or tests/ changes. The code follows on its own branch after the milestone is synced.
Issues
No issue closed: this plans work whose issues do not exist yet.
## Summary
Plans the visible-colours change: a contrast cut-off that removes faint colours from the palette. Documents only; no code changes.
**Why.** Drawing the first painting from the reference photograph showed colours that pass the white-shade rule (SC3) but are still faint on the white background. Measured with the WCAG contrast ratio against white, the 30 palette colours range from 1.22 to 15.85. The eight palest lie between 1.22 and 1.96 and the next one is at 2.56. Raising the white threshold or keeping fewer colours would not fix it: even "all channels at or above 220" removes none of them, and the palest colours are among the most common in the photo.
**What changes**
- Business Case: new objective O6 (every dot clearly visible: drop palette colours whose contrast with white is below 2.0) and criterion SC8, the WCAG contrast standard, an In Scope item, a risk row, and a Problem Statement sentence. SC3 is unchanged and still holds. Review: RC-007, a delta re-review (verdict `Go`).
- New milestone MIL-003 Visible Colours, due 2026-10-10: a contrast measure and a faint-colour filter applied when the palette is extracted, with their tests, a real run that rechecks SC1 to SC8, and the code review. Five Go criteria, six plain technical tasks, no use cases. Review: RC-008 (verdict `Go`).
- Project Plan: the MIL-003 gateway in the schedule and the Gantt chart, the new scope item, the dependency on MIL-001 and MIL-002, and a plan risk. Accepted by S01 in chat.
- The limit of 2.0 was chosen by S01: it removes 8 of the 30 colours and keeps 22, in the natural gap of the data.
Commit links in the Version Histories are resolved in the last commit.
## Not in this PR
The issues for MIL-003 are not created yet (`sync-project.sh --apply` is S01's call), and no code under `src/` or `tests/` changes. The code follows on its own branch after the milestone is synced.
## Issues
No issue closed: this plans work whose issues do not exist yet.
Drawing the first painting from a photograph showed colours that pass the
white-shade rule (SC3) but are still faint on the white background. Add O6
(every dot clearly visible: drop palette colours whose contrast with white is
below 2.0) and SC8, plus the WCAG contrast standard, an In Scope item, a risk
row and the Problem Statement sentence. SC3 is unchanged and still holds.
The limit of 2.0 was chosen by S01 from the measured palette of the reference
image: 8 of its 30 colours fall below it and the next is at 2.56, so 22 remain.
Record the delta re-review as RC-007 (verdict Go, terms confirmed by S01).
Add milestone MIL-003 Visible Colours (due 2026-10-10): a contrast measure and a
faint-colour filter in the palette extraction, with their tests, a real run
that rechecks SC1 to SC8, and the code review. Five Go criteria and six plain
technical tasks, no use cases.
Revise PP-001: the MIL-003 gateway in the schedule and the Gantt chart, the new
scope item, the dependency on MIL-001 and MIL-002, and a plan risk. Accepted by
S01 in chat.
Record the review of MIL-003 as RC-008 (verdict Go, terms and Tasks wording
confirmed by S01).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Plans the visible-colours change: a contrast cut-off that removes faint colours from the palette. Documents only; no code changes.
Why. Drawing the first painting from the reference photograph showed colours that pass the white-shade rule (SC3) but are still faint on the white background. Measured with the WCAG contrast ratio against white, the 30 palette colours range from 1.22 to 15.85. The eight palest lie between 1.22 and 1.96 and the next one is at 2.56. Raising the white threshold or keeping fewer colours would not fix it: even "all channels at or above 220" removes none of them, and the palest colours are among the most common in the photo.
What changes
Go).Go).Commit links in the Version Histories are resolved in the last commit.
Not in this PR
The issues for MIL-003 are not created yet (
sync-project.sh --applyis S01's call), and no code undersrc/ortests/changes. The code follows on its own branch after the milestone is synced.Issues
No issue closed: this plans work whose issues do not exist yet.