← All notes
Institutional memory

Your records should outlive the software you keep them in

Land trusts, building handovers and local stewardship records run on clocks measured in decades. The software that holds them usually doesn't. Here is how to keep both the records and the reasons behind them.

Escherbridge

Equipment wears out in five to ten years, and software companies pivot or shut down even faster. The things they're hired to keep track of don't. A utility pipe map, a co-op's maintenance history, a 99-year community land lease or the inspection record of a building at Tie Town [TX] will outlast almost every startup hired to host it.

When all of that lives only inside someone else's subscription, continuity fails quietly. Five years after the handoff the board has a new treasurer, the login has lapsed, and "export everything" hands back a spreadsheet that has lost the links explaining why an easement was amended or who signed off on a structural change.

The thirty-year test

The people behind SQLite, one of the most widely used pieces of software in the world, propose a plain test: could someone open your records thirty years from now with ordinary tools, without the original program? Keeping records in a single, self-contained file that any standard tool can read turns a backup from a rescue mission into copying one file. Building projects learned the same lesson: name the exact version of the file standard you're using, rather than trusting that "the export" will mean the same thing to the next team.

The half nobody writes down: why

Owning the files doesn't mean anyone will understand them later. The record also needs the reasons. In 2011 Michael Nygard suggested keeping a short note for each significant decision, so whoever inherits the system knows why something is the way it is before they "fix" it. A co-op board or a land trust council can use exactly the same habit.

Sources

  1. SQLite Consortium, SQLite As An Application File Format
  2. Martin Kleppmann et al., "Local-first software: You own your data, in spite of the cloud," Ink & Switch, April 2019
  3. National Institute of Building Sciences, National BIM Standard–United States (NBIMS-US)
  4. Michael Nygard, "Documenting Architecture Decisions," 15 November 2011

Related