# The algo records whose domain is Architectural Clusters

This index as JSON: https://banes-lab.com/json/api/facets/algo/domain/architectural-clusters

## Entries

- [Structural Core](https://banes-lab.com/records/algo/structural-core.md): The architectural rules that preserve structural integrity — a single authoritative source, no shortcuts, no fallbacks, no duplication, no orphaned artifacts.
- [Correctness Core](https://banes-lab.com/records/algo/correctness-core.md): The rules ensuring behavioral correctness and validity — no silent failures, no hidden invalidity, feedback acted on, results observed.
- [Evolution Principles](https://banes-lab.com/records/algo/evolution-principles.md): The rules governing how a system changes over time — no backward-compat cruft, no deprecation debt, no legacy retention, no 'for now'.
- [Resource Core](https://banes-lab.com/records/algo/resource-core.md): The rules governing resource lifecycle and ownership — bounded lifetime, single ownership, no leaks, no implicit retention.
- [Execution Core](https://banes-lab.com/records/algo/execution-core.md): The rules governing execution flow — a single observable path, no deferring, no dual-path branching, nothing unobserved.
- [Computation Core](https://banes-lab.com/records/algo/computation-core.md): The rules governing computation determinism and purity — no mutable shared state, no hidden nondeterminism, reproducible results.
- [Security Core](https://banes-lab.com/records/algo/security-core.md): The rules governing security posture — no hardcoded secrets, validated input, least privilege, no insecure fallbacks.
- [Performance Core](https://banes-lab.com/records/algo/performance-core.md): The rules governing performance discipline — measured optimization, planned capacity, no guesswork.
- [Contracts Core](https://banes-lab.com/records/algo/contracts-core.md): The rules governing interfaces and contracts — explicit typed boundaries, versioned change, no implicit or breaking contracts.
- [Causality Core](https://banes-lab.com/records/algo/causality-core.md): The rules governing causal ordering and time — logical ordering, retractable state, no wall-clock dependence.
- [Declarative Core](https://banes-lab.com/records/algo/declarative-core.md): The rules favoring declarative over imperative — declared configuration, separated concerns, no imperative wiring.
- [Extensibility Core](https://banes-lab.com/records/algo/extensibility-core.md): The rules governing extension — declarative discovered wiring over hardcoded, no imperative hardcoded registration.
- [Observability](https://banes-lab.com/records/algo/observability.md): The rules ensuring a system is observable — emitted metrics and signals, no unobserved execution, no opaque runtime.
- [Enforcement Core](https://banes-lab.com/records/algo/enforcement-core.md): The rules ensuring discipline is enforced programmatically — automated gates over convention, no discipline-only reliance.
- [Atomic Boundary](https://banes-lab.com/records/algo/atomic-boundary.md): The rules governing atomicity — a transactional boundary that fully commits or fully rolls back, no partial commit, no deferring within.
- [Human Factors](https://banes-lab.com/records/algo/human-factors.md): The rules governing human ergonomics — bounded cognitive complexity, acted-on feedback, explicit approval, no unlimited options.
- [Domain Modeling](https://banes-lab.com/records/algo/domain-modeling.md): The rules governing domain boundaries — bounded contexts, ubiquitous language, no leaky context.
- [Design Patterns Core](https://banes-lab.com/records/algo/design-patterns-core.md): The rules governing design-pattern use — patterns applied only to demonstrated recurrence, no speculative pattern application.
- [State Pattern](https://banes-lab.com/records/algo/state-pattern.md): The State design pattern — encapsulate state-dependent behavior in distinct state objects so transitions replace conditional branching.
- [Separation of Concerns](https://banes-lab.com/records/algo/separation-of-concerns.md): The principle of separating a system into distinct concerns so each is addressed and changed independently.
- [Concurrency Correctness](https://banes-lab.com/records/algo/concurrency-correctness.md): The rules ensuring correct concurrent behavior — no data races, well-defined interleavings, verified with models such as Petri nets.
- [Capacity Planning](https://banes-lab.com/records/algo/capacity-planning.md): The activity of forecasting resource demand and provisioning capacity to meet it, informed by queuing theory.