# The algo records whose force is architecture_evolution

This index as JSON: https://banes-lab.com/json/api/facets/algo/force/architecture-evolution

## Entries

- [DSL Compliance Loading](https://banes-lab.com/records/algo/dsl-compliance-loading.md): Load grammar, keyword, operator, workflow, and checklist references before workflow generation, then require generated content to follow the declared DSL, naming, handoff, execution, forking, spawning, and capability rules.
- [Checklist Integration](https://banes-lab.com/records/algo/checklist-integration.md): Create a workflow progress checklist in the artifact workspace, include execution model metadata, phases in linear dependency order with severity metadata, task checkboxes, progress bars, success criteria, and agent-edit coordination rules.
- [Template Assembly](https://banes-lab.com/records/algo/template-assembly.md): Assemble frontmatter, workspace config, overview, phase documentation, checklist requirements, orchestration protocol, handoff format, coordination sequence, capability integration, workflow principles, and domain notes into one workflow artifact.
- [Workflow Validation Gate](https://banes-lab.com/records/algo/workflow-validation-gate.md): Validate DSL compliance, workspace discovery, dynamic agent count, execution classification, context configuration, 4D graphs, handoff protocol, hybrid execution, checklist integration, capability integration, template assembly, dynamic paths, uppercase filenames, and agent-oriented content.
- [Workflow Creation Kernel](https://banes-lab.com/records/algo/workflow-creation-kernel.md): Load DSL and orchestration references, configure file recovery and context forking, discover workspace zones and agents, select shared documents, define dynamic agent sequence, classify execution mode, build 4D graphs, define handoff protocol, assemble coordination sequence, integrate checklist and capabilities, generate phase documentation, assemble template, and validate success criteria.
- [<Workflow Orchestration Concern>](https://banes-lab.com/records/algo/workflow-orchestration-concern.md): <Load orchestration grammar> → <Discover workspace config> → <Select shared documents> → <Define agents> → <Classify parallel vs sequential> → <Fork discovery contexts> → <Serialize action phases> → <Build 4D graphs> → <Create handoff protocol> → <Coordinate shared-document refinement> → <Integrate checklist and capabilities> → <Validate template>
- [Anti-Pattern Relationship Record](https://banes-lab.com/records/algo/anti-pattern-relationship-record.md): Model every anti-pattern as a typed relationship record: name, scope, causal links, conflicts, degradations, enabled failures, detection signals, measurement, remediation inverse, prevention, and severity.
- [Architecture Knowledge Graph](https://banes-lab.com/records/algo/architecture-knowledge-graph.md): Parse all relationship records into a directed multigraph where concepts are nodes and fields such as requires, reinforces, enables, conflicts, tensions, detects, measures, refactors, and enforces are typed edges.
- [Architectural Force Classification](https://banes-lab.com/records/algo/architectural-force-classification.md): Given a design issue or desired quality, classify it into a force family, then select all concepts whose scope, type, violation signals, and enabled capabilities match that force.
- [Dependency Closure](https://banes-lab.com/records/algo/dependency-closure.md): For any target architectural concept, recursively collect its required concepts until no new requirements remain, then order the closure by dependency depth before implementation.
- [Reinforcement Propagation](https://banes-lab.com/records/algo/reinforcement-propagation.md): When a concept is implemented or strengthened, traverse its reinforces and enables edges to identify secondary quality gains and architecture capabilities unlocked.
- [Enforcement Gate](https://banes-lab.com/records/algo/enforcement-gate.md): Translate each concept’s enforced_by field into static checks, contract tests, schema validation, CI gates, policy rules, runtime monitors, review gates, or architecture fitness functions.
- [Architecture Assessment](https://banes-lab.com/records/algo/architecture-assessment.md): Select concepts relevant to a target scope, compute dependency closure, detect violations, measure evidence, rank findings by severity, and emit a prioritized architecture assessment.
- [Contract Compatibility](https://banes-lab.com/records/algo/contract-compatibility.md): For APIs, services, data, schemas, and protocols, validate explicit contracts, preconditions, postconditions, invariants, versioning, backward compatibility, forward compatibility, and interoperability.
- [Architecture Evolution Governance](https://banes-lab.com/records/algo/architecture-evolution-governance.md): Assess architecture against quality attributes, document decisions, analyze impact, track gaps, define fitness functions, standardize patterns, and evolve through ADR-backed controlled change.
- [Architectural Recommendation](https://banes-lab.com/records/algo/architectural-recommendation.md): Given a target problem, query the graph for matching violated_by and detected_by signals, collect candidate concepts, compute required dependencies, remove conflicting concepts, rank by severity and reinforcement gain, then recommend an ordered implementation path.
- [Architecture Fitness Function Generation](https://banes-lab.com/records/algo/architecture-fitness-function-generation.md): Convert mandatory and high-impact recommended records into executable fitness functions by binding detected_by signals to checks, measured_by fields to thresholds, and enforced_by fields to pipeline gates.
- [Concept Cluster Extraction](https://banes-lab.com/records/algo/concept-cluster-extraction.md): Group concepts into clusters by mutual requires, reinforces, enables, and shared scope; treat clusters as higher-order architectural concerns.
- [Architecture Decision Support](https://banes-lab.com/records/algo/architecture-decision-support.md): For each proposed design decision, compute satisfied concepts, violated concepts, tensions introduced, conflicts triggered, enabled capabilities, and enforcement cost; require ADR when trade-offs are nontrivial.
- [Master Architecture Governance Kernel](https://banes-lab.com/records/algo/master-architecture-governance-kernel.md): Parse the catalog, validate records, build the graph, classify target scope, select relevant concept clusters, compute dependency closure, detect violations, measure evidence, resolve conflicts, generate refactor plans, enforce gates, and record decisions.
- [Architectural Relationship Algebra](https://banes-lab.com/records/algo/architectural-relationship-algebra.md): <Parse concept records> → <Build relationship graph> → <Classify design force> → <Select applicable concepts> → <Resolve prerequisites> → <Detect violations> → <Measure evidence> → <Choose refactors> → <Enforce gates> → <Govern evolution>
- [Verification Fitness](https://banes-lab.com/records/algo/verification-fitness.md): Define executable architecture rules, validate with static analysis, specification tests, property tests, and runtime checks, then block release when critical rules fail.
- [Governance Evolution](https://banes-lab.com/records/algo/governance-evolution.md): Assess architecture against quality attributes, record decisions, analyze impact, enforce standards with fitness functions, and evolve through documented change.
- [Universal Architectural Concern Template](https://banes-lab.com/records/algo/universal-architectural-concern-template.md): For any architectural concern, define its intent, boundary, contract, invariants, allowed variation, forbidden leakage, validation strategy, observability model, and evolution policy.
- [Architectural Contract Algebra](https://banes-lab.com/records/algo/architectural-contract-algebra.md): <Classify architectural force> → <Declare boundary> → <Define contract> → <Choose pattern> → <Bind implementation> → <Verify invariant> → <Observe runtime> → <Govern evolution>
- [Centralized Reference Resolver](https://banes-lab.com/records/algo/centralized-reference-resolver.md): Group duplicated hardcoded references, derive resolver names, define scope-safe resolution rules, provide configuration override fallback, and map each old reference to a resolver migration.
- [Entry Point Migration](https://banes-lab.com/records/algo/entry-point-migration.md): Locate composition roots, identify manual registrations and hardcoded references, compose updates that use discovery registries and centralized resolvers, and apply only in implementation mode.
- [Knowledge Capture](https://banes-lab.com/records/algo/knowledge-capture.md): Load or initialize the automation knowledge base, merge new detections, conventions, scalability concerns, architecture designs, migration history, and validation outcomes, then persist when capability exists.
- [Detection Registry](https://banes-lab.com/records/algo/detection-registry.md): For every discovered occurrence, record resource, location, local context, matched pattern, extracted value, occurrence role, variation type, and discovery iteration.
- [Migration Action Mapping](https://banes-lab.com/records/algo/migration-action-mapping.md): Convert every detection-registry occurrence into an explicit migration action, including old content, replacement strategy, skip policy, and justification requirement.
- [Rollback-Centered Execution](https://banes-lab.com/records/algo/rollback-centered-execution.md): Before each destructive or high-risk phase, create a checkpoint, execute actions, verify results, and roll back immediately on critical action or verification failure.
- [Centralization Kernel](https://banes-lab.com/records/algo/centralization-kernel.md): Initialize runtime context, classify the target pattern, gather research, discover all variations, analyze architecture, build a refactor plan, optionally execute migration, validate zero duplication, and report status.
- [<Centralization Concern>](https://banes-lab.com/records/algo/centralization-concern.md): <Detect context> → <Classify pattern> → <Discover all occurrences and variants> → <Choose canonical source> → <Map migration> → <Gate execution> → <Validate zero debt> → <Report evidence>
- [Teleological Intent Gate](https://banes-lab.com/records/algo/teleological-intent-gate.md): Resolve what the checklist is for before planning it: enumerate the admissible decomposition branches, score each by utility minus cost against the normalized intent and change relation, and gate on the highest-worth admissible branch before any seeing or deriving.
- [Planning Stage](https://banes-lab.com/records/algo/planning-stage.md): Activate the principles that govern the current decision surfaces, select protocols by semantic fit against the requested transition, decompose them into phases, build the four-dimensional graph, and linearize the phases by dependency.
- [Principle Activation](https://banes-lab.com/records/algo/principle-activation.md): Test each principle in the ontology catalog against the current decision surfaces, mark it applies, uncertain, or not-applicable with a reason, and bind every applied principle to a decision test, a validator, and a severity that later routes its repair.
- [Phase Decomposition](https://banes-lab.com/records/algo/phase-decomposition.md): Expand each selected protocol's verb chain into phases, and annotate every phase with an id, verb, objective, preconditions, inputs, outputs, affected artifacts, local principles, severity, loop class, and a four-dimensional graph.
- [Four-Dimensional Phase Graph](https://banes-lab.com/records/algo/four-dimensional-phase-graph.md): For every phase, model the sequential dependency axis, the lateral independent-peer axis, the diagonal shared-data axis, and the propagation axis carrying superseded state, propagated contracts, and what breaks if the edge is omitted.
- [Severity Assignment](https://banes-lab.com/records/algo/severity-assignment.md): Derive each phase's severity from the worst severity of its governing principles; severity is per-phase metadata that selects the repair route, while execution order stays linear by dependency.
- [Compilation Stage](https://banes-lab.com/records/algo/compilation-stage.md): Compile each phase into atomic, target-specific tasks under binding codebase-pattern execution constraints, attach a full nine-dimension named ripple chain to every task, and number the hierarchy N.N.N.
- [Codebase Pattern Enforcement](https://banes-lab.com/records/algo/codebase-pattern-enforcement.md): Bind every emitted step to the required architecture pattern for its concern — factory construction, dependency injection, registry discovery, event emission, ports and adapters, contract-first boundaries, encapsulation, structured observability, bounded complexity, secrets management, input validation, least privilege, config externalization, fail-fast, legacy elimination, and enforcement authoring — rewriting each forbidden form into its required form.
- [Ripple Chain Analysis](https://banes-lab.com/records/algo/ripple-chain-analysis.md): Analyze each task across nine impact dimensions — registry, contracts, persistence, security, infrastructure, performance, observability, enforcement, and consumers — and record every named downstream effect with its consequence-if-omitted rather than a count, retaining an empty dimension with explicit applicability evidence.
- [Cross-Cutting Surface Coverage](https://banes-lab.com/records/algo/cross-cutting-surface-coverage.md): Gate the software surface beyond structure — security, performance, infrastructure and deployment, and resilience — so a change's threat, budget, config, and failure consequences are covered, not only its structural ones.
- [Legacy Elimination](https://banes-lab.com/records/algo/legacy-elimination.md): For any change that touches a replaced, deprecated, dual-path, or fallback code path, delete the superseded path and its orphaned exports in the same completed change so exactly one forward path remains.
- [Hierarchical Numbering](https://banes-lab.com/records/algo/hierarchical-numbering.md): Render addressable coordinates — Phase N, Task N.N, Subtask N.N.N — assigned only after the phase order is stable.
- [Admissibility Constraint Gate](https://banes-lab.com/records/algo/admissibility-constraint-stage.md): Gate the formalised plan on teleological admissibility before verification: sum the realised cost, compare it to the selected branch's budget and hard limits, and confirm every task traces to the selected branch — an over-budget, limit-breaching, or off-branch plan is inadmissible and routes back rather than being silently accepted.
- [Semantic Debt Policy](https://banes-lab.com/records/algo/semantic-debt-policy.md): Classify the relation a task holds to each controlled debt concept — backward-compatibility path, failure-masking fallback, deprecated or dual production path, deferred required work, shortcut debt, and unsupported superlative claim — blocking only the introduce and retain relations while allowing mention, analysis, quotation, and removal.
- [Validation Suite Battery](https://banes-lab.com/records/algo/validation-suite-battery.md): Run the governance validation suites over the generated context, phases, tasks, and claims — state integrity, authority, principle activation, plan graph, tasks, ripple, semantic policy, evidence, and output serializability — and emit findings that each name what was examined and carry an owner stage.
- [Rendering Stage](https://banes-lab.com/records/algo/rendering-stage.md): Serialize only validated records into the checklist deterministically, or render the blocked report, emitting exactly one terminal — success or blocked — with future execution checkboxes left unchecked, and stop within the cycle bound.
- [Checklist Output Rendering](https://banes-lab.com/records/algo/checklist-output-rendering.md): Emit the markdown checklist — governing context, principle disposition, phases in Z-topological order with loop class, severity, four-dimensional graph, and named ripple chains, hierarchically numbered tasks with evidence contracts, per-phase execution gates, appendices, and a final blocking execution gate — all left unchecked for future execution.
- [Cross-Stage Invariants](https://banes-lab.com/records/algo/cross-stage-invariants.md): Bind every stage to the always-and-never rules of the generator — resolve authority and directionality before planning, discover before assuming, activate principles with a bound validator, order by dependency with severity as routing metadata, read only the prior stage's output contract through one evidence-bearing handoff, represent all four graph axes, require evidence for every claim, separate generation gates from future execution gates, repair from the earliest invalid stage, and render deterministically.
- [Checklist Creation Kernel](https://banes-lab.com/records/algo/checklist-creation-kernel.md): Run the six-stage generator in order — orientation, planning, compilation, validation, repair, and rendering — bound by the cross-stage invariants, compiling a task description into a validated, dependency-aware execution checklist or an evidence-bearing blocked report.
- [<Checklist Governance Concern>](https://banes-lab.com/records/algo/checklist-governance-concern.md): <Orient on authority + evidence> → <Plan principles + protocols + dependency graph> → <Compile atomic tasks + ripple chains> → <Validate reasoning by evidence + semantic policy> → <Repair from the earliest invalid stage> → <Render one bounded terminal>
- [Naming Convention Remediation](https://banes-lab.com/records/algo/naming-convention-remediation.md): Compare file, folder, class, or symbol names against naming rules, derive compliant names, rename artifacts, and update all references.
- [Layer Fitness Enforcement](https://banes-lab.com/records/algo/layer-fitness-enforcement.md): Bind each layer invariant to a machine check — layer order declared once, placement properties barred from globals, class selectors barred from globals, literals barred where a token exists, no horizontal margin, all DOM through the factory, no inline style — run them as hard errors with no warn tier and no inline disables, and gate the push on a clean verdict.
- [Type-Migration Centralization](https://banes-lab.com/records/algo/type-migration-centralization.md): To move an existing purpose-class or page-scoped stylesheet into this model, treat every appearance-bearing class rule as a migration unit, derive the element type it decorates, register a custom `data-el` type when no tag or variant expresses it, move its look, size, and spacing into one global rule keyed by that type, demote any residual position into components and any residual layout into app, and verify that zero appearance rule keyed by a purpose-class remains outside the globals layer.
- [CSS Type-Cascade Kernel](https://banes-lab.com/records/algo/css-type-cascade-concern.md): Declare one layer order, hold every value in tokens, key every appearance on a type — native or custom-registered — exactly once in globals, hold placement in components and assembly in app, create all DOM through a factory that stamps types and refuses inline style, and gate the whole contract behind machine fitness functions.
- [Version Provenance](https://banes-lab.com/records/algo/version-provenance.md): Specializing Governance Evolution, detect whether the merge changed state, and only on real change bump the version, timestamp it, and append a modification record — leaving a no-op untouched.
- [Analysis Workspace](https://banes-lab.com/records/algo/analysis-workspace.md): Create a unique analysis session, allocate phase/metric/migration artifact locations, load baseline documentation and registries, write a manifest, and block continuation if required context is unavailable.
- [Fractal Scale Duplication](https://banes-lab.com/records/algo/fractal-scale-duplication.md): Test whether a duplication shape recurs at more than one scale (method, class, module), and determine the scale at which the abstraction belongs, so single-scale scanning does not abstract at the wrong level.
- [Migration Ordering](https://banes-lab.com/records/algo/migration-ordering.md): Sort target classes by complexity from lowest to highest, migrate simpler implementations first, and use early migrations to validate the abstraction before complex adoption.
- [Backup-Verified Migration](https://banes-lab.com/records/algo/backup-verified-migration.md): For each target class, create a recoverable checkpoint, refactor it to extend or use the abstraction, verify the removed anti-pattern no longer exists, and restore from backup on failure.
- [Anti-Pattern Elimination Verification](https://banes-lab.com/records/algo/anti-pattern-elimination-verification.md): After migration, search the entire target scope for old duplicate patterns, allow only approved base-location occurrences, and fail completion if unapproved duplicates remain.
- [Anti-Reintroduction Gate](https://banes-lab.com/records/algo/anti-reintroduction-gate.md): After eliminating an anti-pattern, author or strengthen the custom lint rule that statically forbids its reintroduction and any bypass of the new base, build the rule plugin, and regenerate the rule catalog, so the distilled boundary is enforced by a gate rather than by discipline.
- [Distillation Metrics](https://banes-lab.com/records/algo/distillation-metrics.md): Calculate duplication reduction, code reduction, adoption rate, lines saved, maintenance burden reduction, and cognitive-load reduction after migration.
- [Completion Truthfulness](https://banes-lab.com/records/algo/pattern-distillation-completion-truthfulness.md): Mark pattern distillation complete only if workspace, baseline, semantic analysis, anti-pattern classification, abstraction selection, migration, verification, registry update, anti-reintroduction gate, and metrics logging all pass.
- [Taxonomy Jurisdiction](https://banes-lab.com/records/algo/taxonomy-jurisdiction.md): Read the registry's root, container, bucket and ignore declarations, enumerate every file under a declared root, and separate the governed set from the ignored set and from the folders declared as neither, so jurisdiction is read rather than inferred.
- [Reshape Risk Priority](https://banes-lab.com/records/algo/reshape-risk-priority.md): Score each governed container by how much reference surface a rename disturbs — importer count and the number of surfaces that resolve by pattern rather than by literal path — and rank ascending, so the pilot is the lowest-risk container and the highest-risk one lands last.
- [Container Reshape](https://banes-lab.com/records/algo/container-reshape.md): Convert one container at a time: split the multi-role files first, move and rename each remaining file to its projected name and folder, update every importer in the same pass, move the mirrored tests to match the new concern folders, and re-point every surface whose pattern encoded the old form.
- [Taxonomy Ledger](https://banes-lab.com/records/algo/taxonomy-ledger.md): Record the registry version, the conversion state of each container, and every admitted and refused word with its reasoning, so the taxonomy's history is durable evidence rather than a fact re-derived from the tree on each pass.
- [Taxonomy Kernel](https://banes-lab.com/records/algo/taxonomy-kernel.md): Resolve jurisdiction from the registry, order the containers by reshape risk, walk each path into its ordered roles, classify each file to its narrowest concern, project the name and the folder chain together, reshape one container at a time, hold every proposed word at the admission gate, verify that pattern-resolved surfaces still collect what they collected, ledger the state, and terminate only when no residual finding remains.
- [Coverage Ledger](https://banes-lab.com/records/algo/coverage-ledger.md): Record each surface's verdict in a durable coverage ledger together with the residual uncovered and unknown set, so coverage state is reusable evidence rather than a fact re-derived on every run.
- [Test Coverage Kernel](https://banes-lab.com/records/algo/test-coverage-kernel.md): Load the surface catalog for a unit, walk the dimension-by-lens grid, derive the required-uncovered surfaces, prioritise them by risk, select a mode-matched technique and invariant per surface, author the test, issue an evidence verdict, ledger the state, and terminate only when no required surface remains unknown.