leaf
Kind: domain-tier
Record: vocabulary:domain-tier-leaf
Canonical: Schema
A domain whose contracts carry a math type and a yield and run at no loop stage.
Listed in Controlled vocabularies, after process and before exempt.
Tier of
- Anti-Pattern Inversion
- Anti-Pattern Propagation Kernel
- Anti-Pattern Remediation Algebra
- Architecture Smell Record
- Anti-Pattern Rule Compiler
- Smell Taxonomy
- Anti-Pattern Relationship Record
- <Architecture Anti-Pattern>
- Document Truth Alignment
- Architectural Contract Kernel
- Responsibility Boundary
- Coupling Control
- Interface Contract
- Substitutability
- Canonical Data
- Domain Boundary
- Self-Description Manifest
- Runtime Discovery
- Extension Point
- Construction Boundary
- Structural Mediation
- Behavioral Dispatch
- Architectural Style Boundary
- Port Adapter
- Event Messaging
- Saga Compensation
- Transaction Boundary
- Idempotent Side Effect
- Deterministic Core
- Verification Fitness
- Error Boundary
- Resilience Control
- Recovery Deployment
- Observability Trace
- Causality Ordering
- Performance Scaling
- Cache Correctness
- Portability Environment
- Security Policy
- Control Plane
- Declarative Metaprogramming
- Streaming Dataflow
- RAG Knowledge Boundary
- Architecture Selection Meta-Algorithm
- Universal Architectural Concern Template
- Architectural Contract Algebra
- Manifest-Driven Documentation
- Consumer Config SSOT
- Finite State Machine
- Statecharts
- Petri Nets
- Queuing Theory
- Architectural Relationship Record
- Architecture Knowledge Graph
- Architectural Force Classification
- Dependency Closure
- Reinforcement Propagation
- Conflict and Tension Resolution
- Severity Policy
- Violation Detection
- Measurement Normalization
- Refactor Selection
- Enforcement Gate
- Architecture Assessment
- Modular Boundary Compliance
- Contract Compatibility
- Canonical Semantics
- Self-Description and Discovery
- Runtime Extensibility
- Pattern Selection
- Event and Messaging Consistency
- State and Transaction Safety
- Correctness Verification
- Resilience Policy
- Observability and Auditability
- Performance and Scalability
- Security Governance
- Architecture Evolution Governance
- Control Plane Coordination
- Metaprogramming Safety
- Model Lifecycle Governance
- Architectural Recommendation
- Architecture Fitness Function Generation
- Architecture Refactoring Roadmap
- Concept Cluster Extraction
- Architecture Decision Support
- Relationship Schema Validation
- Architecture Catalog Compiler
- Master Architecture Governance Kernel
- Architectural Relationship Algebra
- Constraints Over Shortcuts
- Forward Compatibility Over Backward Compatibility
- Fail-Fast Over Fallback
- Explicit Removal Over Deprecation
- Greenfield Over Legacy
- Single-Path Determinism Over Dual-Path
- Immediacy Over Deferring
- Mandatory Over Optional
- Now Over For-Now
- Observed Execution Over Unobserved
- Compression Over Repetition
- Approved Evolution Over Unapproved
- Enforced Feedback Over Ignored
- Single Owner Over Shared Ownership
- Bounded Lifetime Over Unbounded
- Enforced Symmetry Over Asymmetric Lifecycle
- Explicit Retention Over Implicit
- Structural Release Over Discipline
- Immutable Data Over Mutable State
- Errors As Language Over Silent Errors
- Explicit Invalidity Over Hidden
- Event Emission Over Parent Callbacks
- Monotonic Growth Over Retraction
- Semantic Addressing Over Location Addressing
- Ordinal Time Over Timestamps
- Homoiconicity Over Separation
- Bounded Complexity Over Unlimited
- Computed Health Over Metric Health
- Secret Store Over Hardcoded Secrets
- Boundary Validation Over Unvalidated Input
- Least Privilege Over Broad Privilege
- Config Externalization Over Env Fallback
- Profile-First Over Unmeasured Optimization
- Rule As Code Over Convention
- Design By Contract Over Implicit Contract
- Versioned Evolution Over Breaking Change
- Schema-Validated Boundary Over Untyped
- Atomic Boundary Over Partial Commit
- Saga Compensation Over Distributed 2PC
- Async Events Over Synchronous Cross-Boundary
- Observable Signals Over Opaque Runtime
- Injected Dependency Over Hidden
- Convention Discovery Over Hardcoded Wiring
- Declarative Config Over Imperative
- Anti-Corruption Layer Over Cross-Context Leak
- Injected Nondeterminism Over Hidden
- Pattern By Fit Over Speculative Pattern
- Cascade Layer Partition
- Token Source-of-Truth
- Type-Keyed Appearance
- Custom Type Registration
- Governed Construction Boundary
- Placement Isolation
- Assembly Composition
- Layer Fitness Enforcement
- Type-Migration Centralization
- CSS Type-Cascade Kernel