Glossary

Term	Code name	Definition
Artifact	ArtifactConfig	One deliverable of a repository, such as a service, a library, firmware, or a circuit board; generated into the repository root (single) or its own subdirectory (mono).
Capability Specification		The single specification of one capability of a generated repository, from which the assistant derives tests, interface descriptions, and glossary terms.
Component Test		A test of units working together, such as a use case, with mocks at the layer boundaries; programmed or a scenario, and counted by make coverage (capability 011).
Derived Document		A document derived from the Working Documents for readers outside development, such as use cases or a user's guide; lives in docs/ and is never a source.
Developer-owned file		A file repo update writes on its first run only and never touches afterwards, e.g. README.md or source code.
Documentation Mode		lean or extended; sets the ADR template and whether the repository has Derived Documents for readers outside the development team.
Generator-owned file		A file repo update refreshes on every run, e.g. .claude/rules/ or the CI pipeline.
Input Document		A document handed to development, such as a requirements specification; lives in specs/inputs/ and is translated into Capability Specifications, never implemented directly.
Integrative Test		A Component Test with one real dependency, such as a database in a container; Martin Fowler's narrow integration test. Runs apart from make test and is not counted by make coverage.
Module		A coarse unit of generation the developer selects per artifact, e.g. ci or bdd; groups the generator's internal units.
Next Step	NextSteps	A manual step the developer has to take after an artifact is generated; without it, a make target or the pipeline fails, e.g. committing go.sum.
Profile	ProfileKey	The combination of language and project type of an artifact; decides which modules it offers.
Repository configuration	Config	.repo.yaml at the repository root; describes the repository and its artifacts and is owned by the developer.
Repository type	RepoType	single (one artifact at the root) or mono (one artifact per subdirectory).
Requirements Source		repo or external; sets whether the Capability Specifications are files in specs/capabilities/ or issues in an issue tracker.
Unit Test		A test of the smallest unit, such as one function, often without a mock; counted by make coverage.
Working Document		A document that development works with and keeps in step with the code, such as a Capability Specification, the glossary, an ADR, or a feature file; the single source of truth.