Kind

Convention

How is it written down?

Recurring ways of writing, naming, and placing things so the same idea always looks the same.

Convention Build & Delivery

Actions

Local composite actions under .gitea/actions/ capture reusable orchestration steps, while the logic they orchestrate stays in the build system.

.gitea/actions/ 3

Convention Documentation & Metadata

Decision Records

Architecture decision records are a last resort, written only when the repository’s structure, code, tests, and owner documentation cannot make a choice clear.

docs/pdlc/decisions/ 2

Convention Infrastructure & Runtime

Derived Developer Identity

A developer deployment names its instance from the Terraform workspace, chosen from an override, the CI branch, or the local username — never from a per-developer file.

workspaces/ 3

Convention Documentation & Metadata

Managed Standard Files

Standard files copied into every repository carry a DO NOT EDIT header; they are changed at their source, never in the repository that received them.

./ 0

Convention Documentation & Metadata

Owner Documentation

Conventions are described beside the thing that owns them — a directory’s layout in its own README, a command’s behaviour in its module or script.

<area>/README.md 4

Convention Documentation & Metadata

Reference Over Duplication

Each fact is stated once, where it is maintained, and every other place that needs it points there instead of keeping a copy.

./ 2

Convention Environment & Tooling

Self-Documenting Help

make help is generated from ## comments on the targets themselves, so the list of commands cannot drift from the real ones.

scripts/build/ 1