# The lex records whose category is core-vocabulary

This index as JSON: https://banes-lab.com/json/api/facets/lex/category/core-vocabulary

## Entries

- [Metrics](https://banes-lab.com/records/lex/metrics.md): Quantitative measurements a system emits about its state and behavior for monitoring and analysis.
- [Contracts](https://banes-lab.com/records/lex/contracts.md): Explicit, enforceable agreements specifying the inputs, outputs, and guarantees between components.
- [Independent Deployment](https://banes-lab.com/records/lex/independent-deployment.md): The ability to release a component to production without coordinating the deployment of others.
- [Delivery Speed](https://banes-lab.com/records/lex/delivery-speed.md): The rate at which changes are delivered to production.
- [Boilerplate](https://banes-lab.com/records/lex/boilerplate.md): Repetitive, mandatory scaffolding code that adds ceremony without domain value.
- [Schema](https://banes-lab.com/records/lex/schema.md): A formal definition of the structure, types, and constraints of data.
- [Compatibility](https://banes-lab.com/records/lex/compatibility.md): The degree to which a component interoperates with other versions or systems without modification.
- [Cost](https://banes-lab.com/records/lex/cost.md): The resource or financial expenditure required to build, run, or change a system.
- [Self-Healing](https://banes-lab.com/records/lex/self-healing.md): The ability of a system to detect and recover from failures without human intervention.
- [Metadata](https://banes-lab.com/records/lex/metadata.md): Descriptive data about a system's structure, capabilities, or content, consumed to drive behavior.
- [Discovery](https://banes-lab.com/records/lex/discovery.md): The ability to locate available components, services, or capabilities at runtime.
- [Iteration Speed](https://banes-lab.com/records/lex/iteration-speed.md): The rate at which cycles of change and feedback can be completed.
- [Race Conditions](https://banes-lab.com/records/lex/race-conditions.md): A defect where the outcome depends on the uncontrolled interleaving of concurrent operations.
- [Ports and Adapters](https://banes-lab.com/records/lex/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/lex/operational-complexity.md): The effort and intricacy required to deploy, run, and maintain a system in production.
- [Standards](https://banes-lab.com/records/lex/standards.md): Agreed conventions and specifications that components conform to for interoperability and consistency.
- [Single Point of Failure](https://banes-lab.com/records/lex/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/lex/debugging.md): The activity of locating and diagnosing the cause of a defect.
- [Specification](https://banes-lab.com/records/lex/specification.md): A precise, authoritative description of required behavior, structure, or interface.
- [False Positives](https://banes-lab.com/records/lex/false-positives.md): Incorrect positive results reported when the detected condition is not present.
- [Ownership](https://banes-lab.com/records/lex/ownership.md): A clear assignment of responsibility for a component to a person or team.
- [Silent Failure](https://banes-lab.com/records/lex/silent-failure.md): A failure that occurs without surfacing any error, log, or signal, leaving it undetected.
- [Message Contract](https://banes-lab.com/records/lex/message-contract.md): The agreed schema and semantics of messages exchanged between components.
- [Replay](https://banes-lab.com/records/lex/replay.md): The ability to re-process a recorded sequence of events to reconstruct or recover state.
- [DSLs](https://banes-lab.com/records/lex/dsls.md): Domain-specific languages, small notations tailored to express solutions within one problem domain.
- [Acceptance Criteria](https://banes-lab.com/records/lex/acceptance-criteria.md): Predefined conditions a deliverable must satisfy to be accepted as complete and correct.
- [Ambiguous Naming](https://banes-lab.com/records/lex/ambiguous-naming.md): Identifiers whose meaning is unclear or open to multiple interpretations, obscuring intent.
- [Automated Enforcement](https://banes-lab.com/records/lex/automated-enforcement.md): Machine-applied checking that rules and policies hold, catching violations without manual review.
- [Automation](https://banes-lab.com/records/lex/automation.md): The execution of tasks by software or machinery without manual intervention.
- [Boolean Flag Soup](https://banes-lab.com/records/lex/boolean-flag-soup.md): Representing state through many interdependent boolean flags, producing tangled and invalid combinations.
- [Capacity Planning](https://banes-lab.com/records/lex/capacity-planning.md): Forecasting resource demand and provisioning capacity to meet it without waste or shortfall.
- [Code Generation](https://banes-lab.com/records/lex/code-generation.md): Producing source code automatically from a higher-level model, schema, or specification.
- [Composition Root](https://banes-lab.com/records/lex/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/lex/context.md): The surrounding information and circumstances captured to make a decision, event, or log entry interpretable.
- [Continuous Processing](https://banes-lab.com/records/lex/continuous-processing.md): Handling data incrementally as it arrives, rather than in discrete scheduled batches.
- [Controlled Access](https://banes-lab.com/records/lex/controlled-access.md): Mediated, restricted access to a resource so that only permitted operations reach it.
- [Controlled Evolution](https://banes-lab.com/records/lex/controlled-evolution.md): The managed, deliberate change of a system over time without breaking existing consumers.
- [Controlled Inputs](https://banes-lab.com/records/lex/controlled-inputs.md): Inputs that are fixed, bounded, or fully specified so that a computation's behavior is reproducible.
- [Cross-Cutting Concerns](https://banes-lab.com/records/lex/cross-cutting-concerns.md): Concerns such as logging, security, or transactions whose implementation spans many modules rather than localizing to one.
- [Cyclic Dependencies](https://banes-lab.com/records/lex/cyclic-dependencies.md): Dependencies that form a cycle among components, preventing independent build, test, or reasoning.
- [Damage Limitation](https://banes-lab.com/records/lex/damage-limitation.md): Containing the blast radius of a failure or breach so its impact stays bounded.
- [Evaluation](https://banes-lab.com/records/lex/evaluation.md): The systematic assessment of a model or system's behavior and quality against defined criteria.
- [Evidence](https://banes-lab.com/records/lex/evidence.md): Recorded proof that substantiates a claim, decision, or compliance requirement.
- [Explicit Inputs](https://banes-lab.com/records/lex/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/lex/fallback.md): An alternative path or default invoked automatically when the primary operation fails or is unavailable.
- [Hidden Dependencies](https://banes-lab.com/records/lex/hidden-dependencies.md): Dependencies a component relies on but does not declare in its interface, surfacing only at runtime.
- [Hidden Side Effects](https://banes-lab.com/records/lex/hidden-side-effects.md): State changes a function performs that are not evident from its name or signature, surprising callers.
- [Independent Work Units](https://banes-lab.com/records/lex/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/lex/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/lex/legal-transition-enforcement.md): Rejecting any state change that is not a permitted transition.
- [Plugin Swap](https://banes-lab.com/records/lex/plugin-swap.md): Replacing one plugin implementation with another at a defined seam without modifying the host.
- [Plugins](https://banes-lab.com/records/lex/plugins.md): Independently-developed components that attach to a host at defined extension points to add capabilities.
- [Policy](https://banes-lab.com/records/lex/policy.md): A declared set of rules governing what actions are permitted or denied within a system.
- [Pub/Sub](https://banes-lab.com/records/lex/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/lex/recovery.md): Restoring a system to correct operation or a consistent state after a failure.
- [Reuse](https://banes-lab.com/records/lex/reuse.md): Using an existing component, module, or solution in a new context rather than rebuilding it.
- [Runtime Indirection](https://banes-lab.com/records/lex/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/lex/safe-defaults.md): Choosing default configurations and behaviors that are safe when left unchanged.
- [Safe Refactoring](https://banes-lab.com/records/lex/safe-refactoring.md): Changing a system's internal structure with confidence that its observable behavior is preserved.
- [Safe Substitution](https://banes-lab.com/records/lex/safe-substitution.md): Replacing a component or expression with an equivalent one without altering program correctness.
- [Saga](https://banes-lab.com/records/lex/saga.md): A pattern that manages a distributed transaction as a sequence of local transactions, each with a compensating action for rollback.
- [Secure Defaults](https://banes-lab.com/records/lex/secure-defaults.md): Making the default configuration the most secure option, requiring explicit action to reduce security.
- [Model Drift](https://banes-lab.com/records/lex/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/lex/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/lex/thresholds.md): Configured boundary values that trigger an alert or action when a measured metric crosses them.
- [Time Budget](https://banes-lab.com/records/lex/time-budget.md): A bounded maximum amount of time allotted for an operation to complete.
- [Time Cost](https://banes-lab.com/records/lex/time-cost.md): The amount of time an activity requires, weighed as a cost against its benefit.
- [Type Metadata](https://banes-lab.com/records/lex/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/lex/undo-redo.md): The ability to reverse a previously applied operation and to reapply it.