# The lex records whose kind is artifact

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

## Entries

- [Attribute Scenarios](https://banes-lab.com/records/lex/attribute-scenarios.md): A concrete scenario specifying how a quality attribute should hold under defined conditions and stimuli.
- [Consequences](https://banes-lab.com/records/lex/consequences.md): A recorded account of the trade-offs and downstream effects that follow from an architectural decision.
- [Decision](https://banes-lab.com/records/lex/decision.md): A recorded architectural choice capturing what was chosen and the context in which it was made.
- [Reusable Architecture Guidance](https://banes-lab.com/records/lex/reusable-architecture-guidance.md): A body of proven architectural guidance packaged for reuse across projects.
- [Standards Definition](https://banes-lab.com/records/lex/standards-definition.md): A defined, authoritative set of standards that units are expected to conform to.
- [Version Vector](https://banes-lab.com/records/lex/version-vector.md): A set of per-node counters that together capture the causal history of a replicated item.
- [Schema](https://banes-lab.com/records/lex/schema.md): A formal definition of the structure, types, and constraints of data.
- [Metadata](https://banes-lab.com/records/lex/metadata.md): Descriptive data about a system's structure, capabilities, or content, consumed to drive behavior.
- [Specification](https://banes-lab.com/records/lex/specification.md): A precise, authoritative description of required behavior, structure, or interface.
- [Context](https://banes-lab.com/records/lex/context.md): The surrounding information and circumstances captured to make a decision, event, or log entry interpretable.
- [Evidence](https://banes-lab.com/records/lex/evidence.md): Recorded proof that substantiates a claim, decision, or compliance requirement.
- [Type Metadata](https://banes-lab.com/records/lex/type-metadata.md): Descriptive data about the types of a structure's fields, available for inspection at runtime.
- [Formal Specification](https://banes-lab.com/records/lex/formal-specification.md): A precise, mathematical statement of what a system must do, against which it is proven.
- [Ruleset](https://banes-lab.com/records/lex/ruleset.md): The set of rules a static analyzer checks source code against.
- [Tests](https://banes-lab.com/records/lex/tests.md): Executable checks that assert a system behaves as intended.
- [Deduplication Key](https://banes-lab.com/records/lex/deduplication-key.md): A stable identifier attached to a message that lets a consumer detect and drop duplicates.
- [Event Schema](https://banes-lab.com/records/lex/event-schema.md): A formal definition of the structure and fields of an event's payload.
- [Events](https://banes-lab.com/records/lex/events.md): Records of things that have happened in a system, emitted for other components to react to.
- [Ordered Log](https://banes-lab.com/records/lex/ordered-log.md): An append-only sequence of records that preserves the order in which they were written.
- [Manifest](https://banes-lab.com/records/lex/manifest.md): A declarative document listing a component's capabilities and metadata.
- [Manifest Schema](https://banes-lab.com/records/lex/manifest-schema.md): A formal definition of the structure a manifest must follow.
- [Metadata Schema](https://banes-lab.com/records/lex/metadata-schema.md): A formal definition of the metadata fields that drive a system's behavior.
- [Runtime Type Metadata](https://banes-lab.com/records/lex/runtime-type-metadata.md): Type information retained at runtime so a program can inspect the shape of its own values.
- [Generated Implementations](https://banes-lab.com/records/lex/generated-implementations.md): Implementation code produced automatically from a model rather than written by hand.
- [Document Store](https://banes-lab.com/records/lex/document-store.md): The body of documents a retrieval system searches to ground a model's generation.
- [Dataset](https://banes-lab.com/records/lex/dataset.md): A curated collection of examples used to train or evaluate a model.
- [Embeddings](https://banes-lab.com/records/lex/embeddings.md): Numeric vector representations of data that place semantically similar items near each other.
- [Entities](https://banes-lab.com/records/lex/entities.md): The distinct things, such as people, places or concepts, that a knowledge graph represents as nodes.
- [Model Artifact](https://banes-lab.com/records/lex/model-artifact.md): The trained model file, with its learned weights, that is loaded to serve predictions.
- [Model Registry](https://banes-lab.com/records/lex/model-registry.md): A catalog that tracks model versions, their metadata, and their deployment status.
- [Rationale/Evidence](https://banes-lab.com/records/lex/rationale-evidence.md): The reasons and supporting evidence recorded for a model's decision.
- [Relations](https://banes-lab.com/records/lex/relations.md): The typed connections between entities that a knowledge graph represents as edges.
- [Schema/Ontology](https://banes-lab.com/records/lex/schema-ontology.md): A formal definition of the entity types and relationship types a knowledge graph may contain.
- [Vector Index](https://banes-lab.com/records/lex/vector-index.md): A data structure that organizes embedding vectors for fast nearest-neighbor lookup.
- [Structured, Versioned Prompts](https://banes-lab.com/records/lex/structured-versioned-prompts.md): Prompts authored as structured, version-controlled artifacts rather than ad-hoc strings.
- [Logs](https://banes-lab.com/records/lex/logs.md): A record of discrete, timestamped events a system emits about what it did.
- [Traces](https://banes-lab.com/records/lex/traces.md): A record of the path and timing of a request as it moves through a system's components.
- [Structured Events](https://banes-lab.com/records/lex/structured-events.md): Log entries emitted as structured, machine-parsable records rather than free-form text.
- [Action](https://banes-lab.com/records/lex/action.md): A field of an audit record identifying the operation that was performed.
- [Actor](https://banes-lab.com/records/lex/actor.md): A field of an audit record identifying who or what performed an action.
- [Target](https://banes-lab.com/records/lex/target.md): A field of an audit record identifying the resource an action was performed on.
- [Timestamp](https://banes-lab.com/records/lex/timestamp.md): A field of an audit record marking when an action occurred.
- [Logs/Traces](https://banes-lab.com/records/lex/logs-traces.md): The combined log and trace records that let a request be followed from end to end.
- [Audit Trail](https://banes-lab.com/records/lex/audit-trail.md): A chronological record linking each event to the one that caused it.
- [Event Metadata](https://banes-lab.com/records/lex/event-metadata.md): Descriptive fields attached to an event, such as its identifiers, timestamps, and causation links.
- [Image Definition](https://banes-lab.com/records/lex/image-definition.md): A declarative file specifying how a container image is built from a base and its dependencies.
- [Config Schema](https://banes-lab.com/records/lex/config-schema.md): A schema defining the structure, types, and defaults of a system's externalized configuration.
- [Bottleneck Evidence](https://banes-lab.com/records/lex/bottleneck-evidence.md): Measured data identifying which component constrains performance, justifying where to optimize.
- [Partition Key](https://banes-lab.com/records/lex/partition-key.md): The field whose value determines which shard or partition a record belongs to.
- [Assets](https://banes-lab.com/records/lex/assets.md): The data, systems, and capabilities of value that a threat model enumerates as the things worth protecting.
- [Attribute Definitions](https://banes-lab.com/records/lex/attribute-definitions.md): Declared descriptions of the subject, resource, action, and environment attributes that an access policy evaluates.
- [Identity Proof](https://banes-lab.com/records/lex/identity-proof.md): The evidence a principal presents to establish its identity, such as a password, token, or certificate.
- [Machine-Readable Policies](https://banes-lab.com/records/lex/machine-readable-policies.md): Security or compliance policies expressed in a structured, executable format that tools can evaluate directly.
- [Role Definitions](https://banes-lab.com/records/lex/role-definitions.md): Declared sets of permissions grouped into named roles that are assigned to principals.
- [Secret Store](https://banes-lab.com/records/lex/secret-store.md): A dedicated, access-controlled repository that holds credentials and keys outside of application code.
- [Threat Scenarios](https://banes-lab.com/records/lex/threat-scenarios.md): Concrete descriptions of how an attacker might attempt to compromise a system, enumerated during threat modeling.
- [Health Signal](https://banes-lab.com/records/lex/health-signal.md): A machine-readable signal that reports whether a component is currently healthy.
- [Detection Signal](https://banes-lab.com/records/lex/detection-signal.md): A machine-readable signal indicating that a fault or anomaly has been detected.
- [Versioned Artifact](https://banes-lab.com/records/lex/versioned-artifact.md): A build artifact tagged with a distinct version so a prior one can be redeployed.
- [Event Time](https://banes-lab.com/records/lex/event-time.md): The time at which an event occurred, carried on the event and used to assign it to a window.
- [Concern Tag](https://banes-lab.com/records/lex/concern-tag.md): A formal definition of the role a file plays, drawn from the closed concern vocabulary and carried as the last dot-segment before the extension.
- [Ignore Declaration](https://banes-lab.com/records/lex/ignore-declaration.md): Descriptive data about the names skipped wherever they appear under a governed root, covering build output, vendored sources, tool caches and ecosystem-fixed names.
- [Collection Concern](https://banes-lab.com/records/lex/collection-concern.md): A formal definition of a concern whose file defines many members at once, plural in both the folder label and the file tag.
- [Single-Unit Concern](https://banes-lab.com/records/lex/single-unit-concern.md): A formal definition of a concern with one instance per file, pairing a plural folder label with a singular file tag.
- [Rejection Table](https://banes-lab.com/records/lex/rejection-table.md): A formal definition of each near-miss word already considered and refused, recording the meta concern that covers it so the same word is not proposed twice.
- [Covering Concern](https://banes-lab.com/records/lex/covering-concern.md): A formal definition of the declared word that already fills a proposed word's role, resolved from the rejection table so a refusal carries its own replacement.
- [Version Field](https://banes-lab.com/records/lex/version-field.md): A field on a record whose value changes on each write, used to detect concurrent modification.