Cookie Consent Audit & Fix
To close: Write the Outcome noting the fix and the later removal. · Move the cycle to HISTORY.md.
last activity May 27
Website visitors were asked to accept cookies again after every release, because the site kept their answer in a fragile place.
The answer moved into a real cookie the whole site shares. Two months later the cookie banner was removed from the site altogether, so the fix no longer matters.
Documents
With file names, on their own page →Start here
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
A visitor's cookie answer was kept in a real cookie for a year, shared by the whole site.
Consent that survives a release · came from Mark Parson
- Later the banner and the tracking it guarded were removed from the website. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
A visitor's cookie answer was kept in a real cookie for a year, shared by the whole site.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Fixed the banner, then removed it
Committed the fix (merged 2026-05-27) and, two months later, the removal of cookie consent (2026-07-30). The record names nobody, so this rests on git authorship.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 0 decisions · 7 key-change entries · 193 words · 0 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c5 →