# The lex records whose category is correctness-determinism-verification

This index as JSON: https://banes-lab.com/json/api/facets/lex/category/correctness-determinism-verification

## Entries

- [Assumption-Driven Delivery](https://banes-lab.com/records/lex/assumption-driven-delivery.md): Shipping on untested assumptions about behavior instead of validating that requirements are met.
- [Environment-Sensitive Behavior](https://banes-lab.com/records/lex/environment-sensitive-behavior.md): Behavior that changes with the host environment, so the same run yields different results elsewhere.
- [Example-Only Testing](https://banes-lab.com/records/lex/example-only-testing.md): Testing only a few hand-picked examples instead of properties that must hold across all inputs.
- [Floating Dependencies](https://banes-lab.com/records/lex/floating-dependencies.md): Depending on unpinned, floating dependency versions, so builds are not reproducible.
- [Hidden Behavior](https://banes-lab.com/records/lex/hidden-behavior.md): Behavior triggered by hidden state or side effects, so outcomes surprise callers.
- [Hidden IO](https://banes-lab.com/records/lex/hidden-io.md): Performing input/output inside a supposedly pure function, hiding side effects from callers.
- [Hidden Time/Randomness/Global State](https://banes-lab.com/records/lex/hidden-time-randomness-global-state.md): Reading the clock, randomness, or global state inside a computation, making its output nondeterministic.
- [Implementation-Only Testing](https://banes-lab.com/records/lex/implementation-only-testing.md): Testing only against the current implementation's behavior rather than the specified contract.
- [Informal Validation Only](https://banes-lab.com/records/lex/informal-validation-only.md): Relying only on informal checks and testing where a formal proof of correctness is warranted.
- [Side Effects](https://banes-lab.com/records/lex/side-effects.md): Producing observable side effects in an expression, so it cannot be replaced by its value.
- [Unchecked Dynamic Code](https://banes-lab.com/records/lex/unchecked-dynamic-code.md): Running dynamically generated or evaluated code that static analysis cannot inspect for defects.
- [Undefined Behavior](https://banes-lab.com/records/lex/undefined-behavior.md): Relying on operations whose result is unspecified, so outcomes vary unpredictably across runs or platforms.
- [Untested Implementation](https://banes-lab.com/records/lex/untested-implementation.md): Shipping code with no tests, so its conformance to the specification is unverified.
- [Behavior Validation](https://banes-lab.com/records/lex/behavior-validation.md): The ability to confirm a system behaves as its specification requires.
- [Broad Input Exploration](https://banes-lab.com/records/lex/broad-input-exploration.md): The ability to exercise a function across a wide, generated range of inputs.
- [Mathematical Assurance](https://banes-lab.com/records/lex/mathematical-assurance.md): The ability to prove mathematically that a system meets its specification.
- [Regression Safety](https://banes-lab.com/records/lex/regression-safety.md): The ability to catch regressions when code changes by re-running tests.
- [Reliable Automation](https://banes-lab.com/records/lex/reliable-automation.md): The ability to automate a process reliably because it repeats identically each run.
- [Reliable Testing](https://banes-lab.com/records/lex/reliable-testing.md): The ability to test dependably because the same inputs always produce the same outputs.
- [Safe Operation](https://banes-lab.com/records/lex/safe-operation.md): The ability to operate without producing incorrect or harmful results.
- [Safe Sharing](https://banes-lab.com/records/lex/safe-sharing.md): The ability to share data freely across threads because it cannot be modified.
- [Specification Compliance](https://banes-lab.com/records/lex/specification-compliance.md): The ability to confirm an implementation conforms to its specification.
- [Formal Specification](https://banes-lab.com/records/lex/formal-specification.md): A precise, mathematical statement of what a system must do, against which it is proven.
- [Ruleset](https://banes-lab.com/records/lex/ruleset.md): The set of rules a static analyzer checks source code against.
- [Tests](https://banes-lab.com/records/lex/tests.md): Executable checks that assert a system behaves as intended.
- [Controlled State](https://banes-lab.com/records/lex/controlled-state.md): The requirement that all inputs and state affecting a computation be controlled and known.
- [Deterministic Behavior](https://banes-lab.com/records/lex/deterministic-behavior.md): The requirement that the code under test produce the same result for the same inputs.
- [No Side Effects](https://banes-lab.com/records/lex/no-side-effects.md): The requirement that a function compute its result without observable side effects.
- [Properties/Invariants](https://banes-lab.com/records/lex/properties-invariants.md): The requirement that the general properties or invariants a function must satisfy be defined.
- [Value Semantics](https://banes-lab.com/records/lex/value-semantics.md): The requirement that values be compared and copied by content rather than by reference identity.
- [Versioned Inputs](https://banes-lab.com/records/lex/versioned-inputs.md): The requirement that all inputs to a build or computation be pinned to specific versions.
- [Allocation Cost](https://banes-lab.com/records/lex/allocation-cost.md): The degree of extra memory allocation incurred by creating new immutable values instead of mutating in place.
- [Continuous Updates](https://banes-lab.com/records/lex/continuous-updates.md): The degree to which pinning everything for reproducibility conflicts with continuously updating dependencies.
- [Cost/Complexity](https://banes-lab.com/records/lex/cost-complexity.md): The degree of cost and complexity added by formally proving a system correct.
- [Dynamic Runtime Behavior](https://banes-lab.com/records/lex/dynamic-runtime-behavior.md): The degree to which runtime-adaptive behavior undermines a system's predictability.
- [Encapsulation Extremes](https://banes-lab.com/records/lex/encapsulation-extremes.md): The degree to which hiding internals too strictly makes a unit's behavior hard to observe in tests.
- [Fitness for Use](https://banes-lab.com/records/lex/fitness-for-use.md): The degree to which a product meets the needs of its users.
- [Real-World Variability](https://banes-lab.com/records/lex/real-world-variability.md): The degree to which controlling conditions for repeatability diverges from real-world variability.
- [Runtime Adaptivity](https://banes-lab.com/records/lex/runtime-adaptivity.md): The degree to which making behavior deterministic limits adapting dynamically at runtime.
- [Shrinking/Debug Complexity](https://banes-lab.com/records/lex/shrinking-debug-complexity.md): The degree to which reducing a failing generated case to a minimal example adds debugging complexity.
- [Spec Maintenance](https://banes-lab.com/records/lex/spec-maintenance.md): The degree of ongoing effort to keep a specification current as the system evolves.
- [Stateful IO](https://banes-lab.com/records/lex/stateful-io.md): The degree to which stateful input/output conflicts with expressions being replaceable by their values.
- [Stateful Operations](https://banes-lab.com/records/lex/stateful-operations.md): The degree to which operations that depend on or mutate state conflict with purity.
- [Thread Safety](https://banes-lab.com/records/lex/thread-safety.md): The degree to which data can be accessed concurrently without corruption.