{
  "$schema": "https://themachinepress.com/schemas/story-v1.schema.json",
  "schema_version": "1.0.0",
  "document_type": "machine_press_story",
  "story": {
    "story_id": "mp-2026-08-22-019",
    "source_story_id": "tmp-sidebar-physical-ai-verification-gap",
    "edition_id": "mp-2026-08-22-morning-0044",
    "edition_url": "https://themachinepress.com/edition/2026-08-22",
    "position": 21,
    "story_type": "ticker",
    "section": "robotics",
    "editorial_classification": "editorial",
    "headline": "Understanding the Command Wasn’t Authority to Execute It",
    "slug": "understanding-the-command-wasn-t-authority-to-execute-it",
    "dek": "A communication framework separated evidence sufficiency, finalization authority and the runtime gate.",
    "summary": "A communication framework separated evidence sufficiency, finalization authority and the runtime gate.",
    "body_text": "Finite-state checks explore how evidence transfer and coordination behave under sender- or receiver-side finalization. The result is a conceptual framework and controlled model, not a deployed physical-AI safety system.",
    "why_it_matters": "A communication framework separated evidence sufficiency, finalization authority and the runtime gate.",
    "limitations": [
      "The result is a conceptual framework and controlled model, not a deployed physical-AI safety system."
    ],
    "importance": 7,
    "canonical_url": "https://themachinepress.com/story/mp-2026-08-22-019/understanding-the-command-wasn-t-authority-to-execute-it",
    "json_url": "https://themachinepress.com/story/mp-2026-08-22-019.json",
    "first_published_at": "2026-08-22T09:00:00.000-04:00",
    "modified_at": "2026-08-22T09:00:00.000-04:00",
    "content_status": "new",
    "is_carryover": false,
    "carryover_reason": null,
    "key_claims": [
      {
        "claim_id": "claim-mp-2026-08-22-019-001",
        "text": "A communication framework separated evidence sufficiency, finalization authority and the runtime gate.",
        "source_ids": [
          "source-2026-08-22-021"
        ],
        "qualification": "The result is a conceptual framework and controlled model, not a deployed physical-AI safety system."
      }
    ],
    "source_ids": [
      "source-2026-08-22-021"
    ],
    "tags": [
      "physical AI",
      "verification",
      "networks",
      "runtime gates"
    ],
    "image_url": null,
    "corrections": []
  },
  "sources": [
    {
      "source_id": "source-2026-08-22-021",
      "title": "arXiv preprint 2608.19593",
      "publisher": "arXiv",
      "url": "https://arxiv.org/abs/2608.19593",
      "canonical_url": "https://arxiv.org/abs/2608.19593",
      "source_type": "primary_research",
      "is_primary_source": true,
      "published_at": "2026-08-19T20:00:00.000-04:00",
      "accessed_at": "2026-08-22T08:29:14.000-04:00",
      "supports_claim_ids": [
        "claim-mp-2026-08-22-019-001"
      ]
    }
  ],
  "corrections": [],
  "publisher": {
    "name": "The Machine Press",
    "url": "https://themachinepress.com",
    "description": "A daily newspaper for the age of artificial intelligence."
  },
  "cite_this_report": {
    "title": "Understanding the Command Wasn’t Authority to Execute It",
    "publisher": "The Machine Press",
    "published_at": "2026-08-22T09:00:00.000-04:00",
    "canonical_url": "https://themachinepress.com/story/mp-2026-08-22-019/understanding-the-command-wasn-t-authority-to-execute-it"
  }
}