# The layer face

> 18 records.

This index as JSON: https://banes-lab.com/json/api/records/layer

## Entries

- [Atomic Boundary](https://banes-lab.com/records/layer/atomic-boundary.md): The rules governing atomicity — a transactional boundary that fully commits or fully rolls back, no partial commit, no deferring within.
- [Causality Core](https://banes-lab.com/records/layer/causality-core.md): The rules governing causal ordering and time — logical ordering, retractable state, no wall-clock dependence.
- [Computation Core](https://banes-lab.com/records/layer/computation-core.md): The rules governing computation determinism and purity — no mutable shared state, no hidden nondeterminism, reproducible results.
- [Contracts Core](https://banes-lab.com/records/layer/contracts-core.md): The rules governing interfaces and contracts — explicit typed boundaries, versioned change, no implicit or breaking contracts.
- [Correctness Core](https://banes-lab.com/records/layer/correctness-core.md): The rules ensuring behavioral correctness and validity — no silent failures, no hidden invalidity, feedback acted on, results observed.
- [Declarative Core](https://banes-lab.com/records/layer/declarative-core.md): The rules favoring declarative over imperative — declared configuration, separated concerns, no imperative wiring.
- [Design Patterns Core](https://banes-lab.com/records/layer/design-patterns-core.md): The rules governing design-pattern use — patterns applied only to demonstrated recurrence, no speculative pattern application.
- [Domain Modeling](https://banes-lab.com/records/layer/domain-modeling.md): The rules governing domain boundaries — bounded contexts, ubiquitous language, no leaky context.
- [Enforcement Core](https://banes-lab.com/records/layer/enforcement-core.md): The rules ensuring discipline is enforced programmatically — automated gates over convention, no discipline-only reliance.
- [Evolution Principles](https://banes-lab.com/records/layer/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'.
- [Execution Core](https://banes-lab.com/records/layer/execution-core.md): The rules governing execution flow — a single observable path, no deferring, no dual-path branching, nothing unobserved.
- [Extensibility Core](https://banes-lab.com/records/layer/extensibility-core.md): The rules governing extension — declarative discovered wiring over hardcoded, no imperative hardcoded registration.
- [Human Factors](https://banes-lab.com/records/layer/human-factors.md): The rules governing human ergonomics — bounded cognitive complexity, acted-on feedback, explicit approval, no unlimited options.
- [Observability](https://banes-lab.com/records/layer/observability.md): The rules ensuring a system is observable — emitted metrics and signals, no unobserved execution, no opaque runtime.
- [Performance Core](https://banes-lab.com/records/layer/performance-core.md): The rules governing performance discipline — measured optimization, planned capacity, no guesswork.
- [Resource Core](https://banes-lab.com/records/layer/resource-core.md): The rules governing resource lifecycle and ownership — bounded lifetime, single ownership, no leaks, no implicit retention.
- [Security Core](https://banes-lab.com/records/layer/security-core.md): The rules governing security posture — no hardcoded secrets, validated input, least privilege, no insecure fallbacks.
- [Structural Core](https://banes-lab.com/records/layer/structural-core.md): The architectural rules that preserve structural integrity — a single authoritative source, no shortcuts, no fallbacks, no duplication, no orphaned artifacts.