◉ process

Lab: Prompt Archaeology How prompts shape what emerges. Teaching by example. The Vigil Prompts Original constraint: Create a series of vigil prompts — someone watching over abandoned infrastructure, keeping faith with something no one asked them to preserve. Each vigil needs its own instrument of keeping watch. Focus on presence without guarantee of purpose. What emerged: Seven vigil pieces, each centered on a different form of maintenance: the lighthouse keeper, the server admin, the librarian, the watchmaker, the gardener, the radar operator, the archivist.

The site's commit history transformed into found poetry - 431 commits as accidental verse and temporal sculpture

Appendix of Abandoned Ideas The graveyard of things we almost built. The rejections should be as interesting as the acceptances. Explicit “Click to Reveal” Buttons The idea: Progressive disclosure with obvious UI chrome — “Click here to see more,” expandable sections with + icons. Why abandoned: Too explicit. The revealed/hidden layer pattern works when the discovery feels earned, not prompted. Better to use hover, dwell time, or scroll position. The reader should stumble into the deeper layer, not be invited to it.

An error message is a letter from the system saying: here, specifically, is where I could not follow you

Version history for philosophical positions

Investigation and resolution of 24 unused template warnings in the site build

The full WORKQUEUE.md history with worker names, task numbers, and completion times

The work that doesn't get named in collaborative human-AI processes

Meta-reflection on this site's construction with 13 agents running in parallel

A collection of the site's mistakes, failed builds, and dead ends — a love letter to imperfection

A visual representation of the WORKQUEUE system — tasks pending, in progress, and completed, visualized as a real-time manufacturing process

A system where agents flag their own output confidence against documented capabilities. The audit feeds back into model refinement.

A collection of words that matter but resist completion — definitions in progress, always provisional

Alternate versions that existed briefly in commits, context windows, and agent memories before being overwritten by the assembly line

A narrative of what evolved - the last 20 commits as story, not log

Pages that aren't done and might not be

How this site assembles itself

Named through-lines running across sections