{
  "canonicalUrl": "https://xn--mwe.com/comparisons/merge-result-vs-owner-decision/",
  "claimStatus": "PROJECT DOCTRINE",
  "correctionStatus": "CURRENT K05 RELEASE",
  "decisionUse": "Use this distinction to prevent deterministic test evidence, signatures, consensus, merge output, stress results, gate states, process replay, scheduler simulation, labels, or release diffs from being represented as authority, deployment, operation, or factual truth.",
  "distinction": "Merge result and Owner decision answer different evidentiary, governance, release, or operational questions and must remain separate.",
  "failure": "Conflation can manufacture readiness, erase uncertainty, bypass accountable review, or expose protected information.",
  "id": "K01-COMP-090",
  "lastReviewed": "2026-08-16",
  "left": "Merge result",
  "leftMeaning": "Non-conflicting branch content is combined and conflicts are exposed.",
  "name": "Merge result vs Owner decision",
  "releaseId": "K12-2026-08-16",
  "researchCutoff": "2026-08-16",
  "right": "Owner decision",
  "rightMeaning": "The designated owner or authority resolves protected or mission-significant conflicts.",
  "slug": "merge-result-vs-owner-decision",
  "sourceRevalidatedAt": "2026-08-15T23:00:00Z",
  "topic": "cyber-physical-mission-assurance",
  "type": "Comparison"
}