# Lexicon terms whose category is taxonomy-classification-naming

> 61 records

This index as JSON: https://banes-lab.com/json/api/facets/lexicon/category/taxonomy-classification-naming

## Entries

- [Concern Tag](https://banes-lab.com/records/lexicon/concern-tag.md): A formal definition of the role a file plays, drawn from the closed concern vocabulary and carried as the last dot-segment before the extension.
- [Subject Slot](https://banes-lab.com/records/lexicon/subject-slot.md): A facility that names who or what a file serves, occupying the first dot-segment of the filename.
- [Variant Slot](https://banes-lab.com/records/lexicon/variant-slot.md): A facility that narrows a subject to one facet, occupying the segment between subject and concern and present only on collision or facet ambiguity.
- [Container Level](https://banes-lab.com/records/lexicon/container-level.md): A facility that partitions a governed root by grouping axis, declared as a closed set and anchoring the depth count at level one.
- [Concern Folder](https://banes-lab.com/records/lexicon/concern-folder.md): A facility that holds every file of one concern and whose label the file's concern tag must equal.
- [Subject Folder](https://banes-lab.com/records/lexicon/subject-folder.md): A facility that separates two sets of one concern under a container, present if and only if the sets must not merge.
- [Governed Root](https://banes-lab.com/records/lexicon/governed-root.md): A rule or precondition that a path falls under the taxonomy only where its root is declared, so an undeclared tree is ungoverned and a declared one is governed in full.
- [Flat Bucket](https://banes-lab.com/records/lexicon/flat-bucket.md): A facility that holds one collection concern as files with no folders beneath it, declared rather than inferred from shape.
- [Ignore Declaration](https://banes-lab.com/records/lexicon/ignore-declaration.md): Descriptive data about the names skipped wherever they appear under a governed root, covering build output, vendored sources, tool caches and ecosystem-fixed names.
- [Depth Cap](https://banes-lab.com/records/lexicon/depth-cap.md): A rule or precondition that every governed file resolve within a fixed number of folders from its governed root, the container included and the file excluded.
- [Ordered Role Sequence](https://banes-lab.com/records/lexicon/ordered-role-sequence.md): A rule or precondition that each folder depth consume a role strictly later than the depth before it, so container, subject and concern may be skipped but never repeated and never revisited.
- [Layer Spine](https://banes-lab.com/records/lexicon/layer-spine.md): A conceptual representation of the system-decomposition spectrum that totally orders every concern from domain through product and supplies the tie-break direction.
- [Collection Concern](https://banes-lab.com/records/lexicon/collection-concern.md): A formal definition of a concern whose file defines many members at once, plural in both the folder label and the file tag.
- [Single-Unit Concern](https://banes-lab.com/records/lexicon/single-unit-concern.md): A formal definition of a concern with one instance per file, pairing a plural folder label with a singular file tag.
- [Glob Resolvability](https://banes-lab.com/records/lexicon/glob-resolvability.md): The degree to which one depth-unanchored pattern resolves every file or every folder of a concern across the whole tree.
- [Placement Predictability](https://banes-lab.com/records/lexicon/placement-predictability.md): The degree to which a file's correct location is derivable from its role alone, with exactly one legal answer.
- [Naming Expressiveness](https://banes-lab.com/records/lexicon/naming-expressiveness.md): The degree to which a closed vocabulary limits how precisely the developer can name a file that its declared words do not yet cover.
- [Tree Compactness](https://banes-lab.com/records/lexicon/tree-compactness.md): The degree to which a small module can stay in few files and folders rather than expanding into one concern folder per role.
- [Classification Judgment](https://banes-lab.com/records/lexicon/classification-judgment.md): The activity of reading a file and assigning its concern by its primary responsibility, which no pattern-match can perform on its behalf.
- [Vocabulary Admission](https://banes-lab.com/records/lexicon/vocabulary-admission.md): The act of reasoning a proposed word against the declared categories and admitting it only by developer-approved registry edit.
- [Identity Migration](https://banes-lab.com/records/lexicon/identity-migration.md): The activity of renaming an artifact and updating every reference to it in the same pass, so no reference is left dangling.
- [Shape-Discovered Surface](https://banes-lab.com/records/lexicon/shape-discovered-surface.md): A facility that collects its members by matching a pattern rather than by literal path, so a rename silently changes what it collects.
- [Container-by-Container Reshape](https://banes-lab.com/records/lexicon/container-by-container-reshape.md): The practice of converting one container at a time to the taxonomy, updating every reference in the same pass and holding the gate green between each.
- [Is-A Test](https://banes-lab.com/records/lexicon/is-a-test.md): A technique for deciding concern membership by asking whether a file is-a the proposed word, admitting it as a role when it is and as a domain noun when the system merely has-a it.
- [Rejection Table](https://banes-lab.com/records/lexicon/rejection-table.md): A formal definition of each near-miss word already considered and refused, recording the meta concern that covers it so the same word is not proposed twice.
- [Covering Concern](https://banes-lab.com/records/lexicon/covering-concern.md): A formal definition of the declared word that already fills a proposed word's role, resolved from the rejection table so a refusal carries its own replacement.
- [Reverse Coverage Resolution](https://banes-lab.com/records/lexicon/reverse-coverage-resolution.md): A technique for answering which declared words cover a candidate, by indexing the rejection table on its refused words rather than on the concerns they map to.
- [Free-Form Folder Level](https://banes-lab.com/records/lexicon/free-form-folder-level.md): A folder level resolving to no declared word, so the path is conventional rather than checkable and classification has more than one right answer.
- [Unguided Refusal](https://banes-lab.com/records/lexicon/unguided-refusal.md): Reporting an undeclared word without naming the declared word that covers it, so the developer's or the model's next attempt is another guess and the closed set reads as an obstacle rather than a map.
- [Borrowed Synonymy](https://banes-lab.com/records/lexicon/borrowed-synonymy.md): Deciding whether two declared words overlap from a general-language corpus rather than from the roles they name, so distinct concerns collide on their everyday senses and domain overlaps go unseen.
- [Vocabulary Inflation](https://banes-lab.com/records/lexicon/vocabulary-inflation.md): Admitting a word whose role a declared word already covers, such as a synonym or an abbreviation of it, so one role gets two words and classification gets two right answers.
- [Ignore-List Silencing](https://banes-lab.com/records/lexicon/ignore-list-silencing.md): Answering a finding by adding the path to the ignore declaration, removing authored source from the taxonomy entirely and hiding every future violation under the same name.
- [Depth-Relief Container](https://banes-lab.com/records/lexicon/depth-relief-container.md): Declaring a container to shorten a path or to house files that resist placement, turning the level that anchors the depth count into an escape from it.
- [Restated Set Member](https://banes-lab.com/records/lexicon/restated-set-member.md): Naming a file with the subject its folder already declares, so the member repeats the set and the name carries no information.
- [Saturated Role Tag](https://banes-lab.com/records/lexicon/saturated-role-tag.md): Classifying a file under a label that names a stature or fits every role, such as util or helper, so it attaches to lifecycle owners, caches, registries and coordinators alike and excludes nothing.
- [Concern-Swallowing Compound](https://banes-lab.com/records/lexicon/concern-swallowing-compound.md): Fusing a subject and a concern into one word, so the tag that should terminate the name is buried inside it and no glob resolves the file.
- [Downward Nesting](https://banes-lab.com/records/lexicon/downward-nesting.md): Relieving collision or breadth pressure by adding a folder level, breaking the depth cap that both overflow slots exist to protect.
- [Automated Reshape](https://banes-lab.com/records/lexicon/automated-reshape.md): Renaming by tool across a tree holding shape-discovered surfaces, so the rewrite reports clean while an aggregator that collected by suffix now collects nothing.
- [Nominalized Process Word](https://banes-lab.com/records/lexicon/nominalized-process-word.md): Admitting a word naming what the system does rather than what it has, so the vocabulary accumulates activities that classify nothing.
- [Multi-Role File](https://banes-lab.com/records/lexicon/multi-role-file.md): Keeping a file whose primary responsibility is two concerns, forcing an arbitrary tag instead of surfacing the split the ambiguity reports.
- [Reasoning in the Registry](https://banes-lab.com/records/lexicon/reasoning-in-the-registry.md): Writing the rules about a declaration into the declaration file itself, producing a document in a schema's format that no code reads.
- [Mass Concern](https://banes-lab.com/records/lexicon/mass-concern.md): A formal definition of a concern named for an uncountable role, singular in both the folder label and the file tag, as a configuration or a state is.
- [Compound Marker](https://banes-lab.com/records/lexicon/compound-marker.md): A formal definition of the declared words, such as test, generated or rule, that exempt a filename from the naming grammar when they sit just before the extension, while the file's placement stays governed.
- [Ecosystem-Fixed Name](https://banes-lab.com/records/lexicon/ecosystem-fixed-name.md): Descriptive data about the filenames an external tool finds by exact name, such as package manifests, lockfiles and compiler configurations, which are never renamed to the grammar.
- [Structurally Exempt File](https://banes-lab.com/records/lexicon/structurally-exempt-file.md): Descriptive data about the files that carry their own resolution contract, such as an aggregator collected by shape, a build entry named in an entry map, and a generated file rewritten on every run.
- [Conversion Record](https://banes-lab.com/records/lexicon/conversion-record.md): A formal definition of the record written for each file a conversion names, holding its responsibilities with the symbols behind them, its chosen concern and subject, the candidates refused, and the verdict on any file that shares its job.
- [Alignment Entry](https://banes-lab.com/records/lexicon/alignment-entry.md): Descriptive data about one whole reading of a conversion protocol, carrying the content hash of the revision read and the scope it covers, which every conversion record written after it cites.
- [Re-Alignment Cadence](https://banes-lab.com/records/lexicon/re-alignment-cadence.md): A rule or precondition that only a bounded run of conversion records may cite one alignment entry, so a long conversion re-reads its protocol before the rules it applies fade from working context.
- [Frozen Baseline](https://banes-lab.com/records/lexicon/frozen-baseline.md): Descriptive data about the files already conformant when a conversion's record gate shipped, pinned once into a generated set that never grows, so only a file renamed or moved afterwards owes a record.
- [Word-Boundary Case](https://banes-lab.com/records/lexicon/word-boundary-case.md): A formal definition of a naming case by where one word ends and the next begins, whether at a capital letter as in camel and pascal case or at a joiner as in snake and kebab case.
- [Unreferenced Export Triage](https://banes-lab.com/records/lexicon/unreferenced-export-triage.md): The activity of deciding, for each export nothing imports, whether a call site should use it, whether it is capability waiting for a consumer, whether it is superseded, or whether it went with a merged duplicate.
- [Variant-Masked Duplicate](https://banes-lab.com/records/lexicon/variant-masked-duplicate.md): Resolving a naming collision by giving the second file a variant, so two files doing one job keep two names and the duplication becomes permanent.
- [Stranded Test](https://banes-lab.com/records/lexicon/stranded-test.md): Leaving a test where its subject used to sit after the subject moves or splits, so the test tree no longer shows which tests cover which file.
- [Adjective Slot Word](https://banes-lab.com/records/lexicon/adjective-slot-word.md): Admitting an adjective such as lazy, bounded or shallow into a name slot, where no category can take it, so it describes a file without classifying it.
- [Plural Subject](https://banes-lab.com/records/lexicon/plural-subject.md): Using a plural noun such as stats or fields as a subject, where a subject names one thing the system has.
- [Grouping Label](https://banes-lab.com/records/lexicon/grouping-label.md): Using a bucket word such as misc, common, shared or core as a subject, which excludes no file and so classifies none, although grouping is exactly what a container is for.
- [Measurement Word](https://banes-lab.com/records/lexicon/measurement-word.md): Admitting a measurement or property such as duration, interval or budget as a vocabulary word, where it names data held in a file rather than a role or a thing.
- [Instance Identifier Word](https://banes-lab.com/records/lexicon/instance-identifier-word.md): Admitting the id of one registry entry, such as primary or dark-mode, into a vocabulary, so content enters a list that should hold only kinds of thing.
- [Sentence-Shaped Name](https://banes-lab.com/records/lexicon/sentence-shaped-name.md): Naming a file after an activity or a sentence because its role would not resolve, when the name's resistance shows that the file needs a split, a move or a merge.
- [Numeric Order Prefix](https://banes-lab.com/records/lexicon/numeric-order-prefix.md): Encoding a file's place in a sequence as a numeric prefix, so inserting one step renames every file after it and the grammar must parse a number it cannot classify.
- [Claimed Foreign Tree](https://banes-lab.com/records/lexicon/claimed-foreign-tree.md): Declaring a tree that another runtime resolves by name a governed root and renaming it to the grammar, which breaks that runtime at its next start without reorganising anything.