{
  "$schema": "https://themachinepress.com/schemas/story-v1.schema.json",
  "schema_version": "1.0.0",
  "document_type": "machine_press_story",
  "story": {
    "story_id": "mp-2026-09-09-007",
    "source_story_id": "tmp-story-portable-agent-execution-substrates",
    "edition_id": "mp-2026-09-09-morning-0062",
    "edition_url": "https://themachinepress.com/edition/2026-09-09",
    "position": 7,
    "story_type": "dispatch",
    "section": "developer-tools",
    "editorial_classification": "editorial",
    "headline": "One Agent Workflow Ran Three Different Ways",
    "slug": "one-agent-workflow-ran-three-different-ways",
    "dek": "A production platform compiled the same typed graph to streaming, durable orchestration and batch execution without workflow-code changes.",
    "summary": "A production platform compiled the same typed graph to streaming, durable orchestration and batch execution without workflow-code changes.",
    "body_text": "The reported platform emerged from Amazon’s Rufus assistant, where real-time serving, background tasks and high-volume evaluation normally require different runtimes. Developers define one typed dataflow graph, which is then bound to in-process streaming, durable AWS SWF orchestration or distributed Apache Flink processing. Language-model calls become suspendable nodes whose delivery, retry and batching semantics follow the selected substrate. Dozens of production configurations across five orchestration patterns showed no detectable output-quality difference across bindings, while batch execution reduced inference cost in line with published batch pricing. The evidence is an engineering report from one production ecosystem rather than a cross-platform standard.",
    "why_it_matters": "A production platform compiled the same typed graph to streaming, durable orchestration and batch execution without workflow-code changes.",
    "limitations": [],
    "importance": 8,
    "canonical_url": "https://themachinepress.com/story/mp-2026-09-09-007/one-agent-workflow-ran-three-different-ways",
    "json_url": "https://themachinepress.com/story/mp-2026-09-09-007.json",
    "first_published_at": "2026-09-09T09:00:00.000-04:00",
    "modified_at": "2026-09-09T09:00:00.000-04:00",
    "content_status": "new",
    "is_carryover": false,
    "carryover_reason": null,
    "key_claims": [
      {
        "claim_id": "claim-mp-2026-09-09-007-001",
        "text": "A production platform compiled the same typed graph to streaming, durable orchestration and batch execution without workflow-code changes.",
        "source_ids": [
          "source-2026-09-09-007"
        ],
        "qualification": null
      }
    ],
    "source_ids": [
      "source-2026-09-09-007"
    ],
    "tags": [
      "agent workflows",
      "runtime portability",
      "batch inference"
    ],
    "image_url": null,
    "corrections": []
  },
  "sources": [
    {
      "source_id": "source-2026-09-09-007",
      "title": "arXiv preprint 2609.06128",
      "publisher": "arXiv",
      "url": "https://arxiv.org/abs/2609.06128",
      "canonical_url": "https://arxiv.org/abs/2609.06128",
      "source_type": "primary_research",
      "is_primary_source": true,
      "published_at": "2026-09-05T10:52:35.000-04:00",
      "accessed_at": "2026-09-09T08:30:00.000-04:00",
      "supports_claim_ids": [
        "claim-mp-2026-09-09-007-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": "One Agent Workflow Ran Three Different Ways",
    "publisher": "The Machine Press",
    "published_at": "2026-09-09T09:00:00.000-04:00",
    "canonical_url": "https://themachinepress.com/story/mp-2026-09-09-007/one-agent-workflow-ran-three-different-ways"
  }
}