{
  "content": {
    "icon": "bi-signpost-split",
    "id": "the-invariants",
    "intro": "Each invariant the test surfaces assert is listed with the surfaces that assert it.",
    "subsections": [
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Outputs are correct",
                "term": "Invariant"
              },
              {
                "description": "[semantic-correctness](/records/reasoning/test-surface-semantic-correctness), [data-correctness](/records/reasoning/test-surface-data-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-correct-outputs",
        "title": "Correct Outputs"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "State evolves correctly",
                "term": "Invariant"
              },
              {
                "description": "[functional-correctness](/records/reasoning/test-surface-functional-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-correct-state-evolution",
        "title": "Correct State Evolution"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "State transitions are valid",
                "term": "Invariant"
              },
              {
                "description": "[state-correctness](/records/reasoning/test-surface-state-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-valid-state-transitions",
        "title": "Valid State Transitions"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Interactions between components are correct",
                "term": "Invariant"
              },
              {
                "description": "[interaction-correctness](/records/reasoning/test-surface-interaction-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-correct-interactions",
        "title": "Correct Interactions"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Interfaces and contracts are valid",
                "term": "Invariant"
              },
              {
                "description": "[interface-correctness](/records/reasoning/test-surface-interface-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-valid-interfaces-and-contracts",
        "title": "Valid Interfaces and Contracts"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Execution time is acceptable",
                "term": "Invariant"
              },
              {
                "description": "[temporal-correctness](/records/reasoning/test-surface-temporal-correctness), [performance-correctness](/records/reasoning/test-surface-performance-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-acceptable-execution-time",
        "title": "Acceptable Execution Time"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Resource consumption is acceptable",
                "term": "Invariant"
              },
              {
                "description": "[resource-correctness](/records/reasoning/test-surface-resource-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-acceptable-resource-consumption",
        "title": "Acceptable Resource Consumption"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Concurrent behavior is safe",
                "term": "Invariant"
              },
              {
                "description": "[concurrency-correctness](/records/reasoning/test-surface-concurrency-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-safe-concurrent-behavior",
        "title": "Safe Concurrent Behavior"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Memory usage is controlled",
                "term": "Invariant"
              },
              {
                "description": "[memory-correctness](/records/reasoning/test-surface-memory-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-controlled-memory-usage",
        "title": "Controlled Memory Usage"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "The system stays reliable under faults",
                "term": "Invariant"
              },
              {
                "description": "[reliability-correctness](/records/reasoning/test-surface-reliability-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-reliability-under-faults",
        "title": "Reliability Under Faults"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "The system stays available under stress",
                "term": "Invariant"
              },
              {
                "description": "[availability-correctness](/records/reasoning/test-surface-availability-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-availability-under-stress",
        "title": "Availability Under Stress"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Components stay consistent with each other",
                "term": "Invariant"
              },
              {
                "description": "[consistency-correctness](/records/reasoning/test-surface-consistency-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-consistency-across-components",
        "title": "Consistency Across Components"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Behavior is deterministic where determinism is required",
                "term": "Invariant"
              },
              {
                "description": "[determinism-correctness](/records/reasoning/test-surface-determinism-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-deterministic-behavior-where-required",
        "title": "Required Determinism"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Numerical results are valid",
                "term": "Invariant"
              },
              {
                "description": "[numerical-correctness](/records/reasoning/test-surface-numerical-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-numerical-validity",
        "title": "Numerical Validity"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Security boundaries hold",
                "term": "Invariant"
              },
              {
                "description": "[security-correctness](/records/reasoning/test-surface-security-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-security-boundaries",
        "title": "Security Boundaries"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Communication complies with its protocol",
                "term": "Invariant"
              },
              {
                "description": "[protocol-correctness](/records/reasoning/test-surface-protocol-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-protocol-compliance",
        "title": "Protocol Compliance"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Configuration is valid",
                "term": "Invariant"
              },
              {
                "description": "[configuration-correctness](/records/reasoning/test-surface-configuration-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-configuration-validity",
        "title": "Configuration Validity"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Logs, metrics and traces report the system accurately",
                "term": "Invariant"
              },
              {
                "description": "[observability-correctness](/records/reasoning/test-surface-observability-correctness)",
                "term": "Surfaces"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-accurate-observability",
        "title": "Accurate Observability"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Every representation in jurisdiction has a computable check",
                "term": "Invariant"
              },
              {
                "description": "[meta_field](/records/pag/production-meta-field)",
                "term": "Grounded by"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-reachable-check",
        "title": "Reachable Check"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "A check's domain is explicit and reported beside its verdict",
                "term": "Invariant"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-declared-domain",
        "title": "Declared Domain"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "A dependency is declared by the referent, never inferred from a name",
                "term": "Invariant"
              },
              {
                "description": "[dag_declaration](/records/pag/production-dag-declaration), [edge_clause](/records/pag/production-edge-clause)",
                "term": "Grounded by"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-declared-dependency",
        "title": "Declared Dependency"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "A verdict is itself a representation and has a reachable check of its own",
                "term": "Invariant"
              },
              {
                "description": "[report_block](/records/pag/production-report-block)",
                "term": "Grounded by"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-verdict-is-representation",
        "title": "Checked Verdict"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "A lowering keeps every distinction a later check needs",
                "term": "Invariant"
              },
              {
                "description": "[preserves_clause](/records/pag/production-preserves-clause)",
                "term": "Grounded by"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-preserved-distinction",
        "title": "Preserved Distinction"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "A check reads a representation derived after the last relevant mutator",
                "term": "Invariant"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-fresh-read",
        "title": "Fresh Read"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "One canonical question has one authoritative derivation",
                "term": "Invariant"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-one-derivation",
        "title": "One Derivation"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "A chain is as certain as its least certain link, and a link below the floor is removed from the chain",
                "term": "Invariant"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-weakest-link",
        "title": "Weakest Link"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "Dynamic observation locates a failure and never certifies absence",
                "term": "Invariant"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-observation-locates",
        "title": "Observation Scope"
      },
      {
        "blocks": [
          {
            "entries": [
              {
                "description": "A run stops when saturation, completion and verification all hold, or when it is blocked on something outside it",
                "term": "Invariant"
              }
            ],
            "kind": "glossary"
          },
          {
            "kind": "text",
            "text": "How it is checked"
          },
          {
            "entries": [
              {
                "description": "the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground",
                "term": "Checked by"
              },
              {
                "description": "Every test surface and document construct that names the invariant",
                "term": "Population"
              },
              {
                "description": "A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes",
                "term": "Freshness"
              },
              {
                "description": "The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause",
                "term": "Refusal"
              },
              {
                "description": "The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence",
                "term": "Observation"
              },
              {
                "description": "Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean",
                "term": "Evidence"
              },
              {
                "description": "The invariant record, which every surface and document construct that asserts it cites",
                "term": "Authoritative side"
              },
              {
                "description": "Not answered",
                "term": "Depends on"
              },
              {
                "description": "Not answered",
                "term": "Shape it refuses"
              }
            ],
            "kind": "glossary"
          }
        ],
        "id": "reasoning-invariant-epi-terminate-on-three",
        "title": "Three-Condition Stop"
      }
    ],
    "title": "The invariants"
  },
  "graph": {
    "narrative": true,
    "requires": [],
    "teaches": [],
    "traces": []
  },
  "href": "https://banes-lab.com/ontology/reasoning#the-invariants",
  "number": "211",
  "page": "ontology",
  "ref": "chapter:/ontology/reasoning#the-invariants",
  "relations": [
    {
      "links": [
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-semantic-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-semantic-correctness",
          "label": "Semantic Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-semantic-correctness.md",
          "ref": "reasoning:test-surface-semantic-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-data-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-data-correctness",
          "label": "Data Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-data-correctness.md",
          "ref": "reasoning:test-surface-data-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-functional-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-functional-correctness",
          "label": "Functional Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-functional-correctness.md",
          "ref": "reasoning:test-surface-functional-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-state-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-state-correctness",
          "label": "State Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-state-correctness.md",
          "ref": "reasoning:test-surface-state-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-interaction-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-interaction-correctness",
          "label": "Interaction Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-interaction-correctness.md",
          "ref": "reasoning:test-surface-interaction-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-interface-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-interface-correctness",
          "label": "Interface Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-interface-correctness.md",
          "ref": "reasoning:test-surface-interface-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-temporal-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-temporal-correctness",
          "label": "Temporal Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-temporal-correctness.md",
          "ref": "reasoning:test-surface-temporal-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-performance-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-performance-correctness",
          "label": "Performance Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-performance-correctness.md",
          "ref": "reasoning:test-surface-performance-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-resource-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-resource-correctness",
          "label": "Resource Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-resource-correctness.md",
          "ref": "reasoning:test-surface-resource-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-concurrency-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-concurrency-correctness",
          "label": "Concurrency Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-concurrency-correctness.md",
          "ref": "reasoning:test-surface-concurrency-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-memory-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-memory-correctness",
          "label": "Memory Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-memory-correctness.md",
          "ref": "reasoning:test-surface-memory-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-reliability-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-reliability-correctness",
          "label": "Reliability Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-reliability-correctness.md",
          "ref": "reasoning:test-surface-reliability-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-availability-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-availability-correctness",
          "label": "Availability Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-availability-correctness.md",
          "ref": "reasoning:test-surface-availability-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-consistency-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-consistency-correctness",
          "label": "Consistency Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-consistency-correctness.md",
          "ref": "reasoning:test-surface-consistency-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-determinism-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-determinism-correctness",
          "label": "Determinism Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-determinism-correctness.md",
          "ref": "reasoning:test-surface-determinism-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-numerical-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-numerical-correctness",
          "label": "Numerical Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-numerical-correctness.md",
          "ref": "reasoning:test-surface-numerical-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-security-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-security-correctness",
          "label": "Security Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-security-correctness.md",
          "ref": "reasoning:test-surface-security-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-protocol-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-protocol-correctness",
          "label": "Protocol Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-protocol-correctness.md",
          "ref": "reasoning:test-surface-protocol-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-configuration-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-configuration-correctness",
          "label": "Configuration Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-configuration-correctness.md",
          "ref": "reasoning:test-surface-configuration-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/reasoning#reasoning-test-surface-observability-correctness",
          "json": "https://banes-lab.com/json/records/reasoning/test-surface-observability-correctness",
          "label": "Observability Correctness",
          "markdown": "https://banes-lab.com/records/reasoning/test-surface-observability-correctness.md",
          "ref": "reasoning:test-surface-observability-correctness"
        },
        {
          "href": "https://banes-lab.com/ontology/grammar#pag-production-meta-field",
          "json": "https://banes-lab.com/json/records/pag/production-meta-field",
          "label": "meta_field",
          "markdown": "https://banes-lab.com/records/pag/production-meta-field.md",
          "ref": "pag:production-meta-field"
        },
        {
          "href": "https://banes-lab.com/ontology/grammar#pag-production-dag-declaration",
          "json": "https://banes-lab.com/json/records/pag/production-dag-declaration",
          "label": "dag_declaration",
          "markdown": "https://banes-lab.com/records/pag/production-dag-declaration.md",
          "ref": "pag:production-dag-declaration"
        },
        {
          "href": "https://banes-lab.com/ontology/grammar#pag-production-edge-clause",
          "json": "https://banes-lab.com/json/records/pag/production-edge-clause",
          "label": "edge_clause",
          "markdown": "https://banes-lab.com/records/pag/production-edge-clause.md",
          "ref": "pag:production-edge-clause"
        },
        {
          "href": "https://banes-lab.com/ontology/grammar#pag-production-report-block",
          "json": "https://banes-lab.com/json/records/pag/production-report-block",
          "label": "report_block",
          "markdown": "https://banes-lab.com/records/pag/production-report-block.md",
          "ref": "pag:production-report-block"
        },
        {
          "href": "https://banes-lab.com/ontology/grammar#pag-production-preserves-clause",
          "json": "https://banes-lab.com/json/records/pag/production-preserves-clause",
          "label": "preserves_clause",
          "markdown": "https://banes-lab.com/records/pag/production-preserves-clause.md",
          "ref": "pag:production-preserves-clause"
        }
      ],
      "relation": "links-to"
    }
  ],
  "route": null,
  "section": "the-invariants",
  "summary": "Each invariant the test surfaces assert is listed with the surfaces that assert it.",
  "tab": "reasoning",
  "title": "The invariants",
  "siblings": {
    "next": {
      "href": "https://banes-lab.com/ontology/reasoning#the-failure-shapes",
      "json": "https://banes-lab.com/json/ontology/reasoning/the-failure-shapes",
      "label": "Failure shapes",
      "markdown": "https://banes-lab.com/ontology/reasoning/the-failure-shapes.md",
      "ref": "chapter:/ontology/reasoning#the-failure-shapes"
    },
    "previous": {
      "href": "https://banes-lab.com/ontology/reasoning#the-techniques",
      "json": "https://banes-lab.com/json/ontology/reasoning/the-techniques",
      "label": "The techniques",
      "markdown": "https://banes-lab.com/ontology/reasoning/the-techniques.md",
      "ref": "chapter:/ontology/reasoning#the-techniques"
    }
  },
  "up": {
    "href": "https://banes-lab.com/ontology/reasoning",
    "json": "https://banes-lab.com/json/api/pages/ontology/reasoning",
    "label": "Ontology · Reasoning",
    "markdown": "https://banes-lab.com/api/pages/ontology/reasoning.md",
    "ref": "api:/ontology/reasoning"
  }
}
