# Lexicon terms, part 5 of 5

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

## Entries

- [Split One Test per Subject](https://banes-lab.com/records/lexicon/split-one-test-per-subject.md): A technique for dividing a test that covers several subjects into one test file per subject.
- [Take the Domain Noun as the Subject](https://banes-lab.com/records/lexicon/take-the-domain-noun-as-the-subject.md): A technique for replacing the generic subject with the domain noun the file's source names.
- [Classify Before the First Write](https://banes-lab.com/records/lexicon/classify-before-the-first-write.md): A technique for deciding a file's concern and subject before writing it, so it is created under its final name.
- [Move the Order into the Registry](https://banes-lab.com/records/lexicon/move-the-order-into-the-registry.md): A technique for recording a sequence in a registry instead of in numeric filename prefixes.
- [Drop the Prefix](https://banes-lab.com/records/lexicon/drop-the-prefix.md): A technique for removing a numeric order prefix from filenames once a registry holds the order.
- [Resolve the Slot Against Its Source](https://banes-lab.com/records/lexicon/resolve-the-slot-against-its-source.md): A technique for checking a slot word against the source that allocates it instead of against a copied vocabulary.
- [Remove the Copies](https://banes-lab.com/records/lexicon/remove-the-copies.md): A technique for deleting vocabulary entries that copy words another source already owns.
- [Declare the Dialect](https://banes-lab.com/records/lexicon/declare-the-dialect.md): A technique for binding a file extension to the case splitter its language uses.
- [Rename to the Case's Word Run](https://banes-lab.com/records/lexicon/rename-to-the-case-s-word-run.md): A technique for renaming a dialect file so its case splitter yields the three declared slots.
- [Move the File into Its Concern Folder](https://banes-lab.com/records/lexicon/move-the-file-into-its-concern-folder.md): A technique for moving a loose root file into the concern folder its tag names.
- [Vocabulary-Bound Reading](https://banes-lab.com/records/lexicon/vocabulary-bound-reading.md): A defect in which a word is read by the vocabulary that declares it rather than by the slot it lands in.
- [Tag-Folder Mismatch](https://banes-lab.com/records/lexicon/tag-folder-mismatch.md): A defect in which a file's concern tag differs from the label of its parent folder.
- [Depth-Anchored Discovery](https://banes-lab.com/records/lexicon/depth-anchored-discovery.md): A defect in which discovery is anchored to a depth, so a grouped set falls out of the pattern.
- [Shape-Inferred Jurisdiction](https://banes-lab.com/records/lexicon/shape-inferred-jurisdiction.md): A defect in which jurisdiction is inferred from folder shape instead of declared.
- [Per-Check Exemption List](https://banes-lab.com/records/lexicon/per-check-exemption-list.md): A defect in which each check keeps its own exemption list for the same upstream tree.
- [Spine Read as a Dependency Rule](https://banes-lab.com/records/lexicon/spine-read-as-a-dependency-rule.md): A defect in which the layer spine is read as a dependency-direction rule rather than a classification tie-break.
- [Domain-Dialect Role](https://banes-lab.com/records/lexicon/domain-dialect-role.md): A defect in which an agnostic role is restated in a local domain dialect.
- [Prose-Only Vocabulary](https://banes-lab.com/records/lexicon/prose-only-vocabulary.md): A defect in which a vocabulary is kept in prose the gate cannot read.
- [Shared-Subject Test](https://banes-lab.com/records/lexicon/shared-subject-test.md): A defect in which one test file covers several subjects.
- [Generic Subject over a Domain File](https://banes-lab.com/records/lexicon/generic-subject-over-a-domain-file.md): A defect in which a file carries the generic subject while its source names the domain it serves.
- [Provisional Name](https://banes-lab.com/records/lexicon/provisional-name.md): A defect in which a file is written under a provisional name and its correct name is left for a later sweep.
- [Copied Slot Word](https://banes-lab.com/records/lexicon/copied-slot-word.md): A defect in which each word a source owns is copied into the declared vocabulary, one entry per allocated identity or upstream key.
- [Per-Language Vocabulary](https://banes-lab.com/records/lexicon/per-language-vocabulary.md): A defect in which a separate vocabulary is declared for each language instead of one set of slots read through each language's case.
- [Loose Root File](https://banes-lab.com/records/lexicon/loose-root-file.md): A defect in which a file sits at a governed root while it is neither the entry document nor an accumulator.
- [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.
- [Reconciliation Job](https://banes-lab.com/records/lexicon/reconciliation-job.md): A technique for periodically comparing two copies of related state and repairing the differences found.
- [Merge Policy](https://banes-lab.com/records/lexicon/merge-policy.md): A technique for declaring how two concurrent changes to one value are combined.
- [Transaction Isolation Level](https://banes-lab.com/records/lexicon/transaction-isolation-level.md): A technique for choosing how much concurrent transactions see of each other's uncommitted and recent writes.
- [Make Immutable](https://banes-lab.com/records/lexicon/make-immutable.md): A technique for replacing in-place mutation with new values, so state shared between readers cannot change under them.
- [Read From Primary After Write](https://banes-lab.com/records/lexicon/read-from-primary-after-write.md): A technique for routing a client's reads to the primary for a short time after it writes, so it sees its own write.
- [Consistency Contract](https://banes-lab.com/records/lexicon/consistency-contract.md): A technique for stating which reads may be stale, for how long, and how a client learns that its write is visible.
- [Fix the Race](https://banes-lab.com/records/lexicon/fix-the-race.md): A technique for removing a race by ordering, locking or making the shared state immutable, instead of retrying the test.
- [Apply Concurrency Control](https://banes-lab.com/records/lexicon/apply-concurrency-control.md): A technique for coordinating concurrent writers with locks, versions or ownership, so no write is lost.
- [Introduce Transaction Boundary](https://banes-lab.com/records/lexicon/introduce-transaction-boundary.md): A technique for declaring which writes commit or fail together.
- [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.
- [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.
- [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.
- [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.
- [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.
- [Name the Concept](https://banes-lab.com/records/lexicon/name-the-concept.md): A technique for giving a recurring group of values or steps a name in the domain language and one home in the code.
- [Name Constant](https://banes-lab.com/records/lexicon/name-constant.md): A technique for replacing an unexplained literal with a named constant that states its meaning.
- [Replace Boolean with Enum](https://banes-lab.com/records/lexicon/replace-boolean-with-enum.md): A technique for replacing a boolean parameter or flag with a closed set of named values.