No database

Decision · Acceptedspecs/decisions/publication/no-database

The graph (3 passages, no note) is built in memory and serialised (3 passages, no note) to model.json, canonically sorted and validated by a published schema (31 passages, no note); concordance render reads it without touching the sources (note: Source), and a Cypher export is provided for those who want the graph elsewhere. No server, no database and no state (36 passages, no note) between two builds (note: Build) other than the pipeline cache (note: Fingerprint cache): the model (note: Model) is a file that a pipeline (note: Pipeline) writes, commits (29 passages, no note), diffs and serves.

Affects

Properties

Status
Accepted
Decided on

2 keys: the status and the date are authoritative.

See the neighbourhood map6 pages6Neighbourhood mapNo database

Neighbourhood map No database

Distance1 hop

Neighbourhood map. The list below carries the same information as the map.existing pageword without a note

11 neighbours in total, more than the map shows.

textual equivalent

Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.