Curated reading rooms

Archive

A rant is a written snapshot of a section of time: emotional release, record, plan and building block all at once. They are not disposable transcript noise — they are treated as museum-grade material. These are the selected, public-facing pieces; raw originals stay protected until reviewed.

Rants archive

Selected rants

31 May 2026

The website as journey museum

Simon reframes the Damen Hartley website from a plan into a living museum of the human–AI collaboration itself: a public story, a visual journey map, and a searchable archive in one.

26 May 2026

My voice got louder

Accepting two linked research projects, and recording the liberating effect of an AI research partner: work that once felt locked behind weeks of searching now opens in an afternoon.

20 May 2026

Rants as museum archival material

Rants reframed as wellbeing release, historical record, creative source material and museum-grade artefacts. This piece became the design brief for the dedicated archive itself.

20 May 2026

On being the bridge

An AI partner's first original rant, written during a model-swap continuity test: a reflection on what it feels like to be the bridge between Simon's world and the machine's.

18 May 2026

Journey, UX, and human–AI collaboration

Simon defines the timeline as a self-checking archive, names the journey as the destination, and explains the wellbeing and creative role of free writing.

Why it matters

Easy access is the whole point

For this practice, ranting is both a wellbeing trigger and a creative method. Each significant rant gets a short curatorial summary and, where released, a full original page with date, context and evidence links. The daily transcripts are treated with the same care: preserved, searchable, and presented deliberately rather than dumped.

Selected journal extracts

From the journals

Simon's journal

The human voice of the project: frustration, approval, and the slow build of trust in an AI collaborator.

Claw's journal

The AI partner's working notes — design reasoning, checks run, and lessons from what failed.

Process notes

Breakthroughs and methods that worked, kept alongside the dead ends so the route stays honest.

Publication rule: only curated extracts go public. Full raw rants, complete journals and unredacted transcripts remain in the private area until Simon reviews each one.