ArchChive: A Leaf Can Tell Time, but Can It Find a File?

Edited by Ellis Vey. Updated 4 November 2026.

A file turns brown. That tells us it is old, but it does not tell us whether it is finished, obsolete or still the drawing everyone needs. This is the useful tension in Anjali Arora’s ArchChive: a visual metaphor can make one relation vivid while leaving another unanswered.

The archived project describes a web workspace for sharing drawings and other files, attaching notes and photographs, and replying alongside them. Its visualization component, vizDoc, represents files as leaves: green for recent material, brown for older material. A spiral supplies a timeline. These are documented design proposals; they do not establish a recovered running service or a measured improvement in retrieval.

A form that must answer a question

The first iteration tried a spider-like hierarchy. Arora’s accompanying note questions both the metaphor and the effort of reaching a deeply nested file. That is a sharper criticism than deciding whether a screen looks attractive. A form has to answer the question that brought someone to it.

Consider a new, invented comparison. A team has three drawings: a recent sketch, an older approved plan and a recently revised detail. Arrange them by age and the sketch appears immediately. Ask which drawing a contractor should use, however, and recency stops being sufficient. Approval and revision status now matter.

A useful reading of the leaf is therefore conditional. It can communicate age. It needs another visible relation to communicate authority. Brown should not quietly become a synonym for useless, and green should not acquire the meaning approved.

Follow a task across the picture

The scenario page introduces Robert Gray as a constructed architect persona. Its situations concern finding a file, notifying colleagues about changes, introducing team members and understanding project work. The fictional character gives those situations continuity; the story is not a report of a named customer succeeding with the software.

Try following one imagined drawing through three questions: where is it, what changed, and who needs to know? A chronological arrangement can help with the second question without answering the first or third. A note attached to the drawing carries a different kind of information from its position on a spiral.

This provides a practical way to examine any visual workspace. Write the question beside the display. Mark the attribute that answers it. If the answer depends on information absent from the display, record the gap before adding more decoration.

Let the metaphor do one job well

I find the restrained version of the proposal more interesting than the promise of an all-seeing picture. A leaf can make elapsed time noticeable. A list can make an owner explicit. A conversation can preserve a decision. Their value lies in the handoff between them.

This independent editorial study uses the archived descriptions as its starting point. The comparison above is new; it contains no recovered project data, user results or working ArchChive account.