# Lexicon terms, part 4 of 4

This index as JSON: https://banes-lab.com/json/api/records/lexicon/_4

## Entries

- [Automated Control](https://banes-lab.com/records/lexicon/automated-control.md): The ability to enforce rules automatically at runtime without manual intervention.
- [Bounded Session Lifetime](https://banes-lab.com/records/lexicon/bounded-session-lifetime.md): The degree to which a session's validity is time-limited so that access does not persist indefinitely.
- [Coarse-Grained Permission Management](https://banes-lab.com/records/lexicon/coarse-grained-permission-management.md): The ability to manage access by assigning broad, role-level permission sets rather than per-individual grants.
- [Compromise Containment](https://banes-lab.com/records/lexicon/compromise-containment.md): The ability to keep a breach confined to one layer or segment so it cannot spread system-wide.
- [Confidentiality](https://banes-lab.com/records/lexicon/confidentiality.md): The degree to which data is kept secret from all but authorized parties.
- [Confidentiality of Stored Data](https://banes-lab.com/records/lexicon/confidentiality-of-stored-data.md): The degree to which data held at rest remains unreadable to anyone without authorized access.
- [Context-Aware Authorization](https://banes-lab.com/records/lexicon/context-aware-authorization.md): The ability to base access decisions on the runtime context of a request, such as its attributes, its environment and the resource's state.
- [Control Selection](https://banes-lab.com/records/lexicon/control-selection.md): The activity of choosing which security controls to apply based on identified threats and their priority.
- [Data Protection](https://banes-lab.com/records/lexicon/data-protection.md): The ability to safeguard data against unauthorized access, loss, or disclosure throughout its lifecycle.
- [Fine-Grained Access Control](https://banes-lab.com/records/lexicon/fine-grained-access-control.md): The ability to grant or deny access at a precise level using specific attributes rather than broad roles.
- [Forged-Request Rejection](https://banes-lab.com/records/lexicon/forged-request-rejection.md): The ability to detect and reject requests that a user did not intentionally initiate.
- [Identity-Aware Authorization](https://banes-lab.com/records/lexicon/identity-aware-authorization.md): The ability to make access decisions grounded in a verified caller identity.
- [Injection Prevention](https://banes-lab.com/records/lexicon/injection-prevention.md): The ability to stop untrusted input from being interpreted as executable code or commands.
- [Injection-Safe Data Access](https://banes-lab.com/records/lexicon/injection-safe-data-access.md): The ability to query data such that input can never be interpreted as part of the query structure.
- [Integrity](https://banes-lab.com/records/lexicon/integrity.md): The degree to which data is protected from unauthorized or undetected alteration.
- [Ongoing Assurance](https://banes-lab.com/records/lexicon/ongoing-assurance.md): The ability to demonstrate continuously that controls remain effective, rather than only at audit time.
- [Perimeterless Security](https://banes-lab.com/records/lexicon/perimeterless-security.md): A security model that trusts no network location implicitly and verifies every request regardless of origin.
- [Priority-Based Controls](https://banes-lab.com/records/lexicon/priority-based-controls.md): The ability to apply controls in order of risk priority, addressing the greatest exposure first.
- [Privacy Compliance](https://banes-lab.com/records/lexicon/privacy-compliance.md): The degree to which a system meets the privacy obligations imposed by law and policy.
- [Proactive Risk Reduction](https://banes-lab.com/records/lexicon/proactive-risk-reduction.md): The ability to reduce risk by designing safeguards in from the start rather than patching flaws later.
- [Reduced Blast Radius](https://banes-lab.com/records/lexicon/reduced-blast-radius.md): The degree to which the impact of a compromise is confined to a limited scope.
- [Reduced Exploitability](https://banes-lab.com/records/lexicon/reduced-exploitability.md): The degree to which fewer exposed features leave a system harder to exploit.
- [Reduced Misconfiguration Risk](https://banes-lab.com/records/lexicon/reduced-misconfiguration-risk.md): The degree to which safe defaults lower the chance of an insecure configuration.
- [Regulatory Alignment](https://banes-lab.com/records/lexicon/regulatory-alignment.md): The degree to which a system conforms to the laws and regulations that govern it.
- [Resource Protection](https://banes-lab.com/records/lexicon/resource-protection.md): The ability to ensure that only permitted operations reach a protected resource.
- [Revocable Access](https://banes-lab.com/records/lexicon/revocable-access.md): The ability to withdraw a principal's access immediately when a session or grant is terminated.
- [Safe Credential Handling](https://banes-lab.com/records/lexicon/safe-credential-handling.md): The ability to store, transmit, and use credentials without exposing them.
- [Safe Rendering](https://banes-lab.com/records/lexicon/safe-rendering.md): The ability to display untrusted data without allowing it to execute as markup or script.
- [Secure Communication](https://banes-lab.com/records/lexicon/secure-communication.md): The ability to exchange data over a channel protected from interception and tampering.
- [Secure Configuration](https://banes-lab.com/records/lexicon/secure-configuration.md): The degree to which a system's settings and secrets are arranged to minimize exposure.
- [Zero Trust](https://banes-lab.com/records/lexicon/zero-trust.md): A security stance that grants no implicit trust and continuously verifies every access request regardless of its source.
- [Analytics/Personalization](https://banes-lab.com/records/lexicon/analytics-personalization.md): The ability to analyze collected data and tailor experiences to individuals, in tension with strict data minimization.
- [Certificate Management](https://banes-lab.com/records/lexicon/certificate-management.md): The activity of issuing, deploying, renewing, and revoking the digital certificates that transport encryption depends on.
- [Client Complexity](https://banes-lab.com/records/lexicon/client-complexity.md): The degree of additional effort a protective measure imposes on client implementations.
- [Developer Ergonomics](https://banes-lab.com/records/lexicon/developer-ergonomics.md): The degree to which a system is convenient and pleasant for developers to work with.
- [Dynamic Query Flexibility](https://banes-lab.com/records/lexicon/dynamic-query-flexibility.md): The degree of freedom to vary a query's structure at runtime, constrained when inputs must be bound as parameters.
- [Ease of Initial Use](https://banes-lab.com/records/lexicon/ease-of-initial-use.md): The degree to which a system is easy to start using without upfront configuration.
- [Feature Exposure](https://banes-lab.com/records/lexicon/feature-exposure.md): The degree to which functionality is made accessible, which broadens capability but enlarges the attack surface.
- [Formatting Flexibility](https://banes-lab.com/records/lexicon/formatting-flexibility.md): The degree of latitude to present output in varied formats, constrained when encoding must be strict.
- [Input Flexibility](https://banes-lab.com/records/lexicon/input-flexibility.md): The degree to which a system accepts varied or loosely-structured input, in tension with strict validation.
- [Key Operations](https://banes-lab.com/records/lexicon/key-operations.md): The degree of operational burden imposed by generating, rotating, and safeguarding cryptographic keys.
- [Latency/Complexity](https://banes-lab.com/records/lexicon/latency-complexity.md): The degree of added latency and complexity introduced by verifying every request rather than trusting a perimeter.
- [Operational Convenience](https://banes-lab.com/records/lexicon/operational-convenience.md): The degree to which broad access makes day-to-day operations easier, in tension with least privilege.
- [Pipeline Complexity](https://banes-lab.com/records/lexicon/pipeline-complexity.md): The degree of intricacy added to a delivery pipeline by embedding continuous checks within it.
- [Policy Maintenance](https://banes-lab.com/records/lexicon/policy-maintenance.md): The activity of keeping codified policies correct and current as requirements evolve.
- [Role Explosion](https://banes-lab.com/records/lexicon/role-explosion.md): The degree to which roles proliferate into many narrow definitions as access requirements grow.
- [Speed](https://banes-lab.com/records/lexicon/speed.md): The degree to which delivery proceeds rapidly, in tension with the caution that managing risk requires.
- [Team Velocity](https://banes-lab.com/records/lexicon/team-velocity.md): The rate at which a team delivers completed work, which governance overhead can slow.
- [Usability](https://banes-lab.com/records/lexicon/usability.md): The ease with which users can accomplish their goals with a system.
- [User Convenience](https://banes-lab.com/records/lexicon/user-convenience.md): The degree to which a system minimizes friction and effort for its users.
- [Central Database Bottleneck](https://banes-lab.com/records/lexicon/central-database-bottleneck.md): Funneling all state through one shared database that becomes the system's scaling bottleneck.
- [Framework-Centric Core](https://banes-lab.com/records/lexicon/framework-centric-core.md): Building the core around a specific framework, so the framework's concerns permeate the domain.
- [Layer Leakage](https://banes-lab.com/records/lexicon/layer-leakage.md): Letting an inner layer depend on an outer one, violating the direction of the dependency rule.
- [Layer Skipping](https://banes-lab.com/records/lexicon/layer-skipping.md): Bypassing intermediate layers to call a distant layer directly, undermining the layering.
- [Monolithic Transform Function](https://banes-lab.com/records/lexicon/monolithic-transform-function.md): Doing all processing in one large transform instead of a series of composable filter stages.
- [Package by Technical Layer Only](https://banes-lab.com/records/lexicon/package-by-technical-layer-only.md): Organizing code by technical layer alone, scattering each feature across many packages.
- [Shared Monolithic Application](https://banes-lab.com/records/lexicon/shared-monolithic-application.md): Building one large shared application instead of composing independently-governed services.
- [Unbounded Big Ball of Mud](https://banes-lab.com/records/lexicon/unbounded-big-ball-of-mud.md): Letting a system grow without structure into a tangled mass with no clear boundaries.
- [Contract-Governed Service Reuse](https://banes-lab.com/records/lexicon/contract-governed-service-reuse.md): The ability to reuse services across an enterprise through well-defined contracts.
- [Database-Bottleneck Removal](https://banes-lab.com/records/lexicon/database-bottleneck-removal.md): The ability to eliminate the shared-database bottleneck by holding state in distributed memory.
- [Decentralized Ownership](https://banes-lab.com/records/lexicon/decentralized-ownership.md): The ability for separate teams to own, deploy and evolve their services independently.
- [External System Isolation](https://banes-lab.com/records/lexicon/external-system-isolation.md): The ability to isolate the core from external systems behind adapter boundaries.
- [Framework Independence](https://banes-lab.com/records/lexicon/framework-independence.md): The ability to keep business rules independent of any particular framework.
- [Independent Stage Testing](https://banes-lab.com/records/lexicon/independent-stage-testing.md): The ability to test each filter stage in isolation from the rest of the pipeline.
- [Infrastructure Independence](https://banes-lab.com/records/lexicon/infrastructure-independence.md): The ability to keep the core independent of the infrastructure it runs on.
- [Locality of Change](https://banes-lab.com/records/lexicon/locality-of-change.md): The ability to make a feature's changes in one place because its code is grouped together.
- [Reorderable Stages](https://banes-lab.com/records/lexicon/reorderable-stages.md): The ability to reorder or recombine independent processing stages.
- [Structured Code Organization](https://banes-lab.com/records/lexicon/structured-code-organization.md): The ability to organize code predictably by assigning each responsibility to a layer.
- [Transactional Simplicity](https://banes-lab.com/records/lexicon/transactional-simplicity.md): The ability to use straightforward local transactions when all state lives in one process.
- [Adapters](https://banes-lab.com/records/lexicon/adapters.md): Components that translate between a core's ports and the specific external technologies behind them.
- [Boundaries](https://banes-lab.com/records/lexicon/boundaries.md): The requirement that clear boundaries separate the concentric layers of the system.
- [Component Boundaries](https://banes-lab.com/records/lexicon/component-boundaries.md): The requirement that each component expose a well-defined boundary and interface.
- [Dependency Rule](https://banes-lab.com/records/lexicon/dependency-rule.md): The requirement that source-code dependencies point only inward, toward higher-level policy.
- [Domain Core](https://banes-lab.com/records/lexicon/domain-core.md): The requirement that pure domain logic occupy the core, isolated from external concerns.
- [Layer Separation](https://banes-lab.com/records/lexicon/layer-separation.md): The requirement that responsibilities be divided into distinct, ordered layers.
- [Ports](https://banes-lab.com/records/lexicon/ports.md): The requirement that the core define abstract interface points through which all external interaction passes.
- [Replicated In-Memory State](https://banes-lab.com/records/lexicon/replicated-in-memory-state.md): The requirement that application state be kept in replicated in-memory grids rather than a central store.
- [Unified Deployment Boundary](https://banes-lab.com/records/lexicon/unified-deployment-boundary.md): The requirement that the whole application build and deploy as one unit.
- [Uniform Stage Interface](https://banes-lab.com/records/lexicon/uniform-stage-interface.md): The requirement that every stage share one interface so stages can be composed freely.
- [Use Cases](https://banes-lab.com/records/lexicon/use-cases.md): The requirement that application operations be captured as explicit use cases in their own layer.
- [Anemic Layers](https://banes-lab.com/records/lexicon/anemic-layers.md): The degree to which strict layering produces thin pass-through layers that add indirection without logic.
- [End-to-End Traceability](https://banes-lab.com/records/lexicon/end-to-end-traceability.md): The degree to which decomposing flow into independent filters makes tracing a request end to end harder.
- [Feature Cohesion](https://banes-lab.com/records/lexicon/feature-cohesion.md): The degree to which all code serving one feature is grouped together rather than scattered by layer.
- [Independent Scaling](https://banes-lab.com/records/lexicon/independent-scaling.md): The degree to which a single deployable unit prevents scaling parts of the system independently.
- [Initial Complexity](https://banes-lab.com/records/lexicon/initial-complexity.md): The degree of upfront structural complexity introduced by defining ports and adapters.
- [Integration Overhead](https://banes-lab.com/records/lexicon/integration-overhead.md): The degree of effort required to wire independently-developed components together.
- [Operational Simplicity](https://banes-lab.com/records/lexicon/operational-simplicity.md): The degree to which a single deployable unit keeps building, deploying, and operating simple.
- [Shared Technical Concerns](https://banes-lab.com/records/lexicon/shared-technical-concerns.md): The degree to which grouping by feature complicates sharing cross-cutting technical code.
- [Coordination Surface](https://banes-lab.com/records/lexicon/coordination-surface.md): A formal definition of a file that parties read and write to coordinate work, carrying a declared key and scope in its header and records each owned by one writer.
- [Coordination Record](https://banes-lab.com/records/lexicon/coordination-record.md): A formal definition of one addressable claim inside a coordination surface, carrying its schema fields, its edges, an allocated id, a declared subject and the one writer it names.
- [Outcome Surface](https://banes-lab.com/records/lexicon/outcome-surface.md): A formal definition of a surface that carries one product authored jointly, such as a contract or a class statement, with no per-party unit an ownership fence could range over.
- [Participant](https://banes-lab.com/records/lexicon/participant.md): A formal definition of a reader that owns surfaces and an inbox, receives both, and waits between turns instead of ending.
- [Bounded Reader](https://banes-lab.com/records/lexicon/bounded-reader.md): A formal definition of a reader handed a task and whatever its host injects, never a coordination surface, which ends by returning its result.
- [Host Projection](https://banes-lab.com/records/lexicon/host-projection.md): Descriptive data about the coordination graph that a host injects into every bounded reader's context, the only channel through which such a reader learns anything about the surfaces.
- [Venue](https://banes-lab.com/records/lexicon/venue.md): A formal definition of a surface opened for one discussion, which declares its own exit condition and moves to the archive once the outcome it produced has landed.
- [Accumulator](https://banes-lab.com/records/lexicon/accumulator.md): A formal definition of a surface that receives what a record extracts before the record is deleted, so a deletion loses nothing a later reader needs.
- [Retention](https://banes-lab.com/records/lexicon/retention.md): A formal definition of the lifetime axis that states what ends a piece of content, whether nothing, a newer version of itself, the completion of what it asked for, or its producer regenerating the whole surface.
- [Mutability](https://banes-lab.com/records/lexicon/mutability.md): A formal definition of the lifetime axis that states whether a landed statement may be rewritten, and by whom, its own writer or nobody.
- [Removal Authority](https://banes-lab.com/records/lexicon/removal-authority.md): A formal definition of the lifetime axis that states who may take content out, whether nobody at any point, its writer, the party that discharged it, or the mechanism that regenerates it.
- [Write Scope](https://banes-lab.com/records/lexicon/write-scope.md): A formal definition of the set of paths a run declares it may write, compared by declaration before the run begins to decide whether two runs collide.
- [Read Population](https://banes-lab.com/records/lexicon/read-population.md): A formal definition of the set a run read and publishes with its result, which a later caller tests to decide whether that result answers its own question.
- [Joiner](https://banes-lab.com/records/lexicon/joiner.md): A formal definition of a caller that reads a live run's published result and its standing instead of starting a run of its own, with an empty write set.
- [Liveness Witness](https://banes-lab.com/records/lexicon/liveness-witness.md): A facility that answers whether a process is still running by checking that the process is present, so its absence proves death while its presence proves nothing.
- [Distinguished Copy](https://banes-lab.com/records/lexicon/distinguished-copy.md): A formal definition of the one copy of a fact that every other copy derives from, or the one copy a mechanism resolves, which gives a set of copies its direction.
- [Derivation Period](https://banes-lab.com/records/lexicon/derivation-period.md): A formal definition of how often a derivation edge runs, on every read, between stores or once at creation, which decides whether a copy is stale or is a record.
- [Carrier Field](https://banes-lab.com/records/lexicon/carrier-field.md): A formal definition of a field whose consumers are mechanisms and whose value is drawn from a closed set or is an identifier.
- [Payload Field](https://banes-lab.com/records/lexicon/payload-field.md): A formal definition of a field whose only consumer is a reader and which no parser reaches without a heuristic.
- [Concern Partition](https://banes-lab.com/records/lexicon/concern-partition.md): A formal definition of how a body of work divides into concerns, derived from a coupling relation that joins two surfaces when a change to one forces a change to the other.
- [Fan-In](https://banes-lab.com/records/lexicon/fan-in.md): A measure of how many parties' claims rest on one surface, read from who authored each claim, whom it addressed and which surfaces it cites.
- [Acknowledger](https://banes-lab.com/records/lexicon/acknowledger.md): A formal definition of the party a record names to close it when its satisfaction is a judgement, required where no artifact resolves the record and forbidden where one does.
- [Stall Bound](https://banes-lab.com/records/lexicon/stall-bound.md): A rule or precondition that a record satisfied by judgement and left unacknowledged past a declared number of rounds is a finding, a bound on its lifetime rather than its size.
- [Deferred Setting](https://banes-lab.com/records/lexicon/deferred-setting.md): A formal definition of a host setting declared as given later, which blocks every check that depends on it until it is given, while an absent setting turns those checks off.
- [Traceable Guarantee](https://banes-lab.com/records/lexicon/traceable-guarantee.md): The ability to trace every guarantee a topology offers back to a stated property and the mechanism that would object if it stopped holding.
- [Rederivation Detection](https://banes-lab.com/records/lexicon/rederivation-detection.md): The ability to catch a record written a second time about a subject another record already holds.
- [Governed Removal](https://banes-lab.com/records/lexicon/governed-removal.md): The ability to remove content only where its declared lifetime names the party or mechanism allowed to remove it.
- [Shared Invocation](https://banes-lab.com/records/lexicon/shared-invocation.md): The ability for several callers to share one run of a measurement, each either joining a live run that covers its question or starting one that no live run covers.
- [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.
- [Idempotency Key or Deterministic Operation](https://banes-lab.com/records/lexicon/idempotency-key-or-deterministic-operation.md): The requirement that an operation carry a deduplication key or be deterministic so repeating it is safe.
- [Non-Repeatable Side Effects](https://banes-lab.com/records/lexicon/non-repeatable-side-effects.md): Side effects whose repetition changes the outcome, so retrying an operation double-applies them.
- [Safe Retries](https://banes-lab.com/records/lexicon/safe-retries.md): The ability to retry an operation without fear of duplicating its effects.
- [State Tracking](https://banes-lab.com/records/lexicon/state-tracking.md): The degree to which making operations idempotent requires tracking processed keys or prior state.
- [All-or-Nothing State Change](https://banes-lab.com/records/lexicon/all-or-nothing-state-change.md): The ability to apply a set of changes so that either all of them take effect or none do.
- [Distributed Scalability](https://banes-lab.com/records/lexicon/distributed-scalability.md): The degree to which enforcing atomic transactions across nodes limits how far a system can scale out.
- [Partial Commit](https://banes-lab.com/records/lexicon/partial-commit.md): Committing only some of a multi-step change after a failure, leaving state half-updated and inconsistent.
- [BASE/Eventual Consistency](https://banes-lab.com/records/lexicon/base-eventual-consistency.md): A consistency model favoring availability and soft state, letting replicas converge over time rather than staying strongly consistent.
- [Distributed Availability](https://banes-lab.com/records/lexicon/distributed-availability.md): The degree to which insisting on strong transactional consistency reduces availability across a distributed system.
- [Durability](https://banes-lab.com/records/lexicon/durability.md): The degree to which committed data survives crashes and is never lost once acknowledged.
- [Strong Transactional Guarantees](https://banes-lab.com/records/lexicon/strong-transactional-guarantees.md): The ability to guarantee that a group of operations is atomic, consistent, isolated, and durable.
- [Consistency Rules](https://banes-lab.com/records/lexicon/consistency-rules.md): The requirement that the invariants a transaction must preserve be defined for its scope.
- [Hidden Distributed Transaction](https://banes-lab.com/records/lexicon/hidden-distributed-transaction.md): A transaction that silently spans service boundaries, coupling systems that should commit independently.
- [Large Transaction Scope](https://banes-lab.com/records/lexicon/large-transaction-scope.md): The degree to which widening a transaction to cover more work increases contention and failure surface.
- [Safe State Mutation](https://banes-lab.com/records/lexicon/safe-state-mutation.md): The ability to mutate state within a bounded transaction so partial failures cannot corrupt it.
- [Coordinated Persistence](https://banes-lab.com/records/lexicon/coordinated-persistence.md): The ability to commit a set of related changes together as one atomic unit of work.
- [Repository Complexity](https://banes-lab.com/records/lexicon/repository-complexity.md): The degree to which coordinating saves through a unit of work adds indirection to the persistence layer.
- [Scattered Save Calls](https://banes-lab.com/records/lexicon/scattered-save-calls.md): Persisting related changes through many independent save calls, so a mid-sequence failure leaves partial state.
- [Inconsistent Replicas/Models](https://banes-lab.com/records/lexicon/inconsistent-replicas-models.md): Replicas or models that disagree on the same data, so reads return conflicting answers.
- [Reliable State](https://banes-lab.com/records/lexicon/reliable-state.md): The ability to trust that stored state always satisfies its invariants.
- [Dirty Reads/Writes](https://banes-lab.com/records/lexicon/dirty-reads-writes.md): Reading or overwriting another transaction's uncommitted changes, so a rollback leaves corrupt data.
- [Safe Concurrent Operations](https://banes-lab.com/records/lexicon/safe-concurrent-operations.md): The ability to run concurrent transactions without their intermediate states interfering.
- [Safe Parallel Mutation](https://banes-lab.com/records/lexicon/safe-parallel-mutation.md): The ability to let multiple actors mutate shared state in parallel without corrupting it.
- [Shared State Identification](https://banes-lab.com/records/lexicon/shared-state-identification.md): The requirement that all state shared between concurrent actors be identified before it is guarded.
- [Blind Overwrite](https://banes-lab.com/records/lexicon/blind-overwrite.md): Writing over another actor's update without checking whether the data changed first, silently losing it.
- [Conflict Detection](https://banes-lab.com/records/lexicon/conflict-detection.md): The ability to detect that data changed since it was read, so a conflicting write can be rejected.
- [Retry Complexity](https://banes-lab.com/records/lexicon/retry-complexity.md): The degree to which rejecting conflicting writes pushes retry-and-merge logic onto callers.
- [Version Field](https://banes-lab.com/records/lexicon/version-field.md): A field on a record whose value changes on each write, used to detect concurrent modification.
- [Lock Ownership](https://banes-lab.com/records/lexicon/lock-ownership.md): The requirement that a lock be exclusively held by one actor for the duration of a critical section.
- [Lock-Free Throughput](https://banes-lab.com/records/lexicon/lock-free-throughput.md): The degree to which a design sustains high throughput by coordinating concurrent access without holding locks.
- [Strong Conflict Prevention](https://banes-lab.com/records/lexicon/strong-conflict-prevention.md): The ability to prevent conflicting updates by locking data before it is modified.
- [Data Sharing](https://banes-lab.com/records/lexicon/data-sharing.md): The degree to which strictly isolating state limits components from directly sharing data.
- [Effect Boundaries](https://banes-lab.com/records/lexicon/effect-boundaries.md): The requirement that side effects be confined to explicit boundaries rather than scattered through pure logic.
- [Performance Optimization](https://banes-lab.com/records/lexicon/performance-optimization.md): The degree to which pushing side effects to the edges can forgo in-place optimizations that mutate for speed.
- [Pure Core / Imperative Shell](https://banes-lab.com/records/lexicon/pure-core-imperative-shell.md): An arrangement that keeps decision logic pure and pushes all side effects to a thin outer shell.
- [Ad-Hoc Lock Ordering](https://banes-lab.com/records/lexicon/ad-hoc-lock-ordering.md): Ordering lock acquisition by hand-reasoning rather than a proven scheme, inviting deadlock.
- [Concurrency Correctness](https://banes-lab.com/records/lexicon/concurrency-correctness.md): The degree to which concurrent flows produce correct results free of races and lost updates, for example because each unit's state is isolated.
- [Concurrent-Flow Modeling](https://banes-lab.com/records/lexicon/concurrent-flow-modeling.md): The ability to model concurrent token flow explicitly so its behavior can be analyzed.
- [Deadlock Freedom](https://banes-lab.com/records/lexicon/deadlock-freedom.md): The degree to which a concurrent design is provably free of states where progress halts permanently, which acquiring several locks pessimistically puts at risk.
- [Modeling Overhead](https://banes-lab.com/records/lexicon/modeling-overhead.md): The degree to which formally modeling concurrency as a net adds effort over writing the code directly.
- [Places and Transitions](https://banes-lab.com/records/lexicon/places-and-transitions.md): The requirement that a modeled system be expressed as places holding tokens and transitions that move them.
- [Reachability and Deadlock Analysis](https://banes-lab.com/records/lexicon/reachability-and-deadlock-analysis.md): The ability to analyze which states a concurrent model can reach and whether any of them deadlock.
- [Metrics](https://banes-lab.com/records/lexicon/metrics.md): Quantitative measurements a system emits about its state and behavior for monitoring and analysis.
- [Contracts](https://banes-lab.com/records/lexicon/contracts.md): Explicit, enforceable agreements specifying the inputs, outputs, and guarantees between components.
- [Independent Deployment](https://banes-lab.com/records/lexicon/independent-deployment.md): The ability to release a component to production without coordinating the deployment of others.
- [Delivery Speed](https://banes-lab.com/records/lexicon/delivery-speed.md): The rate at which changes are delivered to production.
- [Boilerplate](https://banes-lab.com/records/lexicon/boilerplate.md): Repetitive, mandatory scaffolding code that adds ceremony without domain value.
- [Schema](https://banes-lab.com/records/lexicon/schema.md): A formal definition of the structure, types, and constraints of data.
- [Compatibility](https://banes-lab.com/records/lexicon/compatibility.md): The degree to which a component interoperates with other versions or systems without modification.
- [Cost](https://banes-lab.com/records/lexicon/cost.md): The resource or financial expenditure required to build, run, or change a system.
- [Metadata](https://banes-lab.com/records/lexicon/metadata.md): Descriptive data about a system's structure, capabilities, or content, consumed to drive behavior.
- [Discovery](https://banes-lab.com/records/lexicon/discovery.md): The ability to locate available components, services, or capabilities at runtime.
- [Iteration Speed](https://banes-lab.com/records/lexicon/iteration-speed.md): The rate at which cycles of change and feedback can be completed.
- [Race Conditions](https://banes-lab.com/records/lexicon/race-conditions.md): A defect where the outcome depends on the uncontrolled interleaving of concurrent operations.
- [Ports and Adapters](https://banes-lab.com/records/lexicon/ports-and-adapters.md): An architecture isolating core logic behind ports, with adapters binding it to external technologies.
- [Operational Complexity](https://banes-lab.com/records/lexicon/operational-complexity.md): The effort and intricacy required to deploy, run, and maintain a system in production.
- [Standards](https://banes-lab.com/records/lexicon/standards.md): Agreed conventions and specifications that components conform to for interoperability and consistency.
- [Single Point of Failure](https://banes-lab.com/records/lexicon/single-point-of-failure.md): A component whose failure alone halts the entire system because it has no redundancy.
- [Debugging](https://banes-lab.com/records/lexicon/debugging.md): The activity of locating and diagnosing the cause of a defect.
- [Specification](https://banes-lab.com/records/lexicon/specification.md): A precise, authoritative description of required behavior, structure, or interface.
- [False Positives](https://banes-lab.com/records/lexicon/false-positives.md): Incorrect positive results reported when the detected condition is not present.
- [Ownership](https://banes-lab.com/records/lexicon/ownership.md): A clear assignment of responsibility for a component to a person or team.
- [Silent Failure](https://banes-lab.com/records/lexicon/silent-failure.md): A failure that occurs without surfacing any error, log, or signal, leaving it undetected.
- [Message Contract](https://banes-lab.com/records/lexicon/message-contract.md): The agreed schema and semantics of messages exchanged between components.
- [Replay](https://banes-lab.com/records/lexicon/replay.md): The ability to re-process a recorded sequence of events to reconstruct or recover state, including the state at a past point.
- [DSLs](https://banes-lab.com/records/lexicon/dsls.md): Domain-specific languages, small notations tailored to express solutions within one problem domain.
- [Acceptance Criteria](https://banes-lab.com/records/lexicon/acceptance-criteria.md): Predefined conditions a deliverable must satisfy to be accepted as complete and correct.
- [Ambiguous Naming](https://banes-lab.com/records/lexicon/ambiguous-naming.md): Identifiers whose meaning is unclear or open to multiple interpretations, obscuring intent.
- [Automated Enforcement](https://banes-lab.com/records/lexicon/automated-enforcement.md): Machine-applied checking that rules and policies hold, catching violations without manual review.
- [Automation](https://banes-lab.com/records/lexicon/automation.md): The execution of tasks by software or machinery without manual intervention.
- [Boolean Flag Soup](https://banes-lab.com/records/lexicon/boolean-flag-soup.md): Representing state through many interdependent boolean flags, producing tangled and invalid combinations.
- [Capacity Planning](https://banes-lab.com/records/lexicon/capacity-planning.md): Forecasting resource demand and provisioning capacity to meet it without waste or shortfall.
- [Code Generation](https://banes-lab.com/records/lexicon/code-generation.md): Producing source code automatically from a higher-level model, schema, or specification.
- [Composition Root](https://banes-lab.com/records/lexicon/composition-root.md): The single startup location where an application's object graph is assembled and its dependencies wired.
- [Context](https://banes-lab.com/records/lexicon/context.md): The surrounding information and circumstances captured to make a decision, event, or log entry interpretable.
- [Continuous Processing](https://banes-lab.com/records/lexicon/continuous-processing.md): Handling data incrementally as it arrives, rather than in discrete scheduled batches.
- [Controlled Access](https://banes-lab.com/records/lexicon/controlled-access.md): Mediated, restricted access to a resource so that only permitted operations reach it.
- [Controlled Evolution](https://banes-lab.com/records/lexicon/controlled-evolution.md): The managed, deliberate change of a system over time without breaking existing consumers.
- [Cross-Cutting Concerns](https://banes-lab.com/records/lexicon/cross-cutting-concerns.md): Concerns such as logging, security, or transactions whose implementation spans many modules rather than localizing to one.
- [Damage Limitation](https://banes-lab.com/records/lexicon/damage-limitation.md): Containing the blast radius of a failure or breach so its impact stays bounded.
- [Evaluation](https://banes-lab.com/records/lexicon/evaluation.md): The systematic assessment of a model or system's behavior and quality against defined criteria.
- [Evidence](https://banes-lab.com/records/lexicon/evidence.md): Recorded proof that substantiates a claim, decision, or compliance requirement.
- [Explicit Inputs](https://banes-lab.com/records/lexicon/explicit-inputs.md): All data a computation needs supplied through its parameters rather than read from ambient or hidden state.
- [Fallback](https://banes-lab.com/records/lexicon/fallback.md): An alternative path or default invoked automatically when the primary operation fails or is unavailable.
- [Hidden Dependencies](https://banes-lab.com/records/lexicon/hidden-dependencies.md): Dependencies a component relies on but does not declare in its interface, surfacing only at runtime.
- [Independent Work Units](https://banes-lab.com/records/lexicon/independent-work-units.md): Work partitioned into discrete units that execute in isolation, without shared mutable state or ordering dependencies.
- [Large Input Handling](https://banes-lab.com/records/lexicon/large-input-handling.md): The ability to process inputs too large to fit in memory, through streaming or chunking.
- [Legal-Transition Enforcement](https://banes-lab.com/records/lexicon/legal-transition-enforcement.md): Rejecting any state change that is not a permitted transition.
- [Plugins](https://banes-lab.com/records/lexicon/plugins.md): Independently-developed components that attach to a host at defined extension points to add capabilities.
- [Policy](https://banes-lab.com/records/lexicon/policy.md): A declared set of rules governing what actions are permitted or denied within a system.
- [Pub/Sub](https://banes-lab.com/records/lexicon/pub-sub.md): A messaging pattern in which publishers emit messages to topics and subscribers receive them without direct coupling.
- [Recovery](https://banes-lab.com/records/lexicon/recovery.md): Restoring a system to correct operation or a consistent state after a failure.
- [Reuse](https://banes-lab.com/records/lexicon/reuse.md): Using an existing component, module, or solution in a new context rather than rebuilding it.
- [Runtime Indirection](https://banes-lab.com/records/lexicon/runtime-indirection.md): Resolving a binding or call target at runtime through an intermediary layer rather than a direct, static reference.
- [Safe Defaults](https://banes-lab.com/records/lexicon/safe-defaults.md): Choosing default configurations and behaviors that are safe when left unchanged.
- [Safe Refactoring](https://banes-lab.com/records/lexicon/safe-refactoring.md): Changing a system's internal structure with confidence that its observable behavior is preserved.
- [Safe Substitution](https://banes-lab.com/records/lexicon/safe-substitution.md): Replacing a component or expression with an equivalent one without altering program correctness.
- [Saga](https://banes-lab.com/records/lexicon/saga.md): A pattern that manages a distributed transaction as a sequence of local transactions, each with a compensating action for rollback.
- [Model Drift](https://banes-lab.com/records/lexicon/model-drift.md): The gradual loss of a model's fidelity to the reality it represents, as data or conditions change over time.
- [Stable Contracts](https://banes-lab.com/records/lexicon/stable-contracts.md): Interfaces and agreements that remain unchanged over time so that consumers can depend on them safely.
- [Thresholds](https://banes-lab.com/records/lexicon/thresholds.md): Configured boundary values that trigger an alert or action when a measured metric crosses them.
- [Time Budget](https://banes-lab.com/records/lexicon/time-budget.md): A bounded maximum amount of time allotted for an operation to complete.
- [Time Cost](https://banes-lab.com/records/lexicon/time-cost.md): The amount of time an activity requires, weighed as a cost against its benefit.
- [Type Metadata](https://banes-lab.com/records/lexicon/type-metadata.md): Descriptive data about the types of a structure's fields, available for inspection at runtime.
- [Undo/Redo](https://banes-lab.com/records/lexicon/undo-redo.md): The ability to reverse a previously applied operation and to reapply it.