# Lexicon terms, part 1 of 4

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

## Entries

- [Anemic Model](https://banes-lab.com/records/lexicon/anemic-model.md): A domain model holding only data with no behavior, pushing all logic into separate procedures.
- [Anemic Transaction Script](https://banes-lab.com/records/lexicon/anemic-transaction-script.md): Implementing business logic as procedural scripts over data-only objects, with no rich domain model.
- [Implicit Integration](https://banes-lab.com/records/lexicon/implicit-integration.md): Integrating contexts through undocumented, assumed connections instead of explicit, mapped relationships.
- [Shared Global Model](https://banes-lab.com/records/lexicon/shared-global-model.md): Forcing one global model across the whole system, so unrelated parts are coupled through it.
- [Business Rule Encapsulation](https://banes-lab.com/records/lexicon/business-rule-encapsulation.md): The ability to keep business rules inside the domain objects they govern.
- [Cross-Entity Domain Logic](https://banes-lab.com/records/lexicon/cross-entity-domain-logic.md): The ability to place logic that spans several entities in a dedicated domain service.
- [Domain Alignment](https://banes-lab.com/records/lexicon/domain-alignment.md): The ability to keep the software model closely aligned with the business domain it serves.
- [Identity-Based Equality](https://banes-lab.com/records/lexicon/identity-based-equality.md): The ability to treat two objects as the same when they share an identity, regardless of their attributes.
- [Legacy/System Integration](https://banes-lab.com/records/lexicon/legacy-system-integration.md): The ability to integrate a legacy or external system without letting its model corrupt the domain.
- [Lifecycle Tracking](https://banes-lab.com/records/lexicon/lifecycle-tracking.md): The ability to track an entity as the same thing through changes over its lifetime.
- [Root-Guarded Invariants](https://banes-lab.com/records/lexicon/root-guarded-invariants.md): The ability to enforce an aggregate's invariants by routing all changes through its root.
- [Self-Validating Values](https://banes-lab.com/records/lexicon/self-validating-values.md): The ability for a value object to guarantee its own validity at construction.
- [Side-Effect-Free Equality](https://banes-lab.com/records/lexicon/side-effect-free-equality.md): The ability to compare value objects by their contents with no side effects.
- [Transactional Consistency Boundary](https://banes-lab.com/records/lexicon/transactional-consistency-boundary.md): The ability to treat an aggregate as the unit within which invariants hold atomically.
- [Explicit Boundary](https://banes-lab.com/records/lexicon/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/lexicon/relationship-semantics.md): The requirement that each relationship between bounded contexts carry a defined meaning.
- [Stable Identity](https://banes-lab.com/records/lexicon/stable-identity.md): The requirement that an entity keep one stable identifier throughout its lifetime.
- [Value Equality](https://banes-lab.com/records/lexicon/value-equality.md): The requirement that two value objects be treated as equal when all their attributes match.
- [Translation Model](https://banes-lab.com/records/lexicon/translation-model.md): A mapping between an external system's concepts and the domain's own, keeping the two vocabularies separate.
- [Aggregate Size](https://banes-lab.com/records/lexicon/aggregate-size.md): The degree to which enlarging an aggregate to enforce invariants increases contention and load on it.
- [Cross-Context Reuse](https://banes-lab.com/records/lexicon/cross-context-reuse.md): The degree to which isolating each context's model limits reusing models across contexts.
- [Documentation Overhead](https://banes-lab.com/records/lexicon/documentation-overhead.md): The degree of ongoing effort to document and maintain the map of relationships between contexts.
- [Domain Purity](https://banes-lab.com/records/lexicon/domain-purity.md): The degree to which the domain model stays free of external and infrastructure concerns.
- [Integration Clarity](https://banes-lab.com/records/lexicon/integration-clarity.md): The degree to which relationships between contexts are made explicit and understandable.
- [Object Count](https://banes-lab.com/records/lexicon/object-count.md): The degree to which modeling many concepts as distinct value objects increases the number of objects.
- [Persistence Simplicity](https://banes-lab.com/records/lexicon/persistence-simplicity.md): The degree to which a rich domain model complicates straightforward mapping to storage.
- [Simple CRUD](https://banes-lab.com/records/lexicon/simple-crud.md): The degree to which a full domain model adds overhead where simple create-read-update-delete would suffice.
- [Closed Static Core](https://banes-lab.com/records/lexicon/closed-static-core.md): A core fixed at build time that cannot accept new capabilities without being recompiled.
- [Compile-Time Binding](https://banes-lab.com/records/lexicon/compile-time-binding.md): Fixing at build time which implementation a call uses or how components are wired together, so neither can vary or be discovered at runtime.
- [Hardcoded Endpoints](https://banes-lab.com/records/lexicon/hardcoded-endpoints.md): Hardcoding service network addresses instead of discovering them dynamically.
- [Manual Registration](https://banes-lab.com/records/lexicon/manual-registration.md): Requiring each component to be registered by hand instead of being discovered automatically.
- [Capability Addition without Core Modification](https://banes-lab.com/records/lexicon/capability-addition-without-core-modification.md): The ability to add new capabilities at runtime without modifying the core.
- [Deferred Implementation Choice](https://banes-lab.com/records/lexicon/deferred-implementation-choice.md): The ability to postpone choosing a concrete implementation until runtime, so each environment can assemble its own.
- [Dynamic Routing](https://banes-lab.com/records/lexicon/dynamic-routing.md): The ability to route requests to service instances discovered at runtime.
- [Self-Registration](https://banes-lab.com/records/lexicon/self-registration.md): The ability for a component to register itself on load without external wiring.
- [Replace Conditional with Polymorphism](https://banes-lab.com/records/lexicon/replace-conditional-with-polymorphism.md): Replacing a branching conditional on type with polymorphic dispatch through a shared interface.
- [Conventions](https://banes-lab.com/records/lexicon/conventions.md): The requirement that components follow shared naming or placement conventions so they can be found automatically.
- [Runtime Resolution](https://banes-lab.com/records/lexicon/runtime-resolution.md): The requirement that a symbol's concrete binding be resolved, by discovery or from configuration, during execution rather than at compile time.
- [Extensibility](https://banes-lab.com/records/lexicon/extensibility.md): The degree to which new behavior can be added with minimal change to existing code.
- [Startup Cost](https://banes-lab.com/records/lexicon/startup-cost.md): The degree to which scanning for components at startup slows the system's initialization.
- [Causation Tracking](https://banes-lab.com/records/lexicon/causation-tracking.md): Recording which event caused which, so cause-and-effect chains can be reconstructed later.
- [Correct Workflow Reasoning](https://banes-lab.com/records/lexicon/correct-workflow-reasoning.md): The ability to reason correctly about a workflow's steps by knowing their causal relationships.
- [Unordered Side Effects](https://banes-lab.com/records/lexicon/unordered-side-effects.md): Applying side effects in an order that ignores their causal dependencies, producing incorrect outcomes.
- [Arbitrary Reordering](https://banes-lab.com/records/lexicon/arbitrary-reordering.md): Reordering causally related operations freely, so effects can appear before their causes.
- [Causal Ordering](https://banes-lab.com/records/lexicon/causal-ordering.md): The requirement that operations be applied in an order consistent with their cause-and-effect relationships.
- [Eventual Consistency Safety](https://banes-lab.com/records/lexicon/eventual-consistency-safety.md): The degree to which replicas can converge over time without ever exposing a causally impossible state.
- [Latency/Availability](https://banes-lab.com/records/lexicon/latency-availability.md): The degree to which enforcing causal ordering across replicas costs added latency and reduced availability.
- [User-Visible Ordering Guarantees](https://banes-lab.com/records/lexicon/user-visible-ordering-guarantees.md): The ability to guarantee that users never observe an effect before its cause.
- [Causal Reasoning](https://banes-lab.com/records/lexicon/causal-reasoning.md): Reasoning about which events must precede others based on their causal relationships.
- [Ordering Semantics](https://banes-lab.com/records/lexicon/ordering-semantics.md): The requirement that a defined semantics specify when one event is considered to happen before another.
- [Parallel Execution](https://banes-lab.com/records/lexicon/parallel-execution.md): The degree to which enforcing a happens-before order constrains how much work can run in parallel.
- [Race Detection](https://banes-lab.com/records/lexicon/race-detection.md): The ability to detect data races by finding accesses with no happens-before ordering between them.
- [Correct Stateful Processing](https://banes-lab.com/records/lexicon/correct-stateful-processing.md): The ability to process a stream statefully with correct results by handling events in their proper order.
- [Ordering Key or Sequence](https://banes-lab.com/records/lexicon/ordering-key-or-sequence.md): The requirement that each event carry a key or sequence number that fixes its position in order.
- [Unordered Parallel Consumption](https://banes-lab.com/records/lexicon/unordered-parallel-consumption.md): Consuming an ordered event stream in parallel without preserving order, so state is updated out of sequence.
- [Dependency Declaration](https://banes-lab.com/records/lexicon/dependency-declaration.md): The requirement that each operation declare the operations it causally depends on.
- [Graph Complexity](https://banes-lab.com/records/lexicon/graph-complexity.md): The degree to which tracking fine-grained causal dependencies grows the dependency graph large and hard to reason about.
- [Hidden Dependency](https://banes-lab.com/records/lexicon/hidden-dependency.md): An unstated dependency between operations, so order-sensitive code breaks when the hidden ordering is not preserved.
- [Cycle Detection](https://banes-lab.com/records/lexicon/cycle-detection.md): The ability to detect cycles in a dependency graph before they cause deadlock or infinite resolution.
- [Dependency Extraction](https://banes-lab.com/records/lexicon/dependency-extraction.md): The requirement that dependencies between units be discovered and represented explicitly as a graph.
- [Dynamic Loading](https://banes-lab.com/records/lexicon/dynamic-loading.md): The degree to which resolving dependencies dynamically at runtime undermines a statically analyzable dependency graph.
- [Bidirectional Collaboration](https://banes-lab.com/records/lexicon/bidirectional-collaboration.md): The degree to which forbidding cycles prevents two components from depending on each other bidirectionally.
- [Build Order](https://banes-lab.com/records/lexicon/build-order.md): The ability to derive a correct build or execution order from a graph that contains no cycles.
- [Layering](https://banes-lab.com/records/lexicon/layering.md): A convention of organizing components into ordered layers where each may depend only on the layers beneath it.
- [Topological Ordering](https://banes-lab.com/records/lexicon/topological-ordering.md): The ability to linearize a directed acyclic graph into an order where every node follows its dependencies.
- [Concurrent Update Detection](https://banes-lab.com/records/lexicon/concurrent-update-detection.md): The ability to detect when two updates happened concurrently rather than one causally after the other.
- [Metadata Size](https://banes-lab.com/records/lexicon/metadata-size.md): The degree to which carrying a per-node counter for every node grows the ordering metadata with cluster size.
- [Node Identity](https://banes-lab.com/records/lexicon/node-identity.md): The requirement that each participating node have a distinct identity to index its own counter.
- [Single Global Clock Assumption](https://banes-lab.com/records/lexicon/single-global-clock-assumption.md): Assuming a single global clock orders all events, which fails across distributed nodes with independent clocks.
- [Version Vector](https://banes-lab.com/records/lexicon/version-vector.md): A set of per-node counters that together capture the causal history of a replicated item.
- [Happens-Before Reasoning](https://banes-lab.com/records/lexicon/happens-before-reasoning.md): Reasoning about event order using logical timestamps that respect the happens-before relation.
- [Logical Counter](https://banes-lab.com/records/lexicon/logical-counter.md): A monotonically increasing counter each process maintains to stamp events for logical ordering.
- [No Concurrent Causality Distinction](https://banes-lab.com/records/lexicon/no-concurrent-causality-distinction.md): The degree to which a single logical counter cannot tell concurrent events apart from causally ordered ones.
- [Partial Ordering](https://banes-lab.com/records/lexicon/partial-ordering.md): The ability to establish a consistent partial order over events without a shared physical clock.
- [Wall-Clock Ordering Assumption](https://banes-lab.com/records/lexicon/wall-clock-ordering-assumption.md): Ordering distributed events by wall-clock timestamps, which clock skew makes unreliable.
- [Clock Skew](https://banes-lab.com/records/lexicon/clock-skew.md): The degree to which physical clocks on different nodes drift apart, distorting time-based ordering.
- [Physical-Clock-Only Ordering](https://banes-lab.com/records/lexicon/physical-clock-only-ordering.md): Ordering events by physical clocks alone, which clock skew renders inconsistent across nodes.
- [Wall-Clock-Correlated Causal Order](https://banes-lab.com/records/lexicon/wall-clock-correlated-causal-order.md): The ability to order events causally while keeping timestamps close to wall-clock time.
- [Commutative Merge](https://banes-lab.com/records/lexicon/commutative-merge.md): The requirement that concurrent updates merge in any order to the same result.
- [Conflict-Free Replica Convergence](https://banes-lab.com/records/lexicon/conflict-free-replica-convergence.md): The ability for replicas to converge to one state automatically without conflict resolution.
- [Last-Write-Wins Overwrite](https://banes-lab.com/records/lexicon/last-write-wins-overwrite.md): Resolving concurrent updates by keeping the most recent write, rather than merging all updates.
- [Metadata Overhead](https://banes-lab.com/records/lexicon/metadata-overhead.md): The degree to which the bookkeeping a conflict-free type carries per value adds storage and transmission cost.
- [Identical Delivery Order Across Nodes](https://banes-lab.com/records/lexicon/identical-delivery-order-across-nodes.md): The ability to deliver messages to every node in the same total order.
- [Per-Node Independent Ordering](https://banes-lab.com/records/lexicon/per-node-independent-ordering.md): Letting each node decide message order independently, so replicas diverge on sequence.
- [Assumed Total Consistency And Availability](https://banes-lab.com/records/lexicon/assumed-total-consistency-and-availability.md): Assuming a distributed system can be fully consistent and available at once, ignoring partitions that force a choice.
- [Explicit Consistency/Availability Choice Under Partition](https://banes-lab.com/records/lexicon/explicit-consistency-availability-choice-under-partition.md): The ability to choose deliberately between consistency and availability when a network partition occurs.
- [Network Partition Possibility](https://banes-lab.com/records/lexicon/network-partition-possibility.md): The requirement that a distributed design account for the possibility of network partitions.
- [Consistency Assumed Free When Healthy](https://banes-lab.com/records/lexicon/consistency-assumed-free-when-healthy.md): Assuming consistency carries no cost while the network is healthy, ignoring the latency it still imposes.
- [Latency-Consistency Trade-off When Healthy](https://banes-lab.com/records/lexicon/latency-consistency-trade-off-when-healthy.md): The ability to weigh the latency-versus-consistency trade-off that remains even when the network is healthy.
- [Service Tag](https://banes-lab.com/records/lexicon/service-tag.md): A formal definition of the tag for a file that offers a stateful capability other code calls, filed in a services folder.
- [Controller Tag](https://banes-lab.com/records/lexicon/controller-tag.md): A formal definition of the tag for a file that receives an external request and routes it to the code that answers it, filed in a controllers folder.
- [Coordinator Tag](https://banes-lab.com/records/lexicon/coordinator-tag.md): A formal definition of the tag for a file that owns a lifecycle and drives the collaborators it depends on, filed in a coordinators folder.
- [Orchestrator Tag](https://banes-lab.com/records/lexicon/orchestrator-tag.md): A formal definition of the tag for a file that sequences several independent steps into one run and decides what happens when one fails, filed in an orchestrators folder.
- [Mediator Tag](https://banes-lab.com/records/lexicon/mediator-tag.md): A formal definition of the tag for a file through which peers communicate so that none of them refers to another directly, filed in a mediators folder.
- [Dispatcher Tag](https://banes-lab.com/records/lexicon/dispatcher-tag.md): A formal definition of the tag for a file that selects which handler receives each incoming message, filed in a dispatchers folder.
- [Workflow Tag](https://banes-lab.com/records/lexicon/workflow-tag.md): A formal definition of the tag for a file that defines a multi-step process with its transitions and outcomes, filed in a workflows folder.
- [Job Tag](https://banes-lab.com/records/lexicon/job-tag.md): A formal definition of the tag for a file that defines a unit of work run outside the request that asked for it, filed in a jobs folder.
- [Task Tag](https://banes-lab.com/records/lexicon/task-tag.md): A formal definition of the tag for a file that defines one named piece of work a runner can schedule and report on, filed in a tasks folder.
- [Stage Tag](https://banes-lab.com/records/lexicon/stage-tag.md): A formal definition of the tag for a file that defines one ordered phase of a larger run, filed in a stages folder.
- [Step Tag](https://banes-lab.com/records/lexicon/step-tag.md): A formal definition of the tag for a file that performs one advance of a process, filed in a steps folder.
- [State Tag](https://banes-lab.com/records/lexicon/state-tag.md): A formal definition of the tag for a file that holds the current condition of something the system tracks, filed in a state folder.
- [State-Machine Tag](https://banes-lab.com/records/lexicon/state-machine-tag.md): A formal definition of the tag for a file that defines a set of states and the allowed transitions between them, filed in a state-machines folder.
- [Transition Tag](https://banes-lab.com/records/lexicon/transition-tag.md): A formal definition of the tag for a file that defines one move from a state to the next with its guard, filed in a transitions folder.
- [Store Tag](https://banes-lab.com/records/lexicon/store-tag.md): A formal definition of the tag for a file that holds state and controls how it is read and changed, filed in a stores folder.
- [Reducer Tag](https://banes-lab.com/records/lexicon/reducer-tag.md): A formal definition of the tag for a file that computes the next state from the current state and an action, filed in a reducers folder.
- [Mutation Tag](https://banes-lab.com/records/lexicon/mutation-tag.md): A formal definition of the tag for a file that defines one permitted change to held state, filed in a mutations folder.
- [Selector Tag](https://banes-lab.com/records/lexicon/selector-tag.md): A formal definition of the tag for a file that derives a value from held state for its readers, filed in a selectors folder.
- [Observer Tag](https://banes-lab.com/records/lexicon/observer-tag.md): A formal definition of the tag for a file that watches a subject and reacts when it changes, filed in an observers folder.
- [Listener Tag](https://banes-lab.com/records/lexicon/listener-tag.md): A formal definition of the tag for a file that is registered for one kind of event and runs when it arrives, filed in a listeners folder.
- [Emitter Tag](https://banes-lab.com/records/lexicon/emitter-tag.md): A formal definition of the tag for a file that produces events or output for others to receive, filed in an emitters folder.
- [Signal Tag](https://banes-lab.com/records/lexicon/signal-tag.md): A formal definition of the tag for a file that defines a reactive value whose readers update when it changes, filed in a signals folder.
- [Publisher Tag](https://banes-lab.com/records/lexicon/publisher-tag.md): A formal definition of the tag for a file that sends messages to a topic without knowing who receives them, filed in a publishers folder.
- [Subscriber Tag](https://banes-lab.com/records/lexicon/subscriber-tag.md): A formal definition of the tag for a file that receives the messages of a topic it has joined, filed in a subscribers folder.
- [Subscription Tag](https://banes-lab.com/records/lexicon/subscription-tag.md): A formal definition of the tag for a file that defines the binding between a subscriber and what it receives, including how it ends, filed in a subscriptions folder.
- [Context Tag](https://banes-lab.com/records/lexicon/context-tag.md): A formal definition of the tag for a file that carries the ambient values a unit of work reads without passing them through every call, filed in a context folder.
- [Capability Tag](https://banes-lab.com/records/lexicon/capability-tag.md): A formal definition of the tag for a file that grants or describes one ability a component may use, filed in a capabilities folder.
- [Propagation Tag](https://banes-lab.com/records/lexicon/propagation-tag.md): A formal definition of the tag for a file that carries context across a boundary such as a thread or a network call, filed in a propagation folder.
- [Correlation Tag](https://banes-lab.com/records/lexicon/correlation-tag.md): A formal definition of the tag for a file that assigns and reads the identifiers tying related operations together, filed in a correlation folder.
- [Ambient-Context Tag](https://banes-lab.com/records/lexicon/ambient-context-tag.md): A formal definition of the tag for a file that holds values available implicitly for the length of one operation, filed in an ambient-context folder.
- [Viewmodel Tag](https://banes-lab.com/records/lexicon/viewmodel-tag.md): A formal definition of the tag for a file that shapes state for one view and exposes the actions that view offers, filed in a viewmodels folder.
- [Presenter Tag](https://banes-lab.com/records/lexicon/presenter-tag.md): A formal definition of the tag for a file that formats data for a passive view and handles that view's input, filed in a presenters folder.
- [Navigation Tag](https://banes-lab.com/records/lexicon/navigation-tag.md): A formal definition of the tag for a file that defines how a participant moves between views, filed in a navigation folder.
- [Input Tag](https://banes-lab.com/records/lexicon/input-tag.md): A formal definition of the tag for a file that reads device input and turns it into actions the system understands, filed in an input folder.
- [Gesture Tag](https://banes-lab.com/records/lexicon/gesture-tag.md): A formal definition of the tag for a file that recognizes a pattern of pointer or touch movement as one intent, filed in a gestures folder.
- [Behavior Tag](https://banes-lab.com/records/lexicon/behavior-tag.md): A formal definition of the tag for a file that decides what an agent does next from what it perceives, filed in a behaviors folder.
- [Heuristic Tag](https://banes-lab.com/records/lexicon/heuristic-tag.md): A formal definition of the tag for a file that scores options by an approximate rule where an exact answer costs too much, filed in a heuristics folder.
- [Intent Tag](https://banes-lab.com/records/lexicon/intent-tag.md): A formal definition of the tag for a file that represents what an agent means to do before any action carries it out, filed in an intents folder.
- [Actuator Tag](https://banes-lab.com/records/lexicon/actuator-tag.md): A formal definition of the tag for a file that turns an agent's decision into an effect on the world, filed in an actuators folder.
- [Classifier Tag](https://banes-lab.com/records/lexicon/classifier-tag.md): A formal definition of the tag for a file that assigns an input to one of a set of categories, filed in a classifiers folder.
- [Learner Tag](https://banes-lab.com/records/lexicon/learner-tag.md): A formal definition of the tag for a file that adjusts an agent's parameters from the outcomes it observes, filed in a learners folder.
- [Model Tag](https://banes-lab.com/records/lexicon/model-tag.md): A formal definition of the tag for a file that holds a conceptual representation of what the system is about, filed in a models folder.
- [Entity Tag](https://banes-lab.com/records/lexicon/entity-tag.md): A formal definition of the tag for a file that defines a domain object with an identity that persists while its attributes change, filed in an entities folder.
- [Value-Object Tag](https://banes-lab.com/records/lexicon/value-object-tag.md): A formal definition of the tag for a file that defines a domain value compared by its contents rather than by an identity, filed in a value-objects folder.
- [Aggregate Tag](https://banes-lab.com/records/lexicon/aggregate-tag.md): A formal definition of the tag for a file that defines a cluster of domain objects changed together through one root, filed in an aggregates folder.
- [Invariant Tag](https://banes-lab.com/records/lexicon/invariant-tag.md): A formal definition of the tag for a file that states a property the domain must keep true across every change, filed in an invariants folder.
- [Rule Tag](https://banes-lab.com/records/lexicon/rule-tag.md): A formal definition of the tag for a file that holds one business or governance rule as a unit, filed in a rules folder.
- [Constraint Tag](https://banes-lab.com/records/lexicon/constraint-tag.md): A formal definition of the tag for a file that declares a limit a domain value or operation must stay within, filed in a constraints folder.
- [Domain-Event Tag](https://banes-lab.com/records/lexicon/domain-event-tag.md): A formal definition of the tag for a file that defines something meaningful that happened in the domain, filed in a domain-events folder.
- [Specification Tag](https://banes-lab.com/records/lexicon/specification-tag.md): A formal definition of the tag for a file that declares a required end state or a selection rule as data other code evaluates, filed in a specifications folder.
- [Policy Tag](https://banes-lab.com/records/lexicon/policy-tag.md): A formal definition of the tag for a file that chooses among admissible behaviors by a stated rule, filed in a policies folder.
- [Use-Case Tag](https://banes-lab.com/records/lexicon/use-case-tag.md): A formal definition of the tag for a file that carries one interaction the system offers from its trigger to its outcome, filed in a use-cases folder.
- [Resource Tag](https://banes-lab.com/records/lexicon/resource-tag.md): A formal definition of the tag for a file that defines an addressable piece of data the system exposes or consumes, filed in a resources folder.
- [Record Tag](https://banes-lab.com/records/lexicon/record-tag.md): A formal definition of the tag for a file that defines one structured entry of data with named fields, filed in a records folder.
- [Payload Tag](https://banes-lab.com/records/lexicon/payload-tag.md): A formal definition of the tag for a file that defines the body a message or request carries, filed in a payloads folder.
- [Envelope Tag](https://banes-lab.com/records/lexicon/envelope-tag.md): A formal definition of the tag for a file that defines the wrapper carrying a payload's routing and metadata, filed in an envelopes folder.
- [Collection Tag](https://banes-lab.com/records/lexicon/collection-tag.md): A formal definition of the tag for a file that defines a grouped set of domain members and the operations over the set, filed in a collections folder.
- [Buffer Tag](https://banes-lab.com/records/lexicon/buffer-tag.md): A formal definition of the tag for a file that holds data temporarily between a producer and a consumer, filed in a buffers folder.
- [Snapshot Tag](https://banes-lab.com/records/lexicon/snapshot-tag.md): A formal definition of the tag for a file that captures the state of something at one moment so it can be read or restored later, filed in a snapshots folder.
- [Checkpoint Tag](https://banes-lab.com/records/lexicon/checkpoint-tag.md): A formal definition of the tag for a file that records a point a long process can resume from, filed in a checkpoints folder.
- [Event Tag](https://banes-lab.com/records/lexicon/event-tag.md): A formal definition of the tag for a file that defines a notification of something that happened, filed in an events folder.
- [Projection Tag](https://banes-lab.com/records/lexicon/projection-tag.md): A formal definition of the tag for a file that derives a read model from a stream of events, filed in a projections folder.
- [Level Tag](https://banes-lab.com/records/lexicon/level-tag.md): A formal definition of the tag for a file that defines one stage of a world a simulation or game advances through, filed in a levels folder.
- [Wave Tag](https://banes-lab.com/records/lexicon/wave-tag.md): A formal definition of the tag for a file that defines one timed group of arrivals within a level, filed in a waves folder.
- [Progression Tag](https://banes-lab.com/records/lexicon/progression-tag.md): A formal definition of the tag for a file that defines how a participant advances through unlocks and thresholds, filed in a progression folder.
- [Quest Tag](https://banes-lab.com/records/lexicon/quest-tag.md): A formal definition of the tag for a file that defines one objective with its conditions and its reward, filed in a quests folder.
- [Achievement Tag](https://banes-lab.com/records/lexicon/achievement-tag.md): A formal definition of the tag for a file that defines a recognized milestone and the condition that grants it, filed in an achievements folder.
- [Skill Tag](https://banes-lab.com/records/lexicon/skill-tag.md): A formal definition of the tag for a file that defines one ability a participant can train and use, filed in a skills folder.
- [Inventory Tag](https://banes-lab.com/records/lexicon/inventory-tag.md): A formal definition of the tag for a file that defines what a participant holds and the rules for adding and removing it, filed in an inventories folder.
- [Item Tag](https://banes-lab.com/records/lexicon/item-tag.md): A formal definition of the tag for a file that defines one kind of object a participant can own or use, filed in an items folder.
- [Pickup Tag](https://banes-lab.com/records/lexicon/pickup-tag.md): A formal definition of the tag for a file that defines an object placed in a world that grants something when collected, filed in a pickups folder.
- [Drop-Table Tag](https://banes-lab.com/records/lexicon/drop-table-tag.md): A formal definition of the tag for a file that defines the weighted outcomes a source can yield, filed in a drop-tables folder.
- [Shop Tag](https://banes-lab.com/records/lexicon/shop-tag.md): A formal definition of the tag for a file that defines an exchange of currency for items with its stock and prices, filed in a shops folder.
- [Currency Tag](https://banes-lab.com/records/lexicon/currency-tag.md): A formal definition of the tag for a file that defines a unit of value participants earn and spend, filed in a currencies folder.
- [Reward Tag](https://banes-lab.com/records/lexicon/reward-tag.md): A formal definition of the tag for a file that defines what a participant receives for completing something, filed in a rewards folder.
- [Action Tag](https://banes-lab.com/records/lexicon/action-tag.md): A formal definition of the tag for a file that defines one named operation a caller can request, with its inputs, filed in an actions folder.
- [Adapter Tag](https://banes-lab.com/records/lexicon/adapter-tag.md): A formal definition of the tag for a file that translates between the system's interface and an outside one, filed in an adapters folder.
- [Port Tag](https://banes-lab.com/records/lexicon/port-tag.md): A formal definition of the tag for a file that declares an interface the core needs from the outside, with no implementation, filed in a ports folder.
- [Boundary Tag](https://banes-lab.com/records/lexicon/boundary-tag.md): A formal definition of the tag for a file that marks where one module's responsibility ends and checks what crosses it, filed in a boundaries folder.
- [Interface Tag](https://banes-lab.com/records/lexicon/interface-tag.md): A formal definition of the tag for a file that declares the operations a type offers without implementing them, filed in an interfaces folder.
- [Abstraction Tag](https://banes-lab.com/records/lexicon/abstraction-tag.md): A formal definition of the tag for a file that defines a general base others specialize, filed in an abstractions folder.
- [Facade Tag](https://banes-lab.com/records/lexicon/facade-tag.md): A formal definition of the tag for a file that offers one simple entry to a group of more complex parts, filed in a facades folder.
- [Wrapper Tag](https://banes-lab.com/records/lexicon/wrapper-tag.md): A formal definition of the tag for a file that encloses another object to change how it is called while keeping what it does, filed in a wrappers folder.
- [Decorator Tag](https://banes-lab.com/records/lexicon/decorator-tag.md): A formal definition of the tag for a file that adds behavior to an object behind the object's own interface, filed in a decorators folder.
- [Delegate Tag](https://banes-lab.com/records/lexicon/delegate-tag.md): A formal definition of the tag for a file that receives work another object hands on instead of doing it itself, filed in a delegates folder.
- [Mixin Tag](https://banes-lab.com/records/lexicon/mixin-tag.md): A formal definition of the tag for a file that supplies reusable members many types can include, filed in a mixins folder.
- [Trait Tag](https://banes-lab.com/records/lexicon/trait-tag.md): A formal definition of the tag for a file that declares a named set of behaviors a type can implement, filed in a traits folder.
- [Composite Tag](https://banes-lab.com/records/lexicon/composite-tag.md): A formal definition of the tag for a file that treats a tree of parts and a single part through one interface, filed in a composites folder.
- [Primitive Tag](https://banes-lab.com/records/lexicon/primitive-tag.md): A formal definition of the tag for a file that defines a smallest building block higher parts are composed from, filed in a primitives folder.
- [Module Tag](https://banes-lab.com/records/lexicon/module-tag.md): A formal definition of the tag for a file that declares a self-contained unit with the surface it exports, filed in a modules folder.
- [Package Tag](https://banes-lab.com/records/lexicon/package-tag.md): A formal definition of the tag for a file that defines a distributable unit and what it contains, filed in a packages folder.
- [Namespace Tag](https://banes-lab.com/records/lexicon/namespace-tag.md): A formal definition of the tag for a file that groups names under one prefix so they cannot collide with others, filed in a namespaces folder.
- [Layer Tag](https://banes-lab.com/records/lexicon/layer-tag.md): A formal definition of the tag for a file that defines one tier of a layered structure and what it may depend on, filed in a layers folder.
- [Contract Tag](https://banes-lab.com/records/lexicon/contract-tag.md): A formal definition of the tag for a file that states what one side of a boundary guarantees to the other, filed in a contracts folder.
- [Schemas Tag](https://banes-lab.com/records/lexicon/schemas-tag.md): A formal definition of the collection tag for a file that defines the shapes data must take, plural in both folder and tag.
- [Types Tag](https://banes-lab.com/records/lexicon/types-tag.md): A formal definition of the collection tag for a file that declares the types other code uses, plural in both folder and tag.
- [Enums Tag](https://banes-lab.com/records/lexicon/enums-tag.md): A formal definition of the collection tag for a file that declares closed sets of named values, plural in both folder and tag.
- [Union Tag](https://banes-lab.com/records/lexicon/union-tag.md): A formal definition of the tag for a file that defines a value that is exactly one of several declared shapes, filed in a unions folder.
- [Alias Tag](https://banes-lab.com/records/lexicon/alias-tag.md): A formal definition of the tag for a file that gives a second name to an existing type or value, filed in an aliases folder.
- [Guard Tag](https://banes-lab.com/records/lexicon/guard-tag.md): A formal definition of the tag for a file that narrows a value's type after proving what it is, filed in a guards folder.
- [Predicate Tag](https://banes-lab.com/records/lexicon/predicate-tag.md): A formal definition of the tag for a file that answers yes or no about a value, filed in a predicates folder.
- [Identifier Tag](https://banes-lab.com/records/lexicon/identifier-tag.md): A formal definition of the tag for a file that creates or validates the identifiers records are addressed by, filed in an identifiers folder.
- [Metadata Tag](https://banes-lab.com/records/lexicon/metadata-tag.md): A formal definition of the tag for a file that holds data describing other data or code, filed in a metadata folder.
- [Annotation Tag](https://banes-lab.com/records/lexicon/annotation-tag.md): A formal definition of the tag for a file that defines markers attached to code for tools to read, filed in an annotations folder.
- [Constants Tag](https://banes-lab.com/records/lexicon/constants-tag.md): A formal definition of the collection tag for a file that declares named values fixed at build time, plural in both folder and tag, which also holds id tables.
- [Default Tag](https://banes-lab.com/records/lexicon/default-tag.md): A formal definition of the tag for a file that supplies the values used where a caller sets none, filed in a defaults folder.
- [Extension Tag](https://banes-lab.com/records/lexicon/extension-tag.md): A formal definition of the tag for a file that adds a capability to a host through the host's declared extension point, filed in an extensions folder.
- [Plugin Tag](https://banes-lab.com/records/lexicon/plugin-tag.md): A formal definition of the tag for a file that is discovered and loaded by a host to add behavior without editing the host, filed in a plugins folder.
- [Hook Tag](https://banes-lab.com/records/lexicon/hook-tag.md): A formal definition of the tag for a file that runs when a host reaches one named point in its flow, filed in a hooks folder.
- [Manifest Tag](https://banes-lab.com/records/lexicon/manifest-tag.md): A formal definition of the tag for a file that declares what a unit contains or provides for a loader to read, filed in a manifests folder.
- [Descriptor Tag](https://banes-lab.com/records/lexicon/descriptor-tag.md): A formal definition of the tag for a file that describes one registrable thing in the shape its registry expects, filed in a descriptors folder.
- [Registrar Tag](https://banes-lab.com/records/lexicon/registrar-tag.md): A formal definition of the tag for a file that enters members into a registry, filed in a registrars folder.
- [Registry Tag](https://banes-lab.com/records/lexicon/registry-tag.md): A formal definition of the tag for a file that holds a named set of known members and answers lookups against it, filed in a registries folder.
- [Provider Tag](https://banes-lab.com/records/lexicon/provider-tag.md): A formal definition of the tag for a file that supplies an instance or a value on request, filed in a providers folder.
- [Factory Tag](https://banes-lab.com/records/lexicon/factory-tag.md): A formal definition of the tag for a file that constructs instances so callers never call a constructor directly, filed in a factories folder.
- [Builder Tag](https://banes-lab.com/records/lexicon/builder-tag.md): A formal definition of the tag for a file that assembles a complex object or a build output step by step, filed in a builders folder.
- [Injector Tag](https://banes-lab.com/records/lexicon/injector-tag.md): A formal definition of the tag for a file that supplies a component's dependencies from outside it, filed in an injectors folder.
- [Binding Tag](https://banes-lab.com/records/lexicon/binding-tag.md): A formal definition of the tag for a file that ties an abstract name to the concrete value or implementation it resolves to, filed in a bindings folder.
- [Resolver Tag](https://banes-lab.com/records/lexicon/resolver-tag.md): A formal definition of the tag for a file that turns a reference into the thing it refers to, filed in a resolvers folder.
- [Locator Tag](https://banes-lab.com/records/lexicon/locator-tag.md): A formal definition of the tag for a file that finds where a service or a resource lives, filed in a locators folder.
- [Loader Tag](https://banes-lab.com/records/lexicon/loader-tag.md): A formal definition of the tag for a file that reads a resource from storage or the network into memory, filed in a loaders folder.
- [Dependency-Management Tag](https://banes-lab.com/records/lexicon/dependency-management-tag.md): A formal definition of the tag for a file that declares and resolves the versions of the packages a unit depends on, filed in a dependency-management folder.
- [Compatibility Tag](https://banes-lab.com/records/lexicon/compatibility-tag.md): A formal definition of the tag for a file that decides whether two versions or environments can work together, filed in a compatibility folder.
- [Compatibility-Layer Tag](https://banes-lab.com/records/lexicon/compatibility-layer-tag.md): A formal definition of the tag for a file that presents an old interface on top of a new implementation, filed in a compatibility-layers folder.
- [Compatibility-Shim Tag](https://banes-lab.com/records/lexicon/compatibility-shim-tag.md): A formal definition of the tag for a file that patches one small difference between environments so shared code runs on both, filed in a compatibility-shims folder.
- [Polyfill Tag](https://banes-lab.com/records/lexicon/polyfill-tag.md): A formal definition of the tag for a file that supplies a platform feature where the running platform lacks it, filed in a polyfills folder.
- [Versioning Tag](https://banes-lab.com/records/lexicon/versioning-tag.md): A formal definition of the tag for a file that assigns, compares or migrates between versions, filed in a versioning folder.
- [Deprecation Tag](https://banes-lab.com/records/lexicon/deprecation-tag.md): A formal definition of the tag for a file that marks a surface as scheduled for removal and reports its uses, filed in a deprecations folder.
- [Cache Tag](https://banes-lab.com/records/lexicon/cache-tag.md): A formal definition of the tag for a file that keeps computed or fetched values so a repeated request is answered without the original work, filed in a caches folder.
- [Cache-Key Tag](https://banes-lab.com/records/lexicon/cache-key-tag.md): A formal definition of the tag for a file that derives the key a cached value is stored and found under, filed in a cache-keys folder.
- [Invalidation Tag](https://banes-lab.com/records/lexicon/invalidation-tag.md): A formal definition of the tag for a file that decides when a cached value no longer holds and removes it, filed in an invalidation folder.
- [Eviction Tag](https://banes-lab.com/records/lexicon/eviction-tag.md): A formal definition of the tag for a file that chooses which entries a full cache drops, filed in an eviction folder.
- [Expiration Tag](https://banes-lab.com/records/lexicon/expiration-tag.md): A formal definition of the tag for a file that ends an entry's life after a stated condition or time, filed in an expiration folder.
- [Memoization Tag](https://banes-lab.com/records/lexicon/memoization-tag.md): A formal definition of the tag for a file that remembers a function's results by its arguments, filed in a memoization folder.
- [Prefetching Tag](https://banes-lab.com/records/lexicon/prefetching-tag.md): A formal definition of the tag for a file that loads what is likely to be needed before it is asked for, filed in a prefetching folder.
- [Pooling Tag](https://banes-lab.com/records/lexicon/pooling-tag.md): A formal definition of the tag for a file that decides how pooled resources are sized, lent and returned, filed in a pooling folder.
- [Batching Tag](https://banes-lab.com/records/lexicon/batching-tag.md): A formal definition of the tag for a file that groups many small operations into fewer larger ones, filed in a batching folder.
- [Lazy-Loading Tag](https://banes-lab.com/records/lexicon/lazy-loading-tag.md): A formal definition of the tag for a file that defers loading a part until the first time it is used, filed in a lazy-loading folder.
- [Compression Tag](https://banes-lab.com/records/lexicon/compression-tag.md): A formal definition of the tag for a file that encodes data into fewer bytes and restores it, filed in a compression folder.
- [Config Tag](https://banes-lab.com/records/lexicon/config-tag.md): A formal definition of the mass tag for a file that holds the settings a unit reads at start, singular in both folder and tag.
- [Setting Tag](https://banes-lab.com/records/lexicon/setting-tag.md): A formal definition of the tag for a file that defines one configurable option with its type and default, filed in a settings folder.
- [Profile Tag](https://banes-lab.com/records/lexicon/profile-tag.md): A formal definition of the tag for a file that bundles a named set of settings chosen together, filed in a profiles folder.
- [Environment Tag](https://banes-lab.com/records/lexicon/environment-tag.md): A formal definition of the tag for a file that reads and validates the values that differ between deployments, filed in an environments folder.
- [Preference Tag](https://banes-lab.com/records/lexicon/preference-tag.md): A formal definition of the tag for a file that holds a participant's own choices and how they persist, filed in a preferences folder.
- [Override Tag](https://banes-lab.com/records/lexicon/override-tag.md): A formal definition of the tag for a file that replaces a default setting for a stated scope, filed in an overrides folder.
- [Parameter Tag](https://banes-lab.com/records/lexicon/parameter-tag.md): A formal definition of the tag for a file that declares the parameters an operation accepts with their bounds, filed in a parameters folder.
- [Precedence Tag](https://banes-lab.com/records/lexicon/precedence-tag.md): A formal definition of the tag for a file that decides which of several conflicting sources of a setting wins, filed in a precedence folder.
- [Flag Tag](https://banes-lab.com/records/lexicon/flag-tag.md): A formal definition of the tag for a file that defines a boolean switch read at run time, filed in a flags folder.
- [Feature-Flag Tag](https://banes-lab.com/records/lexicon/feature-flag-tag.md): A formal definition of the tag for a file that turns one feature on or off for a stated audience without a deploy, filed in a feature-flags folder.
- [Toggle Tag](https://banes-lab.com/records/lexicon/toggle-tag.md): A formal definition of the tag for a file that switches between two behaviors from a control a participant sets, filed in a toggles folder.
- [Kill-Switch Tag](https://banes-lab.com/records/lexicon/kill-switch-tag.md): A formal definition of the tag for a file that disables a capability immediately when it misbehaves, filed in a kill-switches folder.
- [Remote-Config Tag](https://banes-lab.com/records/lexicon/remote-config-tag.md): A formal definition of the tag for a file that fetches settings from a service while the program runs, filed in a remote-config folder.
- [Persistence Tag](https://banes-lab.com/records/lexicon/persistence-tag.md): A formal definition of the tag for a file that saves state so it survives the process, filed in a persistence folder.
- [Storage Tag](https://banes-lab.com/records/lexicon/storage-tag.md): A formal definition of the tag for a file that wraps a storage medium behind reads and writes of bytes or records, filed in a storage folder.
- [Repository Tag](https://banes-lab.com/records/lexicon/repository-tag.md): A formal definition of the tag for a file that gives domain code a collection-like interface over stored records, filed in a repositories folder.
- [Migration Tag](https://banes-lab.com/records/lexicon/migration-tag.md): A formal definition of the tag for a file that moves stored data or a schema from one version to the next, filed in a migrations folder.
- [Bus Tag](https://banes-lab.com/records/lexicon/bus-tag.md): A formal definition of the tag for a file that carries messages between publishers and subscribers who never refer to each other, filed in a buses folder.
- [Topic Tag](https://banes-lab.com/records/lexicon/topic-tag.md): A formal definition of the tag for a file that defines a named stream of messages and its schema, filed in a topics folder.
- [Stream Tag](https://banes-lab.com/records/lexicon/stream-tag.md): A formal definition of the tag for a file that defines an ordered, unbounded sequence of records processed as they arrive, filed in a streams folder.
- [Asset Tag](https://banes-lab.com/records/lexicon/asset-tag.md): A formal definition of the tag for a file that locates and describes a static resource the product serves, filed in an assets folder.
- [Font Tag](https://banes-lab.com/records/lexicon/font-tag.md): A formal definition of the tag for a file that declares a typeface and how it loads, filed in a fonts folder.
- [Icons Tag](https://banes-lab.com/records/lexicon/icons-tag.md): A formal definition of the collection tag for a file that declares the icons a product uses, plural in both folder and tag.
- [Endpoint Tag](https://banes-lab.com/records/lexicon/endpoint-tag.md): A formal definition of the tag for a file that defines one address a service answers and the request it accepts, filed in an endpoints folder.
- [Error Tag](https://banes-lab.com/records/lexicon/error-tag.md): A formal definition of the tag for a file that defines the errors a unit can raise and what each carries, filed in an errors folder.
- [Exception Tag](https://banes-lab.com/records/lexicon/exception-tag.md): A formal definition of the tag for a file that defines a thrown condition that interrupts normal flow, filed in an exceptions folder.
- [Fault Tag](https://banes-lab.com/records/lexicon/fault-tag.md): A formal definition of the tag for a file that describes a defect in a component that can cause failures, filed in a faults folder.
- [Failure Tag](https://banes-lab.com/records/lexicon/failure-tag.md): A formal definition of the tag for a file that describes how an operation failed so its caller can decide what to do, filed in a failures folder.
- [Result Tag](https://banes-lab.com/records/lexicon/result-tag.md): A formal definition of the tag for a file that defines a return value carrying either a success or a failure, filed in a results folder.
- [Error-Code Tag](https://banes-lab.com/records/lexicon/error-code-tag.md): A formal definition of the tag for a file that declares the stable codes callers match failures on, filed in an error-codes folder.
- [Error-Boundary Tag](https://banes-lab.com/records/lexicon/error-boundary-tag.md): A formal definition of the tag for a file that contains a failure within one part so the rest keeps running, filed in an error-boundaries folder.
- [Recovery Tag](https://banes-lab.com/records/lexicon/recovery-tag.md): A formal definition of the tag for a file that returns a failed part to a working state, filed in a recovery folder.
- [Fallback Tag](https://banes-lab.com/records/lexicon/fallback-tag.md): A formal definition of the tag for a file that supplies a declared substitute when the primary path fails, filed in a fallbacks folder.
- [Error-Reporting Tag](https://banes-lab.com/records/lexicon/error-reporting-tag.md): A formal definition of the tag for a file that sends failures with their context to where they are tracked, filed in an error-reporting folder.
- [Resilience Tag](https://banes-lab.com/records/lexicon/resilience-tag.md): A formal definition of the tag for a file that keeps an operation working through transient failures of what it depends on, filed in a resilience folder.
- [Throttling Tag](https://banes-lab.com/records/lexicon/throttling-tag.md): A formal definition of the tag for a file that limits how often an operation may run, filed in a throttling folder.
- [Deduplication Tag](https://banes-lab.com/records/lexicon/deduplication-tag.md): A formal definition of the tag for a file that recognizes a repeated request or record and processes it once, filed in a deduplication folder.
- [Cancellation Tag](https://banes-lab.com/records/lexicon/cancellation-tag.md): A formal definition of the tag for a file that stops work in progress when its caller no longer needs the result, filed in a cancellation folder.
- [Metric Tag](https://banes-lab.com/records/lexicon/metric-tag.md): A formal definition of the tag for a file that defines and records a measured quantity over time, filed in a metrics folder.
- [Counter Tag](https://banes-lab.com/records/lexicon/counter-tag.md): A formal definition of the tag for a file that counts occurrences of one kind of event, filed in a counters folder.
- [Reporter Tag](https://banes-lab.com/records/lexicon/reporter-tag.md): A formal definition of the tag for a file that renders findings or measurements for the party that asked for them, filed in a reporters folder.
- [Health Tag](https://banes-lab.com/records/lexicon/health-tag.md): A formal definition of the tag for a file that answers whether a component is able to do its work, filed in a health folder.
- [Probe Tag](https://banes-lab.com/records/lexicon/probe-tag.md): A formal definition of the tag for a file that observes a running system and records what it finds without changing it, filed in a probes folder.
- [Alert Tag](https://banes-lab.com/records/lexicon/alert-tag.md): A formal definition of the tag for a file that defines a condition that warrants attention and who is told, filed in an alerts folder.
- [Notification Tag](https://banes-lab.com/records/lexicon/notification-tag.md): A formal definition of the tag for a file that delivers a message to a participant through a declared channel, filed in a notifications folder.
- [Reader Tag](https://banes-lab.com/records/lexicon/reader-tag.md): A formal definition of the tag for a file that reads a stored or external format into structure the system works with, filed in a readers folder.
- [Writer Tag](https://banes-lab.com/records/lexicon/writer-tag.md): A formal definition of the tag for a file that writes structure out to a stored or external format, filed in a writers folder.
- [Converter Tag](https://banes-lab.com/records/lexicon/converter-tag.md): A formal definition of the tag for a file that turns one representation into another of the same content, filed in a converters folder.
- [Formatter Tag](https://banes-lab.com/records/lexicon/formatter-tag.md): A formal definition of the tag for a file that lays data out as text in a target format such as Markdown, JSON or source code, filed in a formatters folder.
- [Normalizer Tag](https://banes-lab.com/records/lexicon/normalizer-tag.md): A formal definition of the tag for a file that brings varied input to one canonical form before it is compared or stored, filed in a normalizers folder.
- [Sanitizer Tag](https://banes-lab.com/records/lexicon/sanitizer-tag.md): A formal definition of the tag for a file that removes or escapes the parts of untrusted input that could do harm, filed in a sanitizers folder.
- [Mapper Tag](https://banes-lab.com/records/lexicon/mapper-tag.md): A formal definition of the tag for a file that maps the fields of one model onto another, filed in a mappers folder.
- [Transformer Tag](https://banes-lab.com/records/lexicon/transformer-tag.md): A formal definition of the tag for a file that maps an input state to an output state, including a fix that rewrites a file, filed in a transformers folder.
- [Pipeline Tag](https://banes-lab.com/records/lexicon/pipeline-tag.md): A formal definition of the tag for a file that chains processing stages so each consumes the one before, filed in a pipelines folder.
- [Source Tag](https://banes-lab.com/records/lexicon/source-tag.md): A formal definition of the tag for a file that produces the records a pipeline starts from, filed in a sources folder.
- [Sink Tag](https://banes-lab.com/records/lexicon/sink-tag.md): A formal definition of the tag for a file that receives the records a pipeline ends with, filed in a sinks folder.
- [Processor Tag](https://banes-lab.com/records/lexicon/processor-tag.md): A formal definition of the tag for a file that applies one processing operation to each item that passes through it, filed in a processors folder.
- [Filter Tag](https://banes-lab.com/records/lexicon/filter-tag.md): A formal definition of the tag for a file that keeps the items meeting a condition and drops the rest, filed in a filters folder.
- [Validator Tag](https://banes-lab.com/records/lexicon/validator-tag.md): A formal definition of the tag for a file that decides whether its input is valid and reports why it is not, filed in a validators folder.
- [Matcher Tag](https://banes-lab.com/records/lexicon/matcher-tag.md): A formal definition of the tag for a file that tests whether a value fits a shape and reports what it matched, filed in a matchers folder.
- [Aggregator Tag](https://banes-lab.com/records/lexicon/aggregator-tag.md): A formal definition of the tag for a file that combines many items into one summary value, filed in an aggregators folder.
- [Comparator Tag](https://banes-lab.com/records/lexicon/comparator-tag.md): A formal definition of the tag for a file that decides the order or the difference between two values, filed in a comparators folder.
- [Sorter Tag](https://banes-lab.com/records/lexicon/sorter-tag.md): A formal definition of the tag for a file that arranges a set of items in an order a comparison defines, filed in a sorters folder.
- [Iterator Tag](https://banes-lab.com/records/lexicon/iterator-tag.md): A formal definition of the tag for a file that yields the members of a set one at a time, filed in an iterators folder.
- [Generator Tag](https://banes-lab.com/records/lexicon/generator-tag.md): A formal definition of the tag for a file that produces values or files from a description of them, filed in a generators folder.
- [Analyzer Tag](https://banes-lab.com/records/lexicon/analyzer-tag.md): A formal definition of the tag for a file that reads a body of material and derives facts about it without judging it, filed in an analyzers folder.
- [Inspector Tag](https://banes-lab.com/records/lexicon/inspector-tag.md): A formal definition of the tag for a file that looks into one artifact and reports what it holds, filed in an inspectors folder.
- [Key Tag](https://banes-lab.com/records/lexicon/key-tag.md): A formal definition of the tag for a file that creates, holds or rotates cryptographic keys, filed in a keys folder.
- [Hashing Tag](https://banes-lab.com/records/lexicon/hashing-tag.md): A formal definition of the tag for a file that computes fixed-size fingerprints of content, filed in a hashing folder.
- [Digest Tag](https://banes-lab.com/records/lexicon/digest-tag.md): A formal definition of the tag for a file that computes a cryptographic summary of content for integrity checks, filed in a digests folder.
- [Randomness Tag](https://banes-lab.com/records/lexicon/randomness-tag.md): A formal definition of the tag for a file that supplies random values from a declared and, where needed, seeded source, filed in a randomness folder.
- [Lexer Tag](https://banes-lab.com/records/lexicon/lexer-tag.md): A formal definition of the tag for a file that splits source text into tokens, filed in a lexers folder.
- [Parser Tag](https://banes-lab.com/records/lexicon/parser-tag.md): A formal definition of the tag for a file that builds a syntax tree from tokens by a grammar, filed in a parsers folder.
- [Grammar Tag](https://banes-lab.com/records/lexicon/grammar-tag.md): A formal definition of the tag for a file that declares the productions a language is parsed by, filed in a grammars folder.
- [Visitor Tag](https://banes-lab.com/records/lexicon/visitor-tag.md): A formal definition of the tag for a file that walks a syntax tree and acts on each node kind it meets, filed in a visitors folder.
- [Pass Tag](https://banes-lab.com/records/lexicon/pass-tag.md): A formal definition of the tag for a file that performs one full traversal of a program or a frame to transform or render it, filed in a passes folder.
- [Extractor Tag](https://banes-lab.com/records/lexicon/extractor-tag.md): A formal definition of the tag for a file that pulls the records a transformation needs out of a larger source, filed in an extractors folder.
- [Partition Tag](https://banes-lab.com/records/lexicon/partition-tag.md): A formal definition of the tag for a file that splits a data set into parts processed or stored separately, filed in a partitions folder.
- [Grid Tag](https://banes-lab.com/records/lexicon/grid-tag.md): A formal definition of the tag for a file that defines a regular division of space into cells, filed in a grids folder.
- [Tile Tag](https://banes-lab.com/records/lexicon/tile-tag.md): A formal definition of the tag for a file that defines one cell of a tiled world and what occupies it, filed in a tiles folder.
- [Collider Tag](https://banes-lab.com/records/lexicon/collider-tag.md): A formal definition of the tag for a file that defines a shape used to detect when two objects touch, filed in a colliders folder.
- [Bounds Tag](https://banes-lab.com/records/lexicon/bounds-tag.md): A formal definition of the tag for a file that computes the extents enclosing an object or a region, filed in a bounds folder.
- [Raycast Tag](https://banes-lab.com/records/lexicon/raycast-tag.md): A formal definition of the tag for a file that finds what a line through space hits first, filed in a raycasts folder.
- [Animation Tag](https://banes-lab.com/records/lexicon/animation-tag.md): A formal definition of the tag for a file that defines how a value or a pose changes over a span of time, filed in an animations folder.
- [Easing Tag](https://banes-lab.com/records/lexicon/easing-tag.md): A formal definition of the tag for a file that maps linear progress onto a curve of acceleration and deceleration, filed in an easings folder.
- [Curve Tag](https://banes-lab.com/records/lexicon/curve-tag.md): A formal definition of the tag for a file that defines a parametric path or response curve, filed in a curves folder.
- [Tween Tag](https://banes-lab.com/records/lexicon/tween-tag.md): A formal definition of the tag for a file that interpolates a value between two endpoints over time, filed in a tweens folder.
- [Trajectory Tag](https://banes-lab.com/records/lexicon/trajectory-tag.md): A formal definition of the tag for a file that computes the path a moving object follows under its forces, filed in a trajectories folder.
- [Path Tag](https://banes-lab.com/records/lexicon/path-tag.md): A formal definition of the tag for a file that finds or defines a route between two points, filed in a paths folder.
- [Formation Tag](https://banes-lab.com/records/lexicon/formation-tag.md): A formal definition of the tag for a file that arranges a group of agents in a shape relative to a leader, filed in a formations folder.
- [Test Tag](https://banes-lab.com/records/lexicon/test-tag.md): A formal definition of the compound marker for a file that exercises another file and asserts on the outcome, which is exempt from the naming grammar and placed in its subject's mirrored concern folder.
- [Suite Tag](https://banes-lab.com/records/lexicon/suite-tag.md): A formal definition of the tag for a file that groups related test cases under one setup, filed in a suites folder.
- [Case Tag](https://banes-lab.com/records/lexicon/case-tag.md): A formal definition of the tag for a file that holds the inputs and expected outcomes one test runs, filed in a cases folder.
- [Fixture Tag](https://banes-lab.com/records/lexicon/fixture-tag.md): A formal definition of the tag for a file that provides the known state or samples a test starts from, filed in a fixtures folder.
- [Mock Tag](https://banes-lab.com/records/lexicon/mock-tag.md): A formal definition of the tag for a file that stands in for a collaborator and records how it was called, filed in a mocks folder.
- [Fake Tag](https://banes-lab.com/records/lexicon/fake-tag.md): A formal definition of the tag for a file that implements a collaborator in a simpler working form for tests, filed in a fakes folder.
- [Stub Tag](https://banes-lab.com/records/lexicon/stub-tag.md): A formal definition of the tag for a file that returns fixed answers in place of a collaborator, filed in a stubs folder.
- [Spy Tag](https://banes-lab.com/records/lexicon/spy-tag.md): A formal definition of the tag for a file that wraps a real collaborator and records its calls, filed in a spies folder.
- [Double Tag](https://banes-lab.com/records/lexicon/double-tag.md): A formal definition of the tag for a file that replaces a collaborator in a test when no narrower double names its role, filed in a doubles folder.
- [Assertion Tag](https://banes-lab.com/records/lexicon/assertion-tag.md): A formal definition of the tag for a file that defines reusable checks tests apply to outcomes, filed in an assertions folder.
- [Harness Tag](https://banes-lab.com/records/lexicon/harness-tag.md): A formal definition of the tag for a file that sets up and drives the environment a subject is tested in, filed in a harnesses folder.
- [Runner Tag](https://banes-lab.com/records/lexicon/runner-tag.md): A formal definition of the tag for a file that discovers and runs a set of tests or tasks and collects their results, filed in a runners folder.
- [Coverage Tag](https://banes-lab.com/records/lexicon/coverage-tag.md): A formal definition of the tag for a file that measures which parts of a subject its tests reach, filed in a coverage folder.
- [Reference Tag](https://banes-lab.com/records/lexicon/reference-tag.md): A formal definition of the tag for a file of authored knowledge a reader consults, such as a guide or a note, filed in a references folder.
- [View Tag](https://banes-lab.com/records/lexicon/view-tag.md): A formal definition of the tag for a file that renders one screen or page from the state it is given, filed in a views folder.
- [Component Tag](https://banes-lab.com/records/lexicon/component-tag.md): A formal definition of the tag for a file that renders one reusable piece of interface with its own inputs, filed in a components folder.
- [Widget Tag](https://banes-lab.com/records/lexicon/widget-tag.md): A formal definition of the tag for a file that renders one interactive control, filed in a widgets folder.
- [Layout Tag](https://banes-lab.com/records/lexicon/layout-tag.md): A formal definition of the tag for a file that arranges regions of an interface without deciding their contents, filed in a layouts folder.
- [Template Tag](https://banes-lab.com/records/lexicon/template-tag.md): A formal definition of the tag for a file that holds a shape with slots that are filled to produce an output, filed in a templates folder.
- [Theme Tag](https://banes-lab.com/records/lexicon/theme-tag.md): A formal definition of the tag for a file that selects one coherent set of visual values for a whole interface, filed in a themes folder.
- [Style Tag](https://banes-lab.com/records/lexicon/style-tag.md): A formal definition of the tag for a file that holds the presentation rules for one surface, filed in a styles folder.
- [Tokens Tag](https://banes-lab.com/records/lexicon/tokens-tag.md): A formal definition of the collection tag for a file that declares named design values such as colors and spacing, plural in both folder and tag.
- [Strings Tag](https://banes-lab.com/records/lexicon/strings-tag.md): A formal definition of the collection tag for a file that holds the user-visible text a surface displays, plural in both folder and tag.
- [Accessibility Tag](https://banes-lab.com/records/lexicon/accessibility-tag.md): A formal definition of the tag for a file that makes an interface usable through assistive technology, filed in an accessibility folder.
- [Command Tag](https://banes-lab.com/records/lexicon/command-tag.md): A formal definition of the tag for a file that defines one command a command-line or chat surface accepts, filed in a commands folder.
- [Prompt Tag](https://banes-lab.com/records/lexicon/prompt-tag.md): A formal definition of the tag for a file that asks a participant for input and validates the answer, filed in a prompts folder.
- [Printer Tag](https://banes-lab.com/records/lexicon/printer-tag.md): A formal definition of the tag for a file that writes a command surface's output to a terminal, filed in a printers folder.
- [Renderer Tag](https://banes-lab.com/records/lexicon/renderer-tag.md): A formal definition of the tag for a file that draws frames to a display from a scene or a model, filed in a renderers folder.
- [Shader Tag](https://banes-lab.com/records/lexicon/shader-tag.md): A formal definition of the tag for a file that holds a program the graphics processor runs per vertex or per pixel, filed in a shaders folder.
- [Material Tag](https://banes-lab.com/records/lexicon/material-tag.md): A formal definition of the tag for a file that defines how a surface reflects light and which textures it uses, filed in a materials folder.
- [Sprite Tag](https://banes-lab.com/records/lexicon/sprite-tag.md): A formal definition of the tag for a file that defines a two-dimensional image drawn and moved as one object, filed in a sprites folder.
- [Atlas Tag](https://banes-lab.com/records/lexicon/atlas-tag.md): A formal definition of the tag for a file that packs many images into one texture with the coordinates of each, filed in an atlases folder.
- [Geometry Tag](https://banes-lab.com/records/lexicon/geometry-tag.md): A formal definition of the mass tag for a file that holds shapes as vertices and faces, singular in both folder and tag.
- [Camera Tag](https://banes-lab.com/records/lexicon/camera-tag.md): A formal definition of the tag for a file that defines the viewpoint and projection a scene is seen through, filed in a cameras folder.
- [Viewport Tag](https://banes-lab.com/records/lexicon/viewport-tag.md): A formal definition of the tag for a file that defines the region of a display a camera draws into, filed in a viewports folder.
- [Frame Tag](https://banes-lab.com/records/lexicon/frame-tag.md): A formal definition of the tag for a file that defines one rendered image in a sequence and what it contains, filed in a frames folder.
- [Effect Tag](https://banes-lab.com/records/lexicon/effect-tag.md): A formal definition of the tag for a file that adds visual or audio feedback to an event without changing the state behind it, filed in an effects folder.
- [Particle Tag](https://banes-lab.com/records/lexicon/particle-tag.md): A formal definition of the tag for a file that simulates many small short-lived elements such as sparks or smoke, filed in a particles folder.
- [Telegraph Tag](https://banes-lab.com/records/lexicon/telegraph-tag.md): A formal definition of the tag for a file that signals an action before it lands so a participant can react, filed in a telegraphs folder.
- [Respawn Tag](https://banes-lab.com/records/lexicon/respawn-tag.md): A formal definition of the tag for a file that returns a removed participant or object to the world under stated rules, filed in a respawn folder.
- [Spawner or Prefab as a Tag](https://banes-lab.com/records/lexicon/spawner-or-prefab-as-a-tag.md): Tagging a file spawner or prefab, where the factory tag already covers a file that constructs instances.
- [Blueprint or Archetype as a Tag](https://banes-lab.com/records/lexicon/blueprint-or-archetype-as-a-tag.md): Tagging a file blueprint or archetype, where the specification tag covers a file that declares a rule and the template tag covers one that declares a shape.
- [Loop or Tick as a Tag](https://banes-lab.com/records/lexicon/loop-or-tick-as-a-tag.md): Tagging a simulation's main loop or its tick as its own concern, where the engine tag covers the file that runs the loop and the step tag covers one advance.
- [Batcher as a Tag](https://banes-lab.com/records/lexicon/batcher-as-a-tag.md): Tagging a file batcher, where the batching tag already covers a file that groups small operations into larger ones.
- [Spatial Index as a Tag](https://banes-lab.com/records/lexicon/spatial-index-as-a-tag.md): Tagging a spatial hash or a quadtree as a domain concern, where a lookup structure over known members takes the registry tag.
- [Keybinding as a Tag](https://banes-lab.com/records/lexicon/keybinding-as-a-tag.md): Tagging a file keybinding or control-scheme, where the binding tag already covers a file that ties a name to what it resolves to.
- [Control Widget as a Tag](https://banes-lab.com/records/lexicon/control-widget-as-a-tag.md): Tagging a slider or a toggle control by its kind of control, where the widget tag covers every interactive control.
- [Condition as a Tag](https://banes-lab.com/records/lexicon/condition-as-a-tag.md): Tagging a file condition or phase-condition, where the predicate tag already covers a file that answers yes or no.
- [Strategy as a Tag](https://banes-lab.com/records/lexicon/strategy-as-a-tag.md): Tagging a file strategy or difficulty-policy, where the policy tag already covers a file that chooses among behaviors by a rule.
- [Agent Memory as a Tag](https://banes-lab.com/records/lexicon/agent-memory-as-a-tag.md): Tagging a file pattern-memory or agent-memory, where the memory tag already covers what an agent remembers between steps.
- [Savegame as a Tag](https://banes-lab.com/records/lexicon/savegame-as-a-tag.md): Tagging a file savegame or autosave, where the persistence tag covers saving state and the store tag covers holding it.
- [Pause or Boot as a Tag](https://banes-lab.com/records/lexicon/pause-or-boot-as-a-tag.md): Tagging a file after one lifecycle moment such as pause, boot or teardown, where the lifecycle tag covers how a component starts and stops.
- [Screen or Page as a Tag](https://banes-lab.com/records/lexicon/screen-or-page-as-a-tag.md): Tagging a file endscreen, hud-panel or page, where the view tag covers a file that renders one screen.
- [Page Script as a Tag](https://banes-lab.com/records/lexicon/page-script-as-a-tag.md): Tagging a file page-script, where the entrypoint tag covers the file a runtime starts from.
- [Preloader as a Tag](https://banes-lab.com/records/lexicon/preloader-as-a-tag.md): Tagging a file preloader or asset-loader, where the loader tag already covers reading a resource into memory.
- [Object Pool as a Tag](https://banes-lab.com/records/lexicon/object-pool-as-a-tag.md): Tagging a file object-pool, where the pool tag already covers keeping reusable instances.
- [Cooldown as a Tag](https://banes-lab.com/records/lexicon/cooldown-as-a-tag.md): Tagging a file cooldown or throttle, where the throttling tag covers limiting how often something runs and the timer tag covers running it after a delay.
- [Thread as a Tag](https://banes-lab.com/records/lexicon/thread-as-a-tag.md): Tagging a file thread, where the worker tag covers running work apart from the caller.
- [Particle Emitter as a Tag](https://banes-lab.com/records/lexicon/particle-emitter-as-a-tag.md): Tagging a file particle-emitter, where the emitter tag already covers a file that produces output for others to receive.
- [Juice or Screenshake as a Tag](https://banes-lab.com/records/lexicon/juice-or-screenshake-as-a-tag.md): Tagging a file feedback, juice or screenshake, where the effect tag covers feedback that leaves the state behind it unchanged.
- [Manager as a Tag](https://banes-lab.com/records/lexicon/manager-as-a-tag.md): Tagging a file manager, which names a stature rather than a role, where the coordinator tag covers a file that owns a lifecycle and the service tag one that offers a stateful capability.
- [Page Feature as a Tag](https://banes-lab.com/records/lexicon/page-feature-as-a-tag.md): Tagging a file page-feature or plug-in behavior, where the extension and plugin tags cover capability added to a host.
- [Id Table as a Tag](https://banes-lab.com/records/lexicon/id-table-as-a-tag.md): Tagging a file ids, id-table or symbol-table, where the constants collection tag covers a file of fixed named values.
- [Attack Pattern as a Tag](https://banes-lab.com/records/lexicon/attack-pattern-as-a-tag.md): Tagging a file weapon-pattern or attack-pattern, where the behavior tag covers a file that decides and the specification tag one that only declares.
- [Checker or Linter as a Tag](https://banes-lab.com/records/lexicon/checker-or-linter-as-a-tag.md): Tagging a file checker or linter, where the validator tag covers a file that decides whether its input is valid.
- [Scanner as a Tag](https://banes-lab.com/records/lexicon/scanner-as-a-tag.md): Tagging a file scanner, which overlaps reporter and inspector, where the analyzer and inspector tags cover a file that reads material and derives facts from it.
- [Fixer or Healer as a Tag](https://banes-lab.com/records/lexicon/fixer-or-healer-as-a-tag.md): Tagging a file fixer, healer or repairer, where the transformer tag covers a file that maps an input state to an output state.
- [Walker or Crawler as a Tag](https://banes-lab.com/records/lexicon/walker-or-crawler-as-a-tag.md): Tagging a file walker or crawler, where the iterator tag covers a file that yields the members of a set.
- [Gate as a Tag](https://banes-lab.com/records/lexicon/gate-as-a-tag.md): Tagging a file gate, which names a decision rather than a thing, where the predicate and validator tags cover the decision it makes.
- [Index as a Tag](https://banes-lab.com/records/lexicon/index-as-a-tag.md): Tagging a file index, which overlaps cache and registry, where the registry tag covers a lookup over known members.
- [Handler as a Tag](https://banes-lab.com/records/lexicon/handler-as-a-tag.md): Tagging a file handler, which fits every role, where the processor tag covers applying an operation to each item and the coordinator tag covers driving collaborators.
- [Guide or Note as a Tag](https://banes-lab.com/records/lexicon/guide-or-note-as-a-tag.md): Tagging a file doc, guide or note, where the reference tag covers authored knowledge a reader consults.
- [Plan as a Tag](https://banes-lab.com/records/lexicon/plan-as-a-tag.md): Tagging a file plan, where the specification tag covers a file that declares a required end state.
- [Entrypoint Tag](https://banes-lab.com/records/lexicon/entrypoint-tag.md): A formal definition of the tag for a file a runtime starts from, which reads its arguments and hands control to the code behind it, filed in an entrypoints folder.
- [Bootstrapper Tag](https://banes-lab.com/records/lexicon/bootstrapper-tag.md): A formal definition of the tag for a file that assembles the system's parts in order before it serves anything, filed in a bootstrappers folder.
- [Initializer Tag](https://banes-lab.com/records/lexicon/initializer-tag.md): A formal definition of the tag for a file that prepares one component's starting state, filed in an initializers folder.
- [Activator Tag](https://banes-lab.com/records/lexicon/activator-tag.md): A formal definition of the tag for a file that switches a prepared component into its active state when its trigger arrives, filed in an activators folder.
- [Lifecycle Tag](https://banes-lab.com/records/lexicon/lifecycle-tag.md): A formal definition of the tag for a file that governs how a component starts, pauses, resumes and stops, filed in a lifecycle folder.
- [Lifecycle-Hook Tag](https://banes-lab.com/records/lexicon/lifecycle-hook-tag.md): A formal definition of the tag for a file that runs at one named point of a component's lifecycle, filed in a lifecycle-hooks folder.
- [Startup Tag](https://banes-lab.com/records/lexicon/startup-tag.md): A formal definition of the tag for a file that runs the work a process must finish before it accepts any, filed in a startup folder.
- [Warmup Tag](https://banes-lab.com/records/lexicon/warmup-tag.md): A formal definition of the tag for a file that primes caches and connections so the first real request runs at normal speed, filed in a warmup folder.
- [Draining Tag](https://banes-lab.com/records/lexicon/draining-tag.md): A formal definition of the tag for a file that lets in-flight work finish while refusing new work before a stop, filed in a draining folder.
- [Shutdown Tag](https://banes-lab.com/records/lexicon/shutdown-tag.md): A formal definition of the tag for a file that stops a process in an order that loses no committed work, filed in a shutdown folder.
- [Teardown Tag](https://banes-lab.com/records/lexicon/teardown-tag.md): A formal definition of the tag for a file that removes what a setup created, such as fixtures or temporary resources, filed in a teardown folder.
- [Disposal Tag](https://banes-lab.com/records/lexicon/disposal-tag.md): A formal definition of the tag for a file that releases the resources an object holds when the object is no longer used, filed in a disposal folder.
- [Cleanup Tag](https://banes-lab.com/records/lexicon/cleanup-tag.md): A formal definition of the tag for a file that removes leftover state a finished operation leaves behind, filed in a cleanup folder.
- [Finalizer Tag](https://banes-lab.com/records/lexicon/finalizer-tag.md): A formal definition of the tag for a file that runs last work on an object as the runtime reclaims it, filed in a finalizers folder.
- [Runtime Tag](https://banes-lab.com/records/lexicon/runtime-tag.md): A formal definition of the tag for a file that provides the environment other code executes inside, filed in a runtimes folder.
- [Engine Tag](https://banes-lab.com/records/lexicon/engine-tag.md): A formal definition of the tag for a file that runs the central loop advancing a system's state, filed in an engines folder.
- [Executor Tag](https://banes-lab.com/records/lexicon/executor-tag.md): A formal definition of the tag for a file that runs submitted work on the resources it manages, filed in an executors folder.
- [Evaluator Tag](https://banes-lab.com/records/lexicon/evaluator-tag.md): A formal definition of the tag for a file that computes the value of an expression or a rule against given inputs, filed in an evaluators folder.
- [Interpreter Tag](https://banes-lab.com/records/lexicon/interpreter-tag.md): A formal definition of the tag for a file that executes a program by walking its representation directly, filed in an interpreters folder.
- [Scheduler Tag](https://banes-lab.com/records/lexicon/scheduler-tag.md): A formal definition of the tag for a file that decides when each piece of work runs, filed in a schedulers folder.
- [Worker Tag](https://banes-lab.com/records/lexicon/worker-tag.md): A formal definition of the tag for a file that runs work on its own thread or process apart from the caller, filed in a workers folder.
- [Future Tag](https://banes-lab.com/records/lexicon/future-tag.md): A formal definition of the tag for a file that defines a handle to a result that is not computed yet, filed in a futures folder.
- [Promise Tag](https://banes-lab.com/records/lexicon/promise-tag.md): A formal definition of the tag for a file that settles an asynchronous result once, as fulfilled or rejected, filed in a promises folder.
- [Queue Tag](https://banes-lab.com/records/lexicon/queue-tag.md): A formal definition of the tag for a file that holds items in arrival order until a consumer takes them, filed in a queues folder.
- [Channel Tag](https://banes-lab.com/records/lexicon/channel-tag.md): A formal definition of the tag for a file that carries messages between two parties of a concurrent program, filed in a channels folder.
- [Pipe Tag](https://banes-lab.com/records/lexicon/pipe-tag.md): A formal definition of the tag for a file that connects one stage's output directly to the next stage's input as a byte or item stream, filed in a pipes folder.
- [Mailbox Tag](https://banes-lab.com/records/lexicon/mailbox-tag.md): A formal definition of the tag for a file that holds the messages addressed to one actor until it processes them, filed in a mailboxes folder.
- [Pool Tag](https://banes-lab.com/records/lexicon/pool-tag.md): A formal definition of the tag for a file that keeps reusable instances and lends them out instead of creating new ones, filed in a pools folder.
- [Memory Tag](https://banes-lab.com/records/lexicon/memory-tag.md): A formal definition of the tag for a file that holds what an agent or a process remembers between steps, filed in a memory folder.
- [Heap Tag](https://banes-lab.com/records/lexicon/heap-tag.md): A formal definition of the tag for a file that keeps items ordered so the highest-priority one is always taken first, filed in a heaps folder.
- [Handle Tag](https://banes-lab.com/records/lexicon/handle-tag.md): A formal definition of the tag for a file that defines an opaque reference to a resource another part of the system owns, filed in a handles folder.
- [Clock Tag](https://banes-lab.com/records/lexicon/clock-tag.md): A formal definition of the tag for a file that supplies the current time through one replaceable source, filed in a clocks folder.
- [Timer Tag](https://banes-lab.com/records/lexicon/timer-tag.md): A formal definition of the tag for a file that runs work after a delay or at a fixed rate, filed in a timers folder.
- [Timeout Tag](https://banes-lab.com/records/lexicon/timeout-tag.md): A formal definition of the tag for a file that abandons an operation that runs past its allowed time, filed in a timeouts folder.
- [Deadline Tag](https://banes-lab.com/records/lexicon/deadline-tag.md): A formal definition of the tag for a file that carries the absolute time by which a piece of work must finish, filed in a deadlines folder.
- [Delay Tag](https://banes-lab.com/records/lexicon/delay-tag.md): A formal definition of the tag for a file that defers an action by a computed amount of time, filed in a delays folder.
- [Period Tag](https://banes-lab.com/records/lexicon/period-tag.md): A formal definition of the tag for a file that defines a named span of calendar time such as a billing month, filed in a periods folder.
- [Window Tag](https://banes-lab.com/records/lexicon/window-tag.md): A formal definition of the tag for a file that groups events into bounded spans of time for aggregation, filed in a windows folder.
- [Recurrence Tag](https://banes-lab.com/records/lexicon/recurrence-tag.md): A formal definition of the tag for a file that defines a rule for repeating an event in time, filed in a recurrences folder.
- [Cron Tag](https://banes-lab.com/records/lexicon/cron-tag.md): A formal definition of the tag for a file that holds a schedule written as a cron expression, filed in a crons folder.
- [Calendar Tag](https://banes-lab.com/records/lexicon/calendar-tag.md): A formal definition of the tag for a file that answers which days count, such as working days and holidays, filed in a calendars folder.
- [Timezone Tag](https://banes-lab.com/records/lexicon/timezone-tag.md): A formal definition of the tag for a file that converts times between zones and their offsets, filed in a timezones folder.
- [Timestamp Tag](https://banes-lab.com/records/lexicon/timestamp-tag.md): A formal definition of the tag for a file that creates, parses or compares recorded instants in time, filed in a timestamps folder.
- [Ad-Hoc Endpoints](https://banes-lab.com/records/lexicon/ad-hoc-endpoints.md): Exposing inconsistent, one-off endpoints instead of a uniform interface, forcing clients to special-case each.
- [Ad-Hoc Payloads](https://banes-lab.com/records/lexicon/ad-hoc-payloads.md): Sending payloads with no agreed schema, so consumers must guess at structure and break on change.
- [Breaking API Change](https://banes-lab.com/records/lexicon/breaking-api-change.md): Changing an API in a way that violates its published contract, breaking existing clients.
- [Breaking Change](https://banes-lab.com/records/lexicon/breaking-change.md): A change that violates a component's contract, forcing consumers to update to keep working.
- [Breaking Changes](https://banes-lab.com/records/lexicon/breaking-changes.md): Changes that break existing consumers by altering behavior or shape they depend on.
- [External State Mutation](https://banes-lab.com/records/lexicon/external-state-mutation.md): Mutating state outside an object's own boundary, breaking the invariants it is supposed to guarantee.
- [Hidden Service Coupling](https://banes-lab.com/records/lexicon/hidden-service-coupling.md): An undeclared dependency between services that surfaces only at runtime, undermining independent evolution.
- [Implementation-First Integration](https://banes-lab.com/records/lexicon/implementation-first-integration.md): Integrating against a concrete implementation before agreeing a contract, coupling consumers to internals.
- [Implicit Assumptions](https://banes-lab.com/records/lexicon/implicit-assumptions.md): Relying on unstated preconditions a caller must satisfy, which break silently when they are violated.
- [Implicit Behavior](https://banes-lab.com/records/lexicon/implicit-behavior.md): Behavior a component performs that is not stated in its contract, surprising callers who come to depend on it.
- [Proprietary Coupling](https://banes-lab.com/records/lexicon/proprietary-coupling.md): Binding to a vendor's proprietary interface, forfeiting interoperability and portability.
- [Proprietary Drift](https://banes-lab.com/records/lexicon/proprietary-drift.md): Extending a standard protocol with proprietary features until it no longer interoperates with others.
- [Silent Breaking Changes](https://banes-lab.com/records/lexicon/silent-breaking-changes.md): Shipping a breaking change with no version bump or notice, so consumers fail without warning.
- [Strict Fragile Parsers](https://banes-lab.com/records/lexicon/strict-fragile-parsers.md): Parsers that reject any input deviating from an exact expectation, breaking on benign additions.
- [Undefined Results](https://banes-lab.com/records/lexicon/undefined-results.md): Returning results a contract never specifies for a given input, leaving callers with undefined behavior.
- [Compatibility Policy](https://banes-lab.com/records/lexicon/compatibility-policy.md): The declared rules governing which changes are compatible and how versions are managed.
- [Consistent Semantics](https://banes-lab.com/records/lexicon/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/lexicon/extensible-schema.md): A schema shaped so new fields can be added without breaking existing consumers.
- [Protocol Contract](https://banes-lab.com/records/lexicon/protocol-contract.md): The agreed rules of a protocol, such as its messages, formats and sequences, that both ends must honor.
- [Result Validation](https://banes-lab.com/records/lexicon/result-validation.md): The activity of checking that an operation's result satisfies its promised postconditions.
- [Semantic Contract](https://banes-lab.com/records/lexicon/semantic-contract.md): An agreement specifying not just the shape of an interface but the meaning and behavior it guarantees.
- [API Usability](https://banes-lab.com/records/lexicon/api-usability.md): The degree to which an API is easy for developers to learn and use correctly.
- [Automated Validation](https://banes-lab.com/records/lexicon/automated-validation.md): The ability to check data automatically against a declared schema.
- [Client Compatibility](https://banes-lab.com/records/lexicon/client-compatibility.md): The degree to which existing clients continue to work as an API evolves.
- [Consumer-Driven Development](https://banes-lab.com/records/lexicon/consumer-driven-development.md): The ability to shape a provider's contract from the concrete needs of its consumers.
- [Consumer-Verified Compatibility](https://banes-lab.com/records/lexicon/consumer-verified-compatibility.md): The ability to verify a provider still satisfies the contracts its consumers depend on.
- [Contract Testing](https://banes-lab.com/records/lexicon/contract-testing.md): The activity of testing that an implementation honors the contract it declares.
- [Cross-System Communication](https://banes-lab.com/records/lexicon/cross-system-communication.md): The ability for independent systems to exchange and understand data with one another.
- [Incremental Deployment](https://banes-lab.com/records/lexicon/incremental-deployment.md): The ability to roll out changes gradually while old and new versions coexist.
- [Independent Consumers](https://banes-lab.com/records/lexicon/independent-consumers.md): The ability for consumers to evolve on their own schedule because the interface stays stable.
- [Multi-Client Integration](https://banes-lab.com/records/lexicon/multi-client-integration.md): The ability to serve many different clients through one compatible protocol.
- [Provider Change Safety](https://banes-lab.com/records/lexicon/provider-change-safety.md): The degree to which a provider can change without breaking its consumers, verified by their contracts.
- [Reliable Integration](https://banes-lab.com/records/lexicon/reliable-integration.md): The degree to which systems integrate correctly because their shared meaning is agreed, not just their shape.
- [Rolling Upgrades](https://banes-lab.com/records/lexicon/rolling-upgrades.md): The ability to upgrade instances one at a time while old and new versions interoperate.
- [Schema Evolution](https://banes-lab.com/records/lexicon/schema-evolution.md): The ability to change a data schema over time without breaking existing readers or writers.
- [Consumer Safety](https://banes-lab.com/records/lexicon/consumer-safety.md): The degree to which consumers are protected from breakage when a provider changes.
- [Data Quality](https://banes-lab.com/records/lexicon/data-quality.md): The degree to which data is accurate, complete, and fit for its intended use.