A Firm's Archive of Past Projects: Work That Never Gets Reused

An architecture firm accumulates a project archive over the years — drawings, renders, alternative solutions, some of which were never built but stay valuable as a starting point for future work. Whether a similar solution was used before, and on which project, is usually a question only one specific architect's memory can answer.

Digercules goes through the firm's project archive and builds a catalog from it: building type, solutions applied, versions, what was actually built versus what stayed at the concept stage — so past work can be searched by the substance of the task, not by project name.

How it works

Processing runs either entirely on the client's own hardware, or — if that hardware isn't powerful enough — is delegated to a specific external machine over a closed peer-to-peer channel (not a public cloud): the compute is physically located in the Caucasus and Eastern Europe, the client is always told explicitly which machine and which jurisdiction is doing the processing, and only text/structured results come back — never the source files. Client projects stay under the same access control — processing runs on direct instruction, and what comes out is a catalog of solutions, not the client's actual drawings.

Objections

"Client projects are confidential" — processing doesn't publish or hand materials to third parties; the catalog is used only inside the firm.

"We already remember our own projects" — that works for a firm with a few architects and a small number of projects; it stops working once a generation of architects turns over, or the archive grows over decades.

First contact

A pilot on the archive of one project typology (say, one firm's residential buildings over 5 years) — a catalog of solutions searchable by task type. The decision on access to the project archive sits with the firm's principal, not a line architect.