Kind

Orchestration

How is the work sequenced and composed?

How work is sequenced, composed, and handed between commands, tools, and pipelines.

Orchestration Environment & Tooling

Make modules register their targets and requirements into shared lists, and aggregate targets are composed from whatever registered.

scripts/build/ 5

Orchestration Environment & Tooling

Networked setup hydrates the workspace once; validation then runs with OFFLINE=1 and never quietly re-downloads anything.

scripts/build/ 3

Orchestration Environment & Tooling

One small runner turns each lifecycle event into a directory of .sh hooks, run in lexical order and stopped by the first failure.

.devcontainer/lifecycle/ 1

Orchestration Product Code

Repository documentation is staged from docs/ into .cache/docs-site/ and mounted into a Hugo site, so the docs stay where they are owned.

.cache/docs-site/ 2

Orchestration Build & Delivery

make deploy is the whole deployment model: build the site, initialise and apply its Terraform root, upload public/, and invalidate the CDN.

scripts/deploy.sh 5

Orchestration Build & Delivery

Workflow YAML decides when automation runs and in what order, and hands the work itself to stable repository commands and reusable actions.

.gitea/workflows/ 4