0001: A repository of its own

Decision: The method one person follows from a problem to its result is one problem, so it gets one public repository, set up with its scope and nothing more.

Status: accepted, 2026-11-02. Shape: decision record.

Context

  • The maintainer's rule for the family: one repository per problem, and no overlap between two. A problem left inside a wider repository makes every user of it depend on everything else there, which is why an earlier, wider repository was paused.
  • Six repositories of the reader-ergonomics family were set up the same way on 2026-10-29: scope first, published empty, the review as the first job, the name provisional until that review's frame step.
  • The boundary with the neighbours is drawn on the front page's scope table. In short: the genres keep their documents, software-design keeps the design document and the decision record, ai-augmented-project keeps the model and the machine.

Decision

  • One public repository for this problem, under the family's provisional prefix, renamed when the review names it.
  • At its start it holds its scope, the questions its review must answer, the checks of reader-ergonomics in CI, a site, and this record. Nothing of the work itself.
  • It pins reader-ergonomics v1.21.0 by commit, and reader-ergonomics-topic v0.6.1 by commit, and links down only.

Consequences

  • A later session can start from the front page alone: the scope, the first job and the questions are there.
  • A fact that belongs here is linked from the neighbours, never copied; a fact that belongs to a neighbour is linked from here.
  • Bad: a repository with a scope and no content is thin for as long as the review waits, and a rename after the frame step moves the address once.

See also

Decisions; the front page, where the scope and the first job are.