Skip to content

Documentation

Documents for people rather than for development, such as a user's guide or a deployment procedure. What goes here is up to the developer.

Some documents here are Derived Documents: use cases, business rules, or an architecture description, derived from the specifications for readers outside the development team. A Derived Document is never a source. Change the specifications first, then the derived document. It may name the capabilities it describes. With documentation: extended in .repo.yaml, use_cases/, business_rules/, and architecture/ hold a template each.

The assistant reads and changes this directory only when asked.

This file is written by repo update; keep notes in another file.