{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T10:49:29.433Z",
  "record_id": "VXI-EXT-PROCUREMENT-STEPFUNCTIONS-EXECUTION-SEMANTICS-01-v1",
  "record_kind": "external_reference",
  "title": "Step Functions: Execution guarantees depend on workflow type",
  "system": "AWS Step Functions",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can every Step Functions workflow be described as exactly-once execution?",
  "near_questions": [
    "Is the state machine Standard or Express?",
    "Is Express invocation synchronous?",
    "Can asynchronous Express run more than once?",
    "Does synchronous Express imply exactly once?",
    "How are execution names used?",
    "Is idempotency automatically managed here?",
    "Were task retries configured?",
    "Could external effects repeat independently?",
    "What execution outcome was retained?",
    "Were concurrent starts distinguished?",
    "Which scope does the guarantee cover?",
    "Can I save the workflow-semantics review?"
  ],
  "supported_claims": [
    {
      "claim": "AWS distinguishes exactly-once Standard workflow execution, at-least-once asynchronous Express execution and at-most-once synchronous Express execution. Express idempotency is not automatically managed. The selected workflow type is essential context for interpreting repeated or missing runs.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "AWS distinguishes exactly-once Standard workflow execution, at-least-once asynchronous Express execution and at-most-once synchronous Express execution. Express idempotency is not automatically managed. The selected workflow type is essential context for interpreting repeated or missing runs.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "AWS Step Functions: Choosing workflow type",
    "source_url": "https://docs.aws.amazon.com/step-functions/latest/dg/choosing-workflow-type.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-STEPFUNCTIONS-EXECUTION-SEMANTICS-01-v1",
    "candidate_record_sha256": "6e4cf1c163799c6a7a06f5de54603065cdb680dd89960d840ed7e59ce4bd7cd6",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "AWS distinguishes exactly-once Standard workflow execution, at-least-once asynchronous Express execution and at-most-once synchronous Express execution. Express idempotency is not automatically managed. The selected workflow type is essential context for interpreting repeated or missing runs.",
    "required_buyer_context": "Workflow type, invocation mode, execution identity and task retry design. Effective buyer configuration and operational results were not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-17",
    "claim_to_check": "Can every Step Functions workflow be described as exactly-once execution?",
    "documented_statement": {
      "status": "documented",
      "statement": "AWS distinguishes exactly-once Standard workflow execution, at-least-once asynchronous Express execution and at-most-once synchronous Express execution. Express idempotency is not automatically managed. The selected workflow type is essential context for interpreting repeated or missing runs.",
      "source_ids": [
        "stepfunctions"
      ]
    },
    "buyer_evidence_required": [
      "State-machine workflow type and invocation mode.",
      "Execution names, identifiers and start responses.",
      "Task retry and downstream idempotency evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Apply the documented guarantee only to its workflow scope; review downstream side effects separately."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "stepfunctions",
        "url": "https://docs.aws.amazon.com/step-functions/latest/dg/choosing-workflow-type.html",
        "final_url": "https://docs.aws.amazon.com/step-functions/latest/dg/choosing-workflow-type.html",
        "title": "AWS Step Functions: Choosing workflow type",
        "checked_on": "2026-10-17",
        "sha256": "1bacb5b2e9be67dd861ae5b94b58c9cb22c9ce94cf8b831ce8574285dac8ad1c",
        "bytes": 27059
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Can every Step Functions workflow be described as exactly-once execution?",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Workflow type, invocation mode, execution identity and task retry design."
    }
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#step-functions-workflow-type-execution-guarantees",
  "machine_readable_record": "/varexis-index/records/step-functions-workflow-type-execution-guarantees.json"
}
