# The lex records whose kind is constraint

This index as JSON: https://banes-lab.com/json/api/facets/lex/kind/constraint

## Entries

- [Architecture Criteria](https://banes-lab.com/records/lex/architecture-criteria.md): The requirement that explicit criteria define what a review judges an architecture against.
- [Architecture Rules](https://banes-lab.com/records/lex/architecture-rules.md): The requirement that explicit, checkable rules govern how the architecture may be structured and evolved.
- [Criteria](https://banes-lab.com/records/lex/criteria.md): The requirement that explicit, agreed measures define how an assessment reaches its verdict.
- [Design Criteria](https://banes-lab.com/records/lex/design-criteria.md): The requirement that explicit criteria define what a design review evaluates a proposal against.
- [Essential Quality Attributes](https://banes-lab.com/records/lex/essential-quality-attributes.md): The requirement that the few quality attributes critical to viability be satisfied before any others.
- [Legacy Constraints](https://banes-lab.com/records/lex/legacy-constraints.md): A binding limitation imposed by pre-existing legacy systems that a new design must accommodate.
- [Measurable Architecture Rule](https://banes-lab.com/records/lex/measurable-architecture-rule.md): The requirement that an architectural rule be expressed as an objective, automatically checkable measure.
- [Quality Goals](https://banes-lab.com/records/lex/quality-goals.md): The requirement that target levels for key quality attributes be defined for an architecture to meet.
- [Review Standards](https://banes-lab.com/records/lex/review-standards.md): The requirement that agreed standards define what a code review checks for.
- [Incremental Change](https://banes-lab.com/records/lex/incremental-change.md): The requirement that a system evolve in small, reversible increments rather than large risky leaps.
- [Explicit State Model](https://banes-lab.com/records/lex/explicit-state-model.md): The requirement that an object's states and their transitions be modeled explicitly.
- [Explicit State Set](https://banes-lab.com/records/lex/explicit-state-set.md): The requirement that the complete set of possible states be defined up front.
- [Interchangeable Algorithms](https://banes-lab.com/records/lex/interchangeable-algorithms.md): The requirement that competing algorithms share one interface so they can be swapped freely.
- [Shared Behavioral Interface](https://banes-lab.com/records/lex/shared-behavioral-interface.md): The requirement that the real object and its null stand-in implement one common interface.
- [Stable Algorithm Skeleton](https://banes-lab.com/records/lex/stable-algorithm-skeleton.md): The requirement that the overall algorithm's structure stay fixed while specific steps vary.
- [Stable Element Hierarchy](https://banes-lab.com/records/lex/stable-element-hierarchy.md): The requirement that the set of element types stay fixed so new operations can be added over them.
- [Subject/Subscriber Contract](https://banes-lab.com/records/lex/subject-subscriber-contract.md): The requirement of an agreed interface by which subjects notify and subscribers receive updates.
- [Uniform Handler Interface](https://banes-lab.com/records/lex/uniform-handler-interface.md): The requirement that every handler in a chain share one interface so requests pass along uniformly.
- [Uniform Traversal Interface](https://banes-lab.com/records/lex/uniform-traversal-interface.md): The requirement that collections expose one common interface for stepping through their elements.
- [Causal Ordering](https://banes-lab.com/records/lex/causal-ordering.md): The requirement that operations be applied in an order consistent with their cause-and-effect relationships.
- [Ordering Semantics](https://banes-lab.com/records/lex/ordering-semantics.md): The requirement that a defined semantics specify when one event is considered to happen before another.
- [Ordering Key or Sequence](https://banes-lab.com/records/lex/ordering-key-or-sequence.md): The requirement that each event carry a key or sequence number that fixes its position in order.
- [Dependency Declaration](https://banes-lab.com/records/lex/dependency-declaration.md): The requirement that each operation declare the operations it causally depends on.
- [Dependency Extraction](https://banes-lab.com/records/lex/dependency-extraction.md): The requirement that dependencies between units be discovered and represented explicitly as a graph.
- [Directed Dependencies](https://banes-lab.com/records/lex/directed-dependencies.md): The requirement that dependencies point in one direction only, forming no cycles.
- [Node Identity](https://banes-lab.com/records/lex/node-identity.md): The requirement that each participating node have a distinct identity to index its own counter.
- [Commutative Merge](https://banes-lab.com/records/lex/commutative-merge.md): The requirement that concurrent updates merge in any order to the same result.
- [Network Partition Possibility](https://banes-lab.com/records/lex/network-partition-possibility.md): The requirement that a distributed design account for the possibility of network partitions.
- [Boundaries](https://banes-lab.com/records/lex/boundaries.md): The requirement that clear boundaries separate the concentric layers of the system.
- [Component Boundaries](https://banes-lab.com/records/lex/component-boundaries.md): The requirement that each component expose a well-defined boundary and interface.
- [Dependency Rule](https://banes-lab.com/records/lex/dependency-rule.md): The requirement that source-code dependencies point only inward, toward higher-level policy.
- [Domain Core](https://banes-lab.com/records/lex/domain-core.md): The requirement that pure domain logic occupy the core, isolated from external concerns.
- [Layer Separation](https://banes-lab.com/records/lex/layer-separation.md): The requirement that responsibilities be divided into distinct, ordered layers.
- [Ports](https://banes-lab.com/records/lex/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/lex/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/lex/unified-deployment-boundary.md): The requirement that the whole application build and deploy as one unit.
- [Uniform Stage Interface](https://banes-lab.com/records/lex/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/lex/use-cases.md): The requirement that application operations be captured as explicit use cases in their own layer.
- [Compatibility Policy](https://banes-lab.com/records/lex/compatibility-policy.md): The declared rules governing which changes are compatible and how versions are managed.
- [Consistent Semantics](https://banes-lab.com/records/lex/consistent-semantics.md): The requirement that the same operation mean the same thing across every resource and endpoint.
- [Extensible Schema](https://banes-lab.com/records/lex/extensible-schema.md): A schema shaped so new fields can be added without breaking existing consumers.
- [Protocol Contract](https://banes-lab.com/records/lex/protocol-contract.md): The agreed rules of a protocol, such as its messages, formats and sequences, that both ends must honor.
- [Semantic Contract](https://banes-lab.com/records/lex/semantic-contract.md): An agreement specifying not just the shape of an interface but the meaning and behavior it guarantees.
- [Unknown Field Handling](https://banes-lab.com/records/lex/unknown-field-handling.md): The requirement that a consumer ignore fields it does not recognize rather than fail on them.
- [Quorum](https://banes-lab.com/records/lex/quorum.md): The requirement that a majority of nodes agree before a decision commits.
- [Canonical Source](https://banes-lab.com/records/lex/canonical-source.md): The requirement that each piece of knowledge have one authoritative definition rather than copies.
- [Contract Compatibility](https://banes-lab.com/records/lex/contract-compatibility.md): The requirement that alternative implementations honor the same interface contract.
- [Explicit Interfaces](https://banes-lab.com/records/lex/explicit-interfaces.md): The requirement that a module interact only through declared interfaces, not its hidden internals.
- [Interface Conformance](https://banes-lab.com/records/lex/interface-conformance.md): The requirement that each implementation fully conform to the shared interface's contract.
- [Interface Definition](https://banes-lab.com/records/lex/interface-definition.md): The requirement that an abstraction expose a defined interface separate from its implementation.
- [Stable Semantics](https://banes-lab.com/records/lex/stable-semantics.md): The requirement that an abstraction's meaning stay consistent even as its implementations change.
- [Contracts](https://banes-lab.com/records/lex/contracts.md): Explicit, enforceable agreements specifying the inputs, outputs, and guarantees between components.
- [Standards](https://banes-lab.com/records/lex/standards.md): Agreed conventions and specifications that components conform to for interoperability and consistency.
- [Ownership](https://banes-lab.com/records/lex/ownership.md): A clear assignment of responsibility for a component to a person or team.
- [Message Contract](https://banes-lab.com/records/lex/message-contract.md): The agreed schema and semantics of messages exchanged between components.
- [Acceptance Criteria](https://banes-lab.com/records/lex/acceptance-criteria.md): Predefined conditions a deliverable must satisfy to be accepted as complete and correct.
- [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.
- [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.
- [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.
- [Policy](https://banes-lab.com/records/lex/policy.md): A declared set of rules governing what actions are permitted or denied within a system.
- [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.
- [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.
- [Cloneable Template Object](https://banes-lab.com/records/lex/cloneable-template-object.md): The requirement that a prototype object support being copied to produce new instances.
- [Creation Variation](https://banes-lab.com/records/lex/creation-variation.md): A precondition that different variants of a product must be produced depending on runtime context.
- [Related Product Variants](https://banes-lab.com/records/lex/related-product-variants.md): The requirement that products form families of related variants meant to be used together.
- [Single-Instance Need](https://banes-lab.com/records/lex/single-instance-need.md): A precondition that exactly one instance of a type must exist across the system.
- [Subclass-Controlled Creation](https://banes-lab.com/records/lex/subclass-controlled-creation.md): The requirement that subclasses determine which concrete product a creator instantiates.
- [Explicit Boundary](https://banes-lab.com/records/lex/explicit-boundary.md): The requirement that a clear boundary separate the domain from external systems it integrates with.
- [Relationship Semantics](https://banes-lab.com/records/lex/relationship-semantics.md): The requirement that each relationship between bounded contexts carry a defined meaning.
- [Stable Identity](https://banes-lab.com/records/lex/stable-identity.md): The requirement that an entity keep one stable identifier throughout its lifetime.
- [Value Equality](https://banes-lab.com/records/lex/value-equality.md): The requirement that two value objects be treated as equal when all their attributes match.
- [Alternate Behavior](https://banes-lab.com/records/lex/alternate-behavior.md): The requirement that a defined alternate behavior exist to use when the primary path fails.
- [Capacity Signaling](https://banes-lab.com/records/lex/capacity-signaling.md): The requirement that downstream capacity be signaled upstream so producers adjust their rate.
- [Failure Isolation](https://banes-lab.com/records/lex/failure-isolation.md): The requirement that a failure be contained within a boundary so it cannot spread.
- [Failure Threshold](https://banes-lab.com/records/lex/failure-threshold.md): The requirement of a defined failure count or rate at which a circuit breaker trips.
- [Feature Isolation](https://banes-lab.com/records/lex/feature-isolation.md): The requirement that individual features be isolated so one can be disabled without taking down others.
- [Resource Isolation](https://banes-lab.com/records/lex/resource-isolation.md): The requirement that resources be partitioned so exhaustion in one pool cannot starve others.
- [Strict Output](https://banes-lab.com/records/lex/strict-output.md): The requirement that a component emit only strictly conformant, well-formed output.
- [Timeout](https://banes-lab.com/records/lex/timeout.md): The requirement that an operation be given a maximum time to complete before being abandoned.
- [Tolerant Input](https://banes-lab.com/records/lex/tolerant-input.md): The requirement that a component accept and cope with input that deviates from the ideal format.
- [Event Contract](https://banes-lab.com/records/lex/event-contract.md): The agreed schema and semantics of an event that publishers and subscribers both honor.
- [Event Semantics](https://banes-lab.com/records/lex/event-semantics.md): The agreed meaning of what an event represents and the conditions under which it is emitted.
- [Immutable Events](https://banes-lab.com/records/lex/immutable-events.md): The requirement that recorded events never change once written, only be appended to.
- [Own Data](https://banes-lab.com/records/lex/own-data.md): The requirement that each service alone own and control its data store.
- [Reversible/Compensable Step](https://banes-lab.com/records/lex/reversible-compensable-step.md): The requirement that each step in a distributed workflow can be undone by a compensating action.
- [User Expectations](https://banes-lab.com/records/lex/user-expectations.md): The behavior users assume a system will exhibit, such as seeing their own writes immediately.
- [Explicit Semantics](https://banes-lab.com/records/lex/explicit-semantics.md): The requirement that declarative configuration carry an explicit, defined meaning.
- [Stable Conventions](https://banes-lab.com/records/lex/stable-conventions.md): The requirement that the conventions a system relies on stay stable and well-known.
- [Code-as-Data Representation](https://banes-lab.com/records/lex/code-as-data-representation.md): The requirement that a program's code be representable in the same data structures the language manipulates.
- [AST or Data Representation](https://banes-lab.com/records/lex/ast-or-data-representation.md): The requirement that code be represented as a structured syntax tree or data rather than as raw text.
- [Reflection/AST/Code Generation](https://banes-lab.com/records/lex/reflection-ast-code-generation.md): The requirement that a language expose reflection, syntax trees, or code generation for programs to manipulate themselves.
- [Compile-Time Inputs](https://banes-lab.com/records/lex/compile-time-inputs.md): The requirement that the inputs a computation needs be known at compile time so it can run then.
- [Safe Generation Boundary](https://banes-lab.com/records/lex/safe-generation-boundary.md): The requirement that runtime code generation be confined to a safe, sandboxed boundary away from untrusted input.
- [Formal Grammar/Semantics](https://banes-lab.com/records/lex/formal-grammar-semantics.md): The requirement that a domain language have a defined grammar and semantics rather than an ad-hoc syntax.
- [Code Generation or Interpreters](https://banes-lab.com/records/lex/code-generation-or-interpreters.md): The requirement that a domain language be backed by a generator or interpreter that executes it.
- [Transformation Rules](https://banes-lab.com/records/lex/transformation-rules.md): The requirement that explicit rules define how a model maps to generated implementation code.
- [Approval Policy](https://banes-lab.com/records/lex/approval-policy.md): The declared rules and gates a model must pass before it may be deployed.
- [Data/Model Boundaries](https://banes-lab.com/records/lex/data-model-boundaries.md): The lines separating data preparation, model training, and serving so each concern stays isolated.
- [Input/Output Contract](https://banes-lab.com/records/lex/input-output-contract.md): The agreed schema of the inputs a model accepts and the outputs it returns.
- [Tool Interface](https://banes-lab.com/records/lex/tool-interface.md): The defined contract through which an agent invokes external tools and receives their results.
- [Training/Inference Separation](https://banes-lab.com/records/lex/training-inference-separation.md): The requirement that model training and prediction serving be distinct, separately-managed phases.
- [Context Propagation](https://banes-lab.com/records/lex/context-propagation.md): The requirement that request context be carried across service boundaries so related calls can be correlated.
- [Trace Context Propagation](https://banes-lab.com/records/lex/trace-context-propagation.md): The requirement that trace identifiers be propagated across every hop of a distributed request.
- [Objective Reliability Targets](https://banes-lab.com/records/lex/objective-reliability-targets.md): The requirement that reliability be expressed as objective, measurable targets rather than vague aspirations.
- [Externalized Flag State](https://banes-lab.com/records/lex/externalized-flag-state.md): The requirement that feature-flag values live in external configuration, not hardcoded in the code.
- [Keyed Registration](https://banes-lab.com/records/lex/keyed-registration.md): The requirement that each component register under a unique key by which it can be retrieved.
- [Registration Protocol](https://banes-lab.com/records/lex/registration-protocol.md): The requirement of a defined protocol by which services register and deregister themselves.
- [Platform Abstraction](https://banes-lab.com/records/lex/platform-abstraction.md): The requirement that platform-specific details sit behind an abstraction the rest of the system depends on.
- [Externalized Config](https://banes-lab.com/records/lex/externalized-config.md): The requirement that configuration live outside the container image so one image runs in any environment.
- [Applicable Standard](https://banes-lab.com/records/lex/applicable-standard.md): The requirement that the relevant external standard a system must meet be identified and adhered to.
- [Secure Config Handling](https://banes-lab.com/records/lex/secure-config-handling.md): The requirement that secrets and sensitive configuration be stored and injected securely, never hardcoded.
- [Conventions](https://banes-lab.com/records/lex/conventions.md): The requirement that components follow shared naming or placement conventions so they can be found automatically.
- [Runtime Discovery or Configuration](https://banes-lab.com/records/lex/runtime-discovery-or-configuration.md): The requirement that implementations be discoverable or configurable at runtime rather than fixed.
- [Runtime Resolution](https://banes-lab.com/records/lex/runtime-resolution.md): The requirement that a symbol's concrete binding be resolved during execution rather than at compile time.
- [Cacheable Content](https://banes-lab.com/records/lex/cacheable-content.md): The requirement that content be stable enough to serve from a cache without harmful staleness.
- [Externalized State](https://banes-lab.com/records/lex/externalized-state.md): The requirement that session or request state be held outside the serving instance, in a shared store.
- [Invalidation Policy](https://banes-lab.com/records/lex/invalidation-policy.md): The rules determining when cached entries are considered stale and must be refreshed or evicted.
- [Multiple Targets](https://banes-lab.com/records/lex/multiple-targets.md): The precondition that more than one interchangeable backend exists across which traffic can be spread.
- [Quota Policy](https://banes-lab.com/records/lex/quota-policy.md): The declared limits on how many requests a caller may make within a time window.
- [Repeatable Test Environment](https://banes-lab.com/records/lex/repeatable-test-environment.md): A controlled, reproducible environment in which measurements can be compared meaningfully across runs.
- [Representative Workload](https://banes-lab.com/records/lex/representative-workload.md): A workload that reflects production usage closely enough that measurements generalize.
- [Model Assumptions](https://banes-lab.com/records/lex/model-assumptions.md): The simplifying premises a performance model depends on, which limit how well it matches reality.
- [Explicit Types](https://banes-lab.com/records/lex/explicit-types.md): The requirement that values crossing a boundary carry explicit, declared types rather than open-ended ones.
- [Canonical Format](https://banes-lab.com/records/lex/canonical-format.md): The requirement that a single normalized form be defined for values before they are compared or stored.
- [Canonical Definition](https://banes-lab.com/records/lex/canonical-definition.md): The requirement that each fact have one authoritative definition that all consumers reference.
- [Data Semantics](https://banes-lab.com/records/lex/data-semantics.md): The requirement that the meaning and dependencies of data be understood before it is decomposed into relations.
- [Domain Collaboration](https://banes-lab.com/records/lex/domain-collaboration.md): The requirement that domain experts and developers collaborate to agree on shared terminology.
- [Clear Semantics](https://banes-lab.com/records/lex/clear-semantics.md): The requirement that an interface's names convey what each operation does and expects.
- [Naming Consistency](https://banes-lab.com/records/lex/naming-consistency.md): The requirement that names for the same concept be used consistently across an interface.
- [Convention](https://banes-lab.com/records/lex/convention.md): The requirement that a design follow established conventions so its behavior matches expectations.
- [Functional Dependencies](https://banes-lab.com/records/lex/functional-dependencies.md): The requirement that the dependencies determining which attributes fix others be identified before decomposing a schema.
- [Authorization Policy](https://banes-lab.com/records/lex/authorization-policy.md): The declared set of rules determining which principals may perform which actions on which resources.
- [Consent/Policy](https://banes-lab.com/records/lex/consent-policy.md): The recorded permission and governing rules under which personal data may lawfully be collected and processed.
- [Defined Policy](https://banes-lab.com/records/lex/defined-policy.md): An explicit, declared set of rules specifying what is permitted or denied, against which enforcement acts.
- [Layered Controls](https://banes-lab.com/records/lex/layered-controls.md): The requirement that multiple independent safeguards protect a resource, so no single failure exposes it.
- [Minimal Exposure](https://banes-lab.com/records/lex/minimal-exposure.md): The condition of exposing only the endpoints, ports, and capabilities strictly required.
- [Minimal Permissions](https://banes-lab.com/records/lex/minimal-permissions.md): The requirement that each principal hold only the permissions its function needs.
- [Rotation Policy](https://banes-lab.com/records/lex/rotation-policy.md): The specified interval and procedure by which secrets or keys must be replaced to limit the value of any single compromise.
- [Strong Identity](https://banes-lab.com/records/lex/strong-identity.md): The requirement that every actor prove a strong, verified identity before any access is granted.
- [Validation Rules](https://banes-lab.com/records/lex/validation-rules.md): Declared constraints that input must satisfy, such as type, range, format and length, before it is accepted.
- [Observable Health Criteria](https://banes-lab.com/records/lex/observable-health-criteria.md): The requirement that explicit, observable criteria define when a component counts as healthy.
- [Replication or Alternate Capacity](https://banes-lab.com/records/lex/replication-or-alternate-capacity.md): The requirement that duplicate copies or spare capacity exist to take over when a component fails.
- [Consistency Policy](https://banes-lab.com/records/lex/consistency-policy.md): The requirement that a defined policy specify how and when replicas converge to a consistent state.
- [Reversible Deployment](https://banes-lab.com/records/lex/reversible-deployment.md): The requirement that a deployment be structured so it can be safely reverted to a prior version.
- [Parallel Environments](https://banes-lab.com/records/lex/parallel-environments.md): The requirement that two full production-equivalent environments run side by side for cutover.
- [Lifecycle Signals](https://banes-lab.com/records/lex/lifecycle-signals.md): The requirement that a process receive lifecycle signals telling it when to start draining and stop.
- [Multiple Physical Disks](https://banes-lab.com/records/lex/multiple-physical-disks.md): The requirement that data span several physical disks so redundancy can survive a single-disk loss.
- [Contract Preservation](https://banes-lab.com/records/lex/contract-preservation.md): The requirement that a subtype honor every behavioral guarantee of the type it replaces.
- [Role-Specific Interfaces](https://banes-lab.com/records/lex/role-specific-interfaces.md): The requirement that interfaces be defined per client role rather than as one general-purpose surface.
- [Forward-Only State Model](https://banes-lab.com/records/lex/forward-only-state-model.md): The requirement that processing keep only forward-moving state, never needing to revisit earlier input.
- [Stage Contracts](https://banes-lab.com/records/lex/stage-contracts.md): The requirement that each pipeline stage declare a typed contract for what it consumes and produces.
- [Deferred Execution Semantics](https://banes-lab.com/records/lex/deferred-execution-semantics.md): The requirement that a computation's semantics defer its work until the result is demanded.
- [Ordered Read Model](https://banes-lab.com/records/lex/ordered-read-model.md): The requirement that data be read in a fixed forward order rather than by arbitrary index.
- [Random Access Requirement](https://banes-lab.com/records/lex/random-access-requirement.md): A need to read arbitrary items by position or key on demand rather than strictly in sequence.
- [No Backtracking Requirement](https://banes-lab.com/records/lex/no-backtracking-requirement.md): The requirement that processing never need to revisit earlier input to make a decision.
- [Data Dependencies](https://banes-lab.com/records/lex/data-dependencies.md): The requirement that the data each stage needs from others be declared as explicit dependencies.
- [Stages](https://banes-lab.com/records/lex/stages.md): The requirement that processing be decomposed into discrete stages connected by data flow.
- [No Hidden State](https://banes-lab.com/records/lex/no-hidden-state.md): The requirement that a processor keep no state hidden between invocations, taking all inputs explicitly.
- [Latency Requirement Clarity](https://banes-lab.com/records/lex/latency-requirement-clarity.md): The requirement that a workload's latency and freshness needs be made explicit before a processing model is chosen.
- [Common Interface](https://banes-lab.com/records/lex/common-interface.md): The requirement that a wrapper and the object it wraps share one interface so they remain interchangeable.
- [Incompatible Interfaces](https://banes-lab.com/records/lex/incompatible-interfaces.md): A precondition of two interfaces that must cooperate yet expose mismatched signatures.
- [Independent Variation Axes](https://banes-lab.com/records/lex/independent-variation-axes.md): The requirement that an abstraction and its implementation vary along separate axes so they can be decoupled.
- [Separable Intrinsic State](https://banes-lab.com/records/lex/separable-intrinsic-state.md): The requirement that an object's shared, context-independent state be separable from its per-use state.
- [Uniform Component Interface](https://banes-lab.com/records/lex/uniform-component-interface.md): The requirement that leaves and composites implement one shared interface so clients treat them alike.
- [Governed Root](https://banes-lab.com/records/lex/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.
- [Depth Cap](https://banes-lab.com/records/lex/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/lex/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.
- [Idempotency Key or Deterministic Operation](https://banes-lab.com/records/lex/idempotency-key-or-deterministic-operation.md): The requirement that an operation carry a deduplication key or be deterministic so repeating it is safe.
- [Consistency Rules](https://banes-lab.com/records/lex/consistency-rules.md): The requirement that the invariants a transaction must preserve be defined for its scope.
- [Shared State Identification](https://banes-lab.com/records/lex/shared-state-identification.md): The requirement that all state shared between concurrent actors be identified before it is guarded.
- [Lock Ownership](https://banes-lab.com/records/lex/lock-ownership.md): The requirement that a lock be exclusively held by one actor for the duration of a critical section.
- [Effect Boundaries](https://banes-lab.com/records/lex/effect-boundaries.md): The requirement that side effects be confined to explicit boundaries rather than scattered through pure logic.
- [Places and Transitions](https://banes-lab.com/records/lex/places-and-transitions.md): The requirement that a modeled system be expressed as places holding tokens and transitions that move them.