# Schema / Canonical Data / Semantics > Every term in this category is listed as one record, with its kind, its definition and its aliases, the principles whose relations name it, the principle or… Page: Ontology · Lexicon Canonical: https://banes-lab.com/ontology/lexicon#lexicon-category-schema-canonical-data-semantics Listed in [Ontology · Lexicon](https://banes-lab.com/api/pages/ontology/lexicon.md), after [Scalability / Performance / Optimization](https://banes-lab.com/ontology/lexicon/lexicon-category-scalability-performance-optimization.md) and before [Security Privacy Compliance](https://banes-lab.com/ontology/lexicon/lexicon-category-security-privacy-compliance.md). Every term in this category is listed as one record, with its kind, its definition and its aliases, the principles whose relations name it, the principle or contract that carries the same name where one exists, and the layer its category belongs to. A tag category also gives each term an example, which is the file the tag places or the rename from a refused word onto a covering tag. ### Ambiguous API - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition An interface whose names and parameters hide what it does, so callers must guess or read the implementation. Referenced by [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md) Distinct from [Boolean Trap](https://banes-lab.com/records/architecture/boolean-trap.md): An ambiguous API hides what an interface does by any means, while a boolean trap is the case of boolean parameters hiding intent at the call site. How it is checked Checked by [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Ambiguous Encoding - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition Representing the same value in multiple encodings without normalizing, so equal values compare as different. Referenced by [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) How it is checked Checked by [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Bounded Context Autonomy - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which enforcing one canonical model limits each bounded context's freedom to model its own domain. Referenced by [Canonical Model](https://banes-lab.com/records/architecture/canonical-model.md) How it is checked Checked by the tension resolution with canonical-model Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Bounded Context Purity - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which sharing one enterprise data model erodes the conceptual purity of each bounded context. Referenced by [Canonical Data Model](https://banes-lab.com/records/architecture/canonical-data-model.md) Distinct from [Local Model Autonomy](https://banes-lab.com/records/lexicon/local-model-autonomy.md): Bounded context purity is each context's concepts staying clean, while local model autonomy is each context being free to evolve its own model. How it is checked Checked by the tension resolution with canonical-data-model Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Canonical Definition - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The requirement that each fact have one authoritative definition that all consumers reference. Referenced by [Single Source of Truth](https://banes-lab.com/records/architecture/single-source-of-truth.md) How it is checked Checked by [Single Source of Truth](https://banes-lab.com/records/architecture/single-source-of-truth.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Canonical Format - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The requirement that a single normalized form be defined for values before they are compared or stored. Referenced by [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) How it is checked Checked by [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Clear Semantics - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The requirement that an interface's names convey what each operation does and expects. Referenced by [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md) How it is checked Checked by [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Clever Abstractions - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which clever, non-obvious abstractions trade familiarity for surprise to the reader. Referenced by [Principle of Least Surprise](https://banes-lab.com/records/architecture/principle-of-least-surprise.md) How it is checked Checked by the tension resolution with principle-of-least-surprise Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Concise Naming - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which naming an interface fully for clarity works against keeping names short. Referenced by [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md), [Set-Relative Member Name](https://banes-lab.com/records/architecture/set-relative-member-name.md) How it is checked Checked by the tension resolution with intent-revealing-interface, [Set-Relative Member Name](https://banes-lab.com/records/architecture/set-relative-member-name.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Convention - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The requirement that a design follow established conventions so its behavior matches expectations. Referenced by [Principle of Least Surprise](https://banes-lab.com/records/architecture/principle-of-least-surprise.md) How it is checked Checked by [Principle of Least Surprise](https://banes-lab.com/records/architecture/principle-of-least-surprise.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Correct Usage - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The ability of callers to use an interface correctly because its names reveal its intent. Referenced by [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md) How it is checked Checked by [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Cross-Context Terminology - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which agreeing on shared terms strains against the distinct vocabularies different contexts need. Referenced by [Ubiquitous Language](https://banes-lab.com/records/architecture/ubiquitous-language.md) How it is checked Checked by the tension resolution with ubiquitous-language Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Cross-System Mapping - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The ability to map data between systems through a single shared canonical representation. Referenced by [Canonical Data Model](https://banes-lab.com/records/architecture/canonical-data-model.md) How it is checked Checked by [Canonical Data Model](https://banes-lab.com/records/architecture/canonical-data-model.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Data Semantics - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The requirement that the meaning and dependencies of data be understood before it is decomposed into relations. Referenced by [Normalization](https://banes-lab.com/records/architecture/normalization.md) How it is checked Checked by [Normalization](https://banes-lab.com/records/architecture/normalization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Deduplication - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The ability to recognize and collapse values that are equivalent once reduced to canonical form. Referenced by [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) How it is checked Checked by [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Denormalized Read Models - Kind: [pattern](https://banes-lab.com/records/kind/pattern.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition A read-optimized model that deliberately duplicates data to serve queries fast, trading storage and write cost for read speed. Referenced by [Normalization](https://banes-lab.com/records/architecture/normalization.md) How it is checked Checked by the tension resolution with normalization Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Disambiguation - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The ability to give each concept one unambiguous name and meaning across a domain. Referenced by [Semantic Consistency](https://banes-lab.com/records/architecture/semantic-consistency.md) How it is checked Checked by [Semantic Consistency](https://banes-lab.com/records/architecture/semantic-consistency.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Domain Collaboration - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The requirement that domain experts and developers collaborate to agree on shared terminology. Referenced by [Ubiquitous Language](https://banes-lab.com/records/architecture/ubiquitous-language.md) How it is checked Checked by [Ubiquitous Language](https://banes-lab.com/records/architecture/ubiquitous-language.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Duplicated Authority - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition Two or more places each claiming to own the same fact, so they drift and disagree over time. Referenced by [Single Source of Truth](https://banes-lab.com/records/architecture/single-source-of-truth.md), [Declared Jurisdiction](https://banes-lab.com/records/architecture/declared-jurisdiction.md), [Externally Resolved Slot](https://banes-lab.com/records/architecture/externally-resolved-slot.md) Distinct from [Claimed Foreign Tree](https://banes-lab.com/records/lexicon/claimed-foreign-tree.md): Duplicated authority is two owners for one fact, while a claimed foreign tree is governing names another runtime owns. Distinct from [Depth-Relief Container](https://banes-lab.com/records/lexicon/depth-relief-container.md): Duplicated authority is two owners for one fact, while a depth-relief container is a container declared to shorten a path. Distinct from [Magic Value](https://banes-lab.com/records/architecture/magic-value.md): Duplicated authority is two owning copies of a fact, while a magic value is a fact written as an unexplained literal, however many times. Distinct from [Ignore-List Silencing](https://banes-lab.com/records/lexicon/ignore-list-silencing.md): Duplicated authority is two owners for one fact, while ignore-list silencing removes a file from the taxonomy to hide a finding. How it is checked Checked by [Single Source of Truth](https://banes-lab.com/records/architecture/single-source-of-truth.md), [Declared Jurisdiction](https://banes-lab.com/records/architecture/declared-jurisdiction.md), [Externally Resolved Slot](https://banes-lab.com/records/architecture/externally-resolved-slot.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Duplicated Denormalized Columns - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The same fact copied into many columns and rows, so updates must touch every copy or leave them inconsistent. Referenced by [Database Normalization](https://banes-lab.com/records/architecture/database-normalization.md) How it is checked Checked by [Database Normalization](https://banes-lab.com/records/architecture/database-normalization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Dynamic Untyped Boundaries - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition Passing untyped values across module or service boundaries, so type errors surface only at runtime. Referenced by [Type Safety](https://banes-lab.com/records/architecture/type-safety.md) Distinct from [Stringly Typed Programming](https://banes-lab.com/records/architecture/stringly-typed-programming.md): Untyped boundaries pass untyped values between modules, while stringly typed programming encodes states and types as strings anywhere in the code. How it is checked Checked by [Type Safety](https://banes-lab.com/records/architecture/type-safety.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Explicit Types - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The requirement that values crossing a boundary carry explicit, declared types rather than open-ended ones. Referenced by [Type Safety](https://banes-lab.com/records/architecture/type-safety.md) How it is checked Checked by [Type Safety](https://banes-lab.com/records/architecture/type-safety.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Flexible Input - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which strictly validating every payload rejects the loosely-shaped input a caller might legitimately send. Referenced by [Schema Validation](https://banes-lab.com/records/architecture/schema-validation.md) How it is checked Checked by the tension resolution with schema-validation Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Functional Dependencies - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The requirement that the dependencies determining which attributes fix others be identified before decomposing a schema. Referenced by [Database Normalization](https://banes-lab.com/records/architecture/database-normalization.md) How it is checked Checked by [Database Normalization](https://banes-lab.com/records/architecture/database-normalization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Local Model Autonomy - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which a bounded context is free to define and evolve its own data model independently of a shared canonical one. Referenced by [Canonical Data Model](https://banes-lab.com/records/architecture/canonical-data-model.md) How it is checked Checked by the tension resolution with canonical-data-model Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Lossless Preservation - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which reducing values to a canonical form can discard distinctions the original preserved. Referenced by [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) How it is checked Checked by the tension resolution with canonicalization Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Multiple Competing Models - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition Several inconsistent models of the same concept coexisting, so translations between them drift and conflict. Referenced by [Canonical Model](https://banes-lab.com/records/architecture/canonical-model.md) How it is checked Checked by [Canonical Model](https://banes-lab.com/records/architecture/canonical-model.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Naming Consistency - Kind: [constraint](https://banes-lab.com/records/kind/constraint.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The requirement that names for the same concept be used consistently across an interface. Referenced by [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md), [Set-Relative Member Name](https://banes-lab.com/records/architecture/set-relative-member-name.md) Distinct from [Set-Relative Member Name](https://banes-lab.com/records/architecture/set-relative-member-name.md): Naming consistency is one name per concept across an interface, while a set-relative member name leaves out what its folder already says. Distinct from [Clear Semantics](https://banes-lab.com/records/lexicon/clear-semantics.md): Naming consistency is the same concept always getting the same name, while clear semantics is each name saying what the operation does. How it is checked Checked by [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md), [Set-Relative Member Name](https://banes-lab.com/records/architecture/set-relative-member-name.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Non-Redundant Storage - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The ability to store each fact once, so it cannot drift out of sync with copies and no update anomaly can arise. Aliases Update-Anomaly Elimination Referenced by [Database Normalization](https://banes-lab.com/records/architecture/database-normalization.md) How it is checked Checked by [Database Normalization](https://banes-lab.com/records/architecture/database-normalization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Normalized Translation - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The ability to translate between systems through one shared canonical form rather than many pairwise mappings. Referenced by [Canonical Model](https://banes-lab.com/records/architecture/canonical-model.md) How it is checked Checked by [Canonical Model](https://banes-lab.com/records/architecture/canonical-model.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Polysemy Across Contexts - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which one term legitimately carries different meanings in different bounded contexts. Referenced by [Semantic Consistency](https://banes-lab.com/records/architecture/semantic-consistency.md) How it is checked Checked by the tension resolution with semantic-consistency Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Query Performance - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which splitting data across normalized relations forces costly joins on read. Referenced by [Normalization](https://banes-lab.com/records/architecture/normalization.md) How it is checked Checked by the tension resolution with normalization Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Rapid Scripting - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which requiring explicit types slows the quick, exploratory coding that dynamic typing allows. Referenced by [Type Safety](https://banes-lab.com/records/architecture/type-safety.md) How it is checked Checked by the tension resolution with type-safety Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Read Performance - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which normalizing a schema into many relations forces joins that slow reads. Referenced by [Database Normalization](https://banes-lab.com/records/architecture/database-normalization.md) How it is checked Checked by the tension resolution with database-normalization Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Reduced Redundancy - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The ability to eliminate duplicated facts by referencing a single stored copy. Referenced by [Normalization](https://banes-lab.com/records/architecture/normalization.md) How it is checked Checked by [Normalization](https://banes-lab.com/records/architecture/normalization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Safe Use - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The ability to use an interface safely because it behaves the way its name and shape suggest. Referenced by [Principle of Least Surprise](https://banes-lab.com/records/architecture/principle-of-least-surprise.md) How it is checked Checked by [Principle of Least Surprise](https://banes-lab.com/records/architecture/principle-of-least-surprise.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Security Checks - Kind: [capability](https://banes-lab.com/records/kind/capability.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The ability to apply security checks reliably by first reducing input to one unambiguous form. Referenced by [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) How it is checked Checked by [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Service-Specific Schemas - Kind: [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition The degree to which a shared canonical schema competes with each service's need for its own tailored schema. Referenced by [Canonical Schema](https://banes-lab.com/records/architecture/canonical-schema.md) How it is checked Checked by the tension resolution with canonical-schema Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Technical/Domain Mismatch - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition Naming code in technical terms disconnected from the domain, so experts and developers talk past each other. Referenced by [Ubiquitous Language](https://banes-lab.com/records/architecture/ubiquitous-language.md) How it is checked Checked by [Ubiquitous Language](https://banes-lab.com/records/architecture/ubiquitous-language.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ### Untyped Payloads - Kind: [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - Category: [Schema / Canonical Data / Semantics](https://banes-lab.com/ontology/lexicon/lexicon-category-schema-canonical-data-semantics.md) - Layer: [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) Details Definition Accepting data at a boundary with no schema, so malformed or unexpected shapes flow in unchecked. Referenced by [Schema Validation](https://banes-lab.com/records/architecture/schema-validation.md) How it is checked Checked by [Schema Validation](https://banes-lab.com/records/architecture/schema-validation.md) Population The term's definition and every architecture edge that names the term Freshness A verdict stands until the definition, the term's kind or an edge that names it changes Refusal The resolution gate fails an edge that resolves to no term, and a definition that opens as another kind Observation The resolution validator's pass over every edge target and every definition opening Evidence Watched to fire and to accept: a suite plants a term no edge names, a dangling dependency and a second check home, and the bundled terms pass Authoritative side The term record, which every edge that names the term cites Depends on Not answered Shape it refuses Not answered ## Links to - [anti-pattern](https://banes-lab.com/records/kind/anti-pattern.md) - [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md) - [Intent-Revealing Interface](https://banes-lab.com/records/architecture/intent-revealing-interface.md) - [Boolean Trap](https://banes-lab.com/records/architecture/boolean-trap.md) - [Canonicalization](https://banes-lab.com/records/architecture/canonicalization.md) - [quality-attribute](https://banes-lab.com/records/kind/quality-attribute.md) - [Canonical Model](https://banes-lab.com/records/architecture/canonical-model.md) - [Canonical Data Model](https://banes-lab.com/records/architecture/canonical-data-model.md) - [Local Model Autonomy](https://banes-lab.com/records/lexicon/local-model-autonomy.md) - [constraint](https://banes-lab.com/records/kind/constraint.md) - [Single Source of Truth](https://banes-lab.com/records/architecture/single-source-of-truth.md) - [Principle of Least Surprise](https://banes-lab.com/records/architecture/principle-of-least-surprise.md) - [Set-Relative Member Name](https://banes-lab.com/records/architecture/set-relative-member-name.md) - [capability](https://banes-lab.com/records/kind/capability.md) - [Ubiquitous Language](https://banes-lab.com/records/architecture/ubiquitous-language.md) - [Normalization](https://banes-lab.com/records/architecture/normalization.md) - [pattern](https://banes-lab.com/records/kind/pattern.md) - [Semantic Consistency](https://banes-lab.com/records/architecture/semantic-consistency.md) - [Declared Jurisdiction](https://banes-lab.com/records/architecture/declared-jurisdiction.md) - [Externally Resolved Slot](https://banes-lab.com/records/architecture/externally-resolved-slot.md) - [Claimed Foreign Tree](https://banes-lab.com/records/lexicon/claimed-foreign-tree.md) - [Depth-Relief Container](https://banes-lab.com/records/lexicon/depth-relief-container.md) - [Magic Value](https://banes-lab.com/records/architecture/magic-value.md) - [Ignore-List Silencing](https://banes-lab.com/records/lexicon/ignore-list-silencing.md) - [Database Normalization](https://banes-lab.com/records/architecture/database-normalization.md) - [Type Safety](https://banes-lab.com/records/architecture/type-safety.md) - [Stringly Typed Programming](https://banes-lab.com/records/architecture/stringly-typed-programming.md) - [Schema Validation](https://banes-lab.com/records/architecture/schema-validation.md) - [Clear Semantics](https://banes-lab.com/records/lexicon/clear-semantics.md) - [Canonical Schema](https://banes-lab.com/records/architecture/canonical-schema.md)