Since the beginning of the damn project, it is ready for two kinds of areas -- current and finished. The original idea was to have the "clones" of current_areas, current_squares, and current_commits tables and store the finished read-only areas (and squares and commits) in them. The database is ready for this, see 70_damndb.sql of the damn-deploy repo.

However, there are two main disadvantages of this approach: (1) There must be an API to retrieve the data from the database basically duplicating and/or complicating the code of the damn-server repo; (2) the database has to serve static, read-only data. Both are against the damn project philosophy, particularly the simplicity (1) and the performance (2).

The proposed solution is to create new service (or even better--update upkeep service) similar to rss_gen of the damn-deploy repository that would (1) create static file containing finished area, it's squares, and commits, (2) delete the finished area, it's squares, and commits from the database, (3) serve the static file at some subdomain.