Brick Work

0002. One name: brickwork

Context

The code base came from an upstream project and carried several names in packages, environment variables, blueprints and docs. A public release needs one consistent name.

Options considered

  1. brickwork everywhere, with exceptions only for upstream credit and the importer.
  2. Other options: not recorded.

Recommendation at the time: not recorded beyond Ulf's instruction.

Decision

Only the name brickwork is used, with no upstream product wording anywhere. The exceptions are upstream credit and the importer, which keeps the old table names it reads.

Consequences

Related: ADR 0001, 0008.