# The invariants

> Each invariant the test surfaces assert is listed with the surfaces that assert it.

Page: Ontology · Reasoning
Canonical: https://banes-lab.com/ontology/reasoning#the-invariants

Each invariant the test surfaces assert is listed with the surfaces that assert it.

### correct-outputs

Details

Invariant
Outputs are correct

Surfaces
[semantic-correctness](https://banes-lab.com/records/reason/test-surface-semantic-correctness.md), [data-correctness](https://banes-lab.com/records/reason/test-surface-data-correctness.md)

### correct-state-evolution

Details

Invariant
State evolves correctly

Surfaces
[functional-correctness](https://banes-lab.com/records/reason/test-surface-functional-correctness.md)

### valid-state-transitions

Details

Invariant
State transitions are valid

Surfaces
[state-correctness](https://banes-lab.com/records/reason/test-surface-state-correctness.md)

### correct-interactions

Details

Invariant
Interactions between components are correct

Surfaces
[interaction-correctness](https://banes-lab.com/records/reason/test-surface-interaction-correctness.md)

### valid-interfaces-and-contracts

Details

Invariant
Interfaces and contracts are valid

Surfaces
[interface-correctness](https://banes-lab.com/records/reason/test-surface-interface-correctness.md)

### acceptable-execution-time

Details

Invariant
Execution time is acceptable

Surfaces
[temporal-correctness](https://banes-lab.com/records/reason/test-surface-temporal-correctness.md), [performance-correctness](https://banes-lab.com/records/reason/test-surface-performance-correctness.md)

### acceptable-resource-consumption

Details

Invariant
Resource consumption is acceptable

Surfaces
[resource-correctness](https://banes-lab.com/records/reason/test-surface-resource-correctness.md)

### safe-concurrent-behaviour

Details

Invariant
Concurrent behaviour is safe

Surfaces
[concurrency-correctness](https://banes-lab.com/records/reason/test-surface-concurrency-correctness.md)

### controlled-memory-usage

Details

Invariant
Memory usage is controlled

Surfaces
[memory-correctness](https://banes-lab.com/records/reason/test-surface-memory-correctness.md)

### reliability-under-faults

Details

Invariant
The system stays reliable under faults

Surfaces
[reliability-correctness](https://banes-lab.com/records/reason/test-surface-reliability-correctness.md)

### availability-under-stress

Details

Invariant
The system stays available under stress

Surfaces
[availability-correctness](https://banes-lab.com/records/reason/test-surface-availability-correctness.md)

### consistency-across-components

Details

Invariant
Components stay consistent with each other

Surfaces
[consistency-correctness](https://banes-lab.com/records/reason/test-surface-consistency-correctness.md)

### deterministic-behaviour-where-required

Details

Invariant
Behaviour is deterministic where determinism is required

Surfaces
[determinism-correctness](https://banes-lab.com/records/reason/test-surface-determinism-correctness.md)

### numerical-validity

Details

Invariant
Numerical results are valid

Surfaces
[numerical-correctness](https://banes-lab.com/records/reason/test-surface-numerical-correctness.md)

### security-boundaries

Details

Invariant
Security boundaries hold

Surfaces
[security-correctness](https://banes-lab.com/records/reason/test-surface-security-correctness.md)

### protocol-compliance

Details

Invariant
Communication complies with its protocol

Surfaces
[protocol-correctness](https://banes-lab.com/records/reason/test-surface-protocol-correctness.md)

### configuration-validity

Details

Invariant
Configuration is valid

Surfaces
[configuration-correctness](https://banes-lab.com/records/reason/test-surface-configuration-correctness.md)

### accurate-observability

Details

Invariant
Logs, metrics and traces report the system accurately

Surfaces
[observability-correctness](https://banes-lab.com/records/reason/test-surface-observability-correctness.md)

### epi-reachable-check

Details

Invariant
Every representation in jurisdiction has a computable check

### epi-declared-domain

Details

Invariant
A check's domain is explicit and reported beside its verdict

### epi-declared-dependency

Details

Invariant
A dependency is declared by the referent, never inferred from a name

### epi-verdict-is-representation

Details

Invariant
A verdict is itself a representation and stays checkable

### epi-preserved-distinction

Details

Invariant
A lowering keeps every distinction a later check needs

### epi-fresh-read

Details

Invariant
A check reads a representation derived after the last relevant mutator

### epi-one-derivation

Details

Invariant
One canonical question has one authoritative derivation

### epi-weakest-link

Details

Invariant
A chain is as certain as its least certain link

### epi-observation-locates

Details

Invariant
Dynamic observation locates a failure and never certifies absence

### epi-terminate-on-three

Details

Invariant
Work stops only when saturation, completion and verification all hold

## Links to

- [Semantic Correctness](https://banes-lab.com/records/reason/test-surface-semantic-correctness.md)
- [Data Correctness](https://banes-lab.com/records/reason/test-surface-data-correctness.md)
- [Functional Correctness](https://banes-lab.com/records/reason/test-surface-functional-correctness.md)
- [State Correctness](https://banes-lab.com/records/reason/test-surface-state-correctness.md)
- [Interaction Correctness](https://banes-lab.com/records/reason/test-surface-interaction-correctness.md)
- [Interface Correctness](https://banes-lab.com/records/reason/test-surface-interface-correctness.md)
- [Temporal Correctness](https://banes-lab.com/records/reason/test-surface-temporal-correctness.md)
- [Performance Correctness](https://banes-lab.com/records/reason/test-surface-performance-correctness.md)
- [Resource Correctness](https://banes-lab.com/records/reason/test-surface-resource-correctness.md)
- [Concurrency Correctness](https://banes-lab.com/records/reason/test-surface-concurrency-correctness.md)
- [Memory Correctness](https://banes-lab.com/records/reason/test-surface-memory-correctness.md)
- [Reliability Correctness](https://banes-lab.com/records/reason/test-surface-reliability-correctness.md)
- [Availability Correctness](https://banes-lab.com/records/reason/test-surface-availability-correctness.md)
- [Consistency Correctness](https://banes-lab.com/records/reason/test-surface-consistency-correctness.md)
- [Determinism Correctness](https://banes-lab.com/records/reason/test-surface-determinism-correctness.md)
- [Numerical Correctness](https://banes-lab.com/records/reason/test-surface-numerical-correctness.md)
- [Security Correctness](https://banes-lab.com/records/reason/test-surface-security-correctness.md)
- [Protocol Correctness](https://banes-lab.com/records/reason/test-surface-protocol-correctness.md)
- [Configuration Correctness](https://banes-lab.com/records/reason/test-surface-configuration-correctness.md)
- [Observability Correctness](https://banes-lab.com/records/reason/test-surface-observability-correctness.md)
