Traceability makes visible the usually hidden dimensions of publishing: who read what, what changed between versions, how did the work evolve from concept to final form, what paths did readers take through the content? Traceability acknowledges that work is not static but accumulates history through its creation, distribution, and reception. The counter to traceability is opacity or erasure, where changes happen invisibly and past states are overwritten rather than preserved.

Traceability operates at multiple levels: tracking versions of the work itself, recording how readers interact with it, and documenting the decisions behind changes. Version traceability preserves the evolution of content. Git and version control systems enable this for code and text, but tools like Notion and Google Docs have brought version history to more accessible publishing contexts. These systems track not just what changed, but who changed it and when, creating transparent records of collaborative authorship.

Interaction traceability records reader behaviors: what pages were visited, how long readers spent on each section, what paths they took through non linear content. While this can raise privacy concerns, consensual interaction tracking can create valuable feedback for creators and generate interesting artifacts of collective reading patterns. Decision traceability documents the "why" behind changes through changelogs, commit messages, or editorial notes. This turns the evolution of work into part of the work itself.

While traceability has become standard for the web as a medium due to its mutability, print is usually restricted by its immutability. But what if that very immutability could become a tool for traceability? If the only way to interact with a book is through irreversible gestures, then the book itself becomes a series of residues, traces of what the reader has seen, read, absorbed, interacted with. What traces should be preserved? Version history of the content? Reader interaction patterns? Editorial decisions and discussions?

Who can see the traces? Are version histories public or private? Can readers see how others navigated the work? Is traceability transparent or hidden? How long is traceability maintained? Forever? Until the next major revision? Until storage limits are reached? What interactions leave traces? Page turns, annotations, highlights, time spent, navigation paths, sharing behaviors? Can readers control their traces? Can they opt out of tracking? Delete their interaction history? Make their paths anonymous?

Cyberfeminism Index has a remarkable feature: every time you open a dropdown, it adds that article to a table of contents which you can then download as an aggregate PDF. While it is possible to retrace steps on most websites through browsing history or metadata, the trace of a user's path is usually not visible to the user themselves. This feature actively creates visible "residue" attached to user interactions, making a visible trace of the act of reading, exploring, browsing.

Google Docs version history shows every edit with timestamp and author attribution. You can see the work evolve keystroke by keystroke, watch collaborative decisions unfold, restore previous versions. The trace becomes a narrative of the work's creation. Git commit histories and changelogs document not just what changed but why, creating transparent records of decision making processes.

A Party to Print captures interactions (images, audio, data) as content, making the trace of the event into the substance of the publication. Analog traceability experiments explore how physical interactions leave marks. Projects using heat sensitive inks, pressure sensitive papers, or materials that visibly wear with handling turn use into trace. The red dye cover where handling stains your fingers and consequently all the pages you touch: the book records your reading path through color transfer. Marginalia and annotation systems like Hypothesis or built in e-reader highlighting create semi public traces where readers can see others' responses accumulated over time.

Projects exploring traceability employ visible version control that embeds changelog or version comparison directly in the published work rather than hiding it in backend systems. Reader path visualization creates visual representations of how readers navigate through content, potentially making these visible to other readers. Material traces use materials that visibly change with handling: papers that wrinkle, inks that fade or smudge, heat sensitive coatings, pressure sensitive substrates. Irreversible interactions design interactions that permanently alter the work: tearing perforation to reveal content, folding pages into new configurations, scratching away surfaces. Collective annotation enables readers to leave public or semi public notes that accumulate over time, creating layered interpretations. Timestamp visibility makes publication dates, last updated dates, and edit timestamps prominent rather than hidden. Evolution documentation publishes the "making of" as integral to the work itself, not as separate bonus content. Behavioral data visualization shows aggregate patterns of how readers engage: most read sections, common paths, time distributions.