# Lexicon terms whose category is architecture-review-evolution-governance

> 89 records

This index as JSON: https://banes-lab.com/json/api/facets/lexicon/category/architecture-review-evolution-governance

## Entries

- [Ad-Hoc Design](https://banes-lab.com/records/lexicon/ad-hoc-design.md): Designing by improvisation with no deliberate structure or review, so the architecture accretes inconsistently.
- [Ad-Hoc Pattern Mixing](https://banes-lab.com/records/lexicon/ad-hoc-pattern-mixing.md): Combining unrelated design patterns arbitrarily with no coherent rationale, producing an inconsistent structure.
- [Analysis Overhead](https://banes-lab.com/records/lexicon/analysis-overhead.md): The degree to which analyzing the impact of every change before making it adds effort and slows delivery.
- [Architecture Criteria](https://banes-lab.com/records/lexicon/architecture-criteria.md): The requirement that explicit criteria define what a review judges an architecture against.
- [Architecture Drift](https://banes-lab.com/records/lexicon/architecture-drift.md): Gradual divergence of an implementation from its intended architecture as unreviewed changes accumulate.
- [Architecture Foundation](https://banes-lab.com/records/lexicon/architecture-foundation.md): The degree to which a system rests on a sound, deliberately designed architectural base rather than accreted structure.
- [Architecture Rules](https://banes-lab.com/records/lexicon/architecture-rules.md): The requirement that explicit, checkable rules govern how the architecture may be structured and evolved.
- [Assumption-Based Judgment](https://banes-lab.com/records/lexicon/assumption-based-judgment.md): Judging an architecture from untested assumptions instead of measured evidence, yielding unreliable conclusions.
- [Attribute Scenarios](https://banes-lab.com/records/lexicon/attribute-scenarios.md): A concrete scenario specifying how a quality attribute should hold under defined conditions and stimuli.
- [Automated Architecture Compliance](https://banes-lab.com/records/lexicon/automated-architecture-compliance.md): The ability to verify conformance to architectural rules automatically rather than by manual review.
- [Blind Change](https://banes-lab.com/records/lexicon/blind-change.md): Changing a system without analyzing what the change affects, so unintended consequences go unseen.
- [Change Safety](https://banes-lab.com/records/lexicon/change-safety.md): The degree to which a change can be made with confidence that its effects are understood and contained.
- [Clean Boundary Design](https://banes-lab.com/records/lexicon/clean-boundary-design.md): The ability to define clear component boundaries from the outset, free of legacy entanglement.
- [Competing Attributes](https://banes-lab.com/records/lexicon/competing-attributes.md): The degree to which improving one quality attribute forces a trade-off against another.
- [Consequences](https://banes-lab.com/records/lexicon/consequences.md): A recorded account of the trade-offs and downstream effects that follow from an architectural decision.
- [Continuous Improvement](https://banes-lab.com/records/lexicon/continuous-improvement.md): Iteratively refining a system's design in small, ongoing steps rather than in large infrequent overhauls.
- [Controlled Architecture Evolution](https://banes-lab.com/records/lexicon/controlled-architecture-evolution.md): The ability to let an architecture change over time within deliberate guardrails rather than drifting freely.
- [Criteria](https://banes-lab.com/records/lexicon/criteria.md): The requirement that explicit, agreed measures define how an assessment reaches its verdict.
- [Current State](https://banes-lab.com/records/lexicon/current-state.md): A conceptual representation of how a system is presently structured and behaves, used as the baseline for analysis.
- [Decision](https://banes-lab.com/records/lexicon/decision.md): A recorded architectural choice capturing what was chosen and the context in which it was made.
- [Decision History](https://banes-lab.com/records/lexicon/decision-history.md): The ability to trace why past architectural choices were made by consulting their recorded rationale.
- [Defect Detection](https://banes-lab.com/records/lexicon/defect-detection.md): The ability to find defects in a change before it is merged or shipped.
- [Design Criteria](https://banes-lab.com/records/lexicon/design-criteria.md): The requirement that explicit criteria define what a design review evaluates a proposal against.
- [Direct-to-main Unreviewed Change](https://banes-lab.com/records/lexicon/direct-to-main-unreviewed-change.md): Pushing changes straight to the main branch with no review, so unvetted code lands directly in production.
- [Documentation Maintenance](https://banes-lab.com/records/lexicon/documentation-maintenance.md): The degree to which keeping decision records current adds ongoing upkeep effort.
- [Early Defect Prevention](https://banes-lab.com/records/lexicon/early-defect-prevention.md): The ability to catch design flaws during review before they are built into the system.
- [Early Delivery with Guardrails](https://banes-lab.com/records/lexicon/early-delivery-with-guardrails.md): The ability to ship a minimal architecture quickly while keeping essential safeguards in place.
- [Easier Refactoring](https://banes-lab.com/records/lexicon/easier-refactoring.md): The ability to restructure code more safely because consistent patterns make change predictable.
- [Essential Quality Attributes](https://banes-lab.com/records/lexicon/essential-quality-attributes.md): The requirement that the few quality attributes critical to viability be satisfied before any others.
- [Fit-for-Purpose Architecture](https://banes-lab.com/records/lexicon/fit-for-purpose-architecture.md): The ability to shape an architecture to the problem it solves rather than to convention.
- [Future Scalability](https://banes-lab.com/records/lexicon/future-scalability.md): The degree to which a design can grow to meet higher future demand without rework.
- [Governance Discipline](https://banes-lab.com/records/lexicon/governance-discipline.md): The degree to which evolving an architecture continuously demands sustained governance to prevent uncontrolled drift.
- [Innovation/Autonomy](https://banes-lab.com/records/lexicon/innovation-autonomy.md): The degree to which enforcing standards constrains teams' freedom to innovate independently.
- [Legacy Constraints](https://banes-lab.com/records/lexicon/legacy-constraints.md): A binding limitation imposed by pre-existing legacy systems that a new design must accommodate.
- [Local Autonomy](https://banes-lab.com/records/lexicon/local-autonomy.md): The degree to which enforcing architectural consistency limits individual teams' freedom to make local choices.
- [Local Optimization](https://banes-lab.com/records/lexicon/local-optimization.md): The degree to which enforcing shared patterns sacrifices locally optimal one-off solutions.
- [Manual Architecture Review Only](https://banes-lab.com/records/lexicon/manual-architecture-review-only.md): Relying solely on human review to police architecture, with no automated checks, so violations slip through.
- [Measurable Architecture Rule](https://banes-lab.com/records/lexicon/measurable-architecture-rule.md): The requirement that an architectural rule be expressed as an objective, automatically checkable measure.
- [Naming/Structure Conventions](https://banes-lab.com/records/lexicon/naming-structure-conventions.md): A convention of naming and structuring code uniformly across a codebase so its shape is predictable.
- [Operability](https://banes-lab.com/records/lexicon/operability.md): The degree to which a system is easy to run, monitor, and keep healthy in production.
- [Predictable Evolution](https://banes-lab.com/records/lexicon/predictable-evolution.md): The ability to change a system with confidence that consistent structure keeps outcomes foreseeable.
- [Prioritized Refactoring](https://banes-lab.com/records/lexicon/prioritized-refactoring.md): The ability to rank refactoring work by assessed impact so effort targets the highest-value fixes.
- [Problem Decomposition](https://banes-lab.com/records/lexicon/problem-decomposition.md): Breaking a problem into fundamental sub-problems that can be reasoned about independently.
- [Quality](https://banes-lab.com/records/lexicon/quality.md): The degree to which a system meets its functional and non-functional expectations.
- [Quality Goals](https://banes-lab.com/records/lexicon/quality-goals.md): The requirement that target levels for key quality attributes be defined for an architecture to meet.
- [Regression Scope Selection](https://banes-lab.com/records/lexicon/regression-scope-selection.md): The ability to select exactly which tests a change requires by analyzing what it affects.
- [Remediation Planning](https://banes-lab.com/records/lexicon/remediation-planning.md): The ability to plan the steps that close the gap between a system's current and target states.
- [Reusable Architecture Guidance](https://banes-lab.com/records/lexicon/reusable-architecture-guidance.md): A body of proven architectural guidance packaged for reuse across projects.
- [Reuse of Established Patterns](https://banes-lab.com/records/lexicon/reuse-of-established-patterns.md): The degree to which designing from first principles forgoes the leverage of reusing proven patterns.
- [Review Standards](https://banes-lab.com/records/lexicon/review-standards.md): The requirement that agreed standards define what a code review checks for.
- [Risk Detection](https://banes-lab.com/records/lexicon/risk-detection.md): The ability to surface architectural risks early by reviewing structure before it is built.
- [Standard Patterns](https://banes-lab.com/records/lexicon/standard-patterns.md): A canonical, widely agreed reusable solution that a reference architecture prescribes for a recurring problem.
- [Standards Definition](https://banes-lab.com/records/lexicon/standards-definition.md): A defined, authoritative set of standards that units are expected to conform to.
- [Target State](https://banes-lab.com/records/lexicon/target-state.md): A conceptual representation of the desired future structure a system is being steered toward.
- [Trade-Off Analysis](https://banes-lab.com/records/lexicon/trade-off-analysis.md): The ability to weigh competing quality attributes and choose a balanced compromise between them.
- [Tribal Knowledge](https://banes-lab.com/records/lexicon/tribal-knowledge.md): Critical architectural knowledge held only in the developers' heads and never recorded, lost when they leave.
- [Uncoordinated Divergence](https://banes-lab.com/records/lexicon/uncoordinated-divergence.md): Teams independently diverging from a shared reference architecture, fragmenting the system into incompatible variants.
- [Unbounded Variation](https://banes-lab.com/records/lexicon/unbounded-variation.md): Allowing unlimited variation in how the same problem is solved, so the system sprawls into inconsistent one-offs.
- [Unknown Requirements](https://banes-lab.com/records/lexicon/unknown-requirements.md): The degree to which starting on a clean slate forces early decisions while requirements are still unknown.
- [Unreviewed Structural Change](https://banes-lab.com/records/lexicon/unreviewed-structural-change.md): Merging changes to architectural structure without review, letting unvetted design decisions into the system.
- [Incremental Change](https://banes-lab.com/records/lexicon/incremental-change.md): The requirement that a system evolve in small, reversible increments rather than large risky leaps.
- [Rule Maintenance](https://banes-lab.com/records/lexicon/rule-maintenance.md): The degree to which keeping fitness-function rules current adds ongoing upkeep effort.
- [Undefined Target](https://banes-lab.com/records/lexicon/undefined-target.md): Attempting to close a gap toward a goal that was never clearly defined, so progress cannot be judged.
- [Delete After Evidence](https://banes-lab.com/records/lexicon/delete-after-evidence.md): A technique for removing code once measurement shows nothing calls it.
- [Deprecation Plan](https://banes-lab.com/records/lexicon/deprecation-plan.md): A technique for recording for each obsolete path its owner, its replacement and its removal date.
- [Assign Owner](https://banes-lab.com/records/lexicon/assign-owner.md): A technique for recording a named owner for each module, risk or rule, who decides on its changes.
- [Severity Classification](https://banes-lab.com/records/lexicon/severity-classification.md): A technique for ranking each finding or risk on a declared scale that sets how soon it is handled.
- [Mitigation Plan](https://banes-lab.com/records/lexicon/mitigation-plan.md): A technique for recording the actions that reduce a risk, with an owner and a date for each.
- [Accepted Risk Record](https://banes-lab.com/records/lexicon/accepted-risk-record.md): A technique for recording a decision to accept a risk with who accepted it and when it is reviewed again.
- [Scheduled Review](https://banes-lab.com/records/lexicon/scheduled-review.md): A technique for setting a date on which a decision, risk or exception is examined again.
- [Risk Register](https://banes-lab.com/records/lexicon/risk-register.md): A technique for keeping every known risk in one list with its owner, severity, mitigation and review date.
- [Decision Record with Alternatives](https://banes-lab.com/records/lexicon/decision-record-with-alternatives.md): A technique for recording a decision together with the options rejected and the forces that decided it.
- [Force Analysis](https://banes-lab.com/records/lexicon/force-analysis.md): A technique for listing the pressures a design must balance before choosing a pattern for it.
- [Trade-Off Matrix](https://banes-lab.com/records/lexicon/trade-off-matrix.md): A technique for scoring candidate designs against the quality attributes that matter for the decision.
- [Quality Scenarios](https://banes-lab.com/records/lexicon/quality-scenarios.md): A technique for stating each quality attribute as a stimulus, a response and a measure the design must meet.
- [Decision Review](https://banes-lab.com/records/lexicon/decision-review.md): A technique for re-examining recorded decisions when the evidence behind them changes.
- [Vertical Slice Proof](https://banes-lab.com/records/lexicon/vertical-slice-proof.md): A technique for proving a design by building one end-to-end path through every layer before generalizing it.
- [Defer Generalization](https://banes-lab.com/records/lexicon/defer-generalization.md): A technique for keeping concrete code until a second real variation shows what the abstraction must cover.
- [Validate Required Forces](https://banes-lab.com/records/lexicon/validate-required-forces.md): A technique for checking that a pattern in use has the boundary rules and contracts the pattern requires.
- [Track Rule Metrics](https://banes-lab.com/records/lexicon/track-rule-metrics.md): A technique for counting violations of each architecture rule over time, so recurrence is visible.
- [Architecture Test](https://banes-lab.com/records/lexicon/architecture-test.md): A technique for expressing a structural rule, such as a dependency direction, as a test that runs in the build.
- [Remove Pattern Shell](https://banes-lab.com/records/lexicon/remove-pattern-shell.md): A technique for deleting the structure of a pattern whose forces are absent, leaving the plain code it wrapped.
- [Duplicate Until the Pattern Stabilizes](https://banes-lab.com/records/lexicon/duplicate-until-the-pattern-stabilizes.md): A technique for tolerating a small duplication until enough cases exist to show the shared shape.
- [Measure Delivery Cost](https://banes-lab.com/records/lexicon/measure-delivery-cost.md): A technique for measuring the time and effort an abstraction adds to delivering a change.
- [Anchor to Use Cases](https://banes-lab.com/records/lexicon/anchor-to-use-cases.md): A technique for justifying each component by a concrete use case it serves.
- [Contextual Pattern Selection](https://banes-lab.com/records/lexicon/contextual-pattern-selection.md): A technique for choosing a pattern by the forces of the problem at hand instead of by familiarity.
- [Dead Code Check](https://banes-lab.com/records/lexicon/dead-code-check.md): A technique for failing the build on exports and branches that nothing reaches.
- [Archive Reference](https://banes-lab.com/records/lexicon/archive-reference.md): A technique for keeping removed code reachable in history or an archive instead of in the live tree.
- [Inconsistent Conventions](https://banes-lab.com/records/lexicon/inconsistent-conventions.md): A defect in which parts of one project use different structures, formats, tools or patterns for the same kind of thing.