# Germanic-derived Verb Vocabulary
This reference provides Germanic alternatives to Latin-derived verbs organized by semantic clusters. These terms can be used to maintain linguistic consistency within related function names, class hierarchies, or module-level names.
For core naming patterns and structural conventions, see the main
[nomenclature guide](nomenclature.md). For Latin-derived terms (project
default), see the [Latin-derived verb vocabulary](nomenclature-latin.md).
## Germanic Naming Philosophy
Germanic-derived terms often provide:
- **Directness**: `get` vs `access`, `make` vs `create`
- **Concrete imagery**: `grab` vs `acquire`, `sniff` vs `examine`
- **Technical familiarity**: `ping` vs `probe`, `dump` vs `save`
- **Compound flexibility**: `setup`, `handoff`, `unswitch`
Germanic terms should only be used to maintain consistency with existing terminology or because they form a better self-contained cluster of names than the equivalent Latin-derived terms (e.g., for the variants of some enums).
## Verb Prefixes by Semantic Cluster
### Analysis and Discovery
**find\_\** (discover)
Detects or determines value from environment or context.
**list\_\** (survey)
Lists or enumerates members of external resource collection.
**sniff\_\** (examine)
Retrieves metadata about resource without accessing full content. Informal but established in technical contexts.
**weigh\_\** (assess)
Examines data to derive insights or patterns.
### Component Initialization
**ready\_\** (prepare)
Fully initializes component, including registration of handlers/extensions. Used as verb, not adjective.
**setup\_\** (configure)
Applies settings or parameters to component, preparing it for operation. Compound from "set up".
### Computation
**reckon\_\** (calculate)
Computes value from one or more inputs using defined algorithm.
### Data Operations
**ask\_\** (query/request)
Performs structured data retrieval with parameters or filters. Also used for initiating requests.
**change\_\