Architecture
Build & Delivery
Automation & CI/CD
.gitea/ is the repository’s automation control folder: event-driven workflows and local actions that orchestrate the repository’s own commands.
.gitea/
2Kind
Architecture
Where does it live, and how do the parts fit?
How the parts of a repository are arranged — where each area lives, what it is for, how parts compose, and where each boundary sits.
Architecture
Documentation & Metadata
Catalog Descriptors
Machine-readable repository identity that tells catalog systems what a repository is and produces, and where the authoritative definitions live.
.descriptor/
2Architecture
Documentation & Metadata
Code Map
A generated CODEMAP.md that says what each area of the repository is for and which local README to open next — a navigation guide, not a reference.
CODEMAP.md
2Architecture
Environment & Tooling
Command Surface
An identical root Makefile in every repository, with the repository’s own components declared once in scripts/build/repository.mk.
Makefile
4Architecture
Environment & Tooling
Development Container
The authoritative development environment for a repository — reusable features provide the toolchains, and repository-specific lifecycle hooks finish the workspace.
.devcontainer/
4Architecture
Infrastructure & Runtime
Environments
Thin, canonical deployable roots under env/ that compose reusable modules for a concrete deployment target and run without ad hoc parameters.
env/
4Architecture
Environment & Tooling
Linter Configuration
A single .linter/ directory holds the repository’s own lint configuration and overrides, layered over organisation defaults from the environment.
.linter/
2Architecture
Infrastructure & Runtime
Modules
Small, focused infrastructure building blocks with explicit inputs and outputs, consumed by deployable roots in env/ and workspaces/.
modules/
3Architecture
Infrastructure & Runtime
Pinned Module Composition
Every deployable root composes the same published module at the same pinned version, so roots differ only in backend, domain, and credentials.
env/
3Architecture
Documentation & Metadata
Product Development Life Cycle
docs/pdlc/ holds the durable product context behind a repository — problems, constraints, tradeoffs, and decisions — and nothing short-lived.
docs/pdlc/
2Architecture
Environment & Tooling
Scripts
Narrow, deterministic command helpers for make modules, CI, and local tooling — glue that takes its inputs from the caller and leaves orchestration to it.
scripts/
4Architecture
Product Code
Static Websites
Each child of www/ is a self-contained site root whose content, layouts, assets, and configuration travel together and whose output is disposable.
www/
3Architecture
Environment & Tooling
Tools
Repository tooling with stable command entry points and documented contracts — small applications that own a workflow, rather than glue around one.
tools/
2Architecture
Infrastructure & Runtime
Workspaces
Developer-oriented deployment roots under workspaces/ whose instance identity may come from the current user or branch, kept apart from canonical environments.
workspaces/
3No specification matches every filter.