{
  "code": null,
  "collection": "tension",
  "href": "https://banes-lab.com/ontology/schema#tension-consensus-latency",
  "id": "consensus-latency",
  "kind": "tension",
  "layer": null,
  "name": "Consensus / Latency",
  "ref": "tension:consensus-latency",
  "relations": [
    {
      "links": [
        {
          "href": "https://banes-lab.com/ontology#architecture-consensus",
          "json": "https://banes-lab.com/json/records/architecture/consensus",
          "label": "Consensus",
          "markdown": "https://banes-lab.com/records/architecture/consensus.md",
          "ref": "architecture:consensus"
        },
        {
          "href": "https://banes-lab.com/ontology#architecture-latency",
          "json": "https://banes-lab.com/json/records/architecture/latency",
          "label": "Latency",
          "markdown": "https://banes-lab.com/records/architecture/latency.md",
          "ref": "architecture:latency"
        }
      ],
      "relation": "tensions-with"
    },
    {
      "links": [
        {
          "href": "https://banes-lab.com/ontology/schema#vocabulary-resolution-mechanism-irreducible-tradeoff",
          "json": "https://banes-lab.com/json/records/vocabulary/resolution-mechanism-irreducible-tradeoff",
          "label": "irreducible-tradeoff",
          "markdown": "https://banes-lab.com/records/vocabulary/resolution-mechanism-irreducible-tradeoff.md",
          "ref": "vocabulary:resolution-mechanism-irreducible-tradeoff"
        }
      ],
      "relation": "mechanism"
    },
    {
      "links": [
        {
          "href": "https://banes-lab.com/ontology#architecture-category-control-coordination-centralization",
          "json": "https://banes-lab.com/json/ontology/principles/architecture-category-control-coordination-centralization",
          "label": "Control / Coordination / Centralization",
          "markdown": "https://banes-lab.com/ontology/principles/architecture-category-control-coordination-centralization.md",
          "ref": "chapter:/ontology#architecture-category-control-coordination-centralization"
        },
        {
          "href": "https://banes-lab.com/ontology/schema#the-vocabulary-resolution-mechanism",
          "json": "https://banes-lab.com/json/ontology/schema/the-vocabulary-resolution-mechanism",
          "label": "Resolution mechanisms",
          "markdown": "https://banes-lab.com/ontology/schema/the-vocabulary-resolution-mechanism.md",
          "ref": "chapter:/ontology/schema#the-vocabulary-resolution-mechanism"
        }
      ],
      "relation": "linked-from"
    }
  ],
  "summary": "\"consensus\" (execution-core layer) is traded against \"Latency\" (performance-core layer) — a principle cannot be scope-separated from a quality, metric, or cost it competes with; resolve by measuring \"Latency\" and choosing an explicit operating point.",
  "siblings": {
    "next": {
      "href": "https://banes-lab.com/ontology/schema#tension-availability-consensus",
      "json": "https://banes-lab.com/json/records/tension/availability-consensus",
      "label": "Consensus / Availability",
      "markdown": "https://banes-lab.com/records/tension/availability-consensus.md",
      "ref": "tension:availability-consensus"
    },
    "previous": {
      "href": "https://banes-lab.com/ontology/schema#tension-availability-leader-election",
      "json": "https://banes-lab.com/json/records/tension/availability-leader-election",
      "label": "Leader Election / Availability",
      "markdown": "https://banes-lab.com/records/tension/availability-leader-election.md",
      "ref": "tension:availability-leader-election"
    }
  },
  "up": {
    "href": null,
    "json": "https://banes-lab.com/json/api/records/tension",
    "label": "Tensions",
    "markdown": "https://banes-lab.com/api/records/tension.md",
    "ref": "api:records/tension"
  }
}