{
  "type": "illustrative-synthetic-pilot-readout",
  "customer_result": false,
  "environment": "nonproduction",
  "sample_version": "2026-10-08.1",
  "sample_notice": "Fictional format example with synthetic USD 10 inputs. These are illustrative observations, not a completed customer evaluation or new verification results.",
  "decision_question": "Can our original and replacement software paths share one recovery contract?",
  "scope": {
    "workflows": 1,
    "software_paths": 2,
    "workflow_name": "Own-account USD transfer recovery",
    "canonical_reference": "cash-request-4822",
    "economic_effect": "OWN_ACCOUNT_CASH_MOVEMENT",
    "currency": "USD",
    "principal_minor": 1000,
    "reference_boundary": "Local synthetic own-account USD reference. This example uses USD 10 within the preserved R2 USD 20 principal ceiling. Real amounts, provider contracts and customer paths require separate qualification."
  },
  "path_map": [
    {"id": "A", "label": "Original transfer worker", "release_point": "The software call site that submits the original attempt.", "identity_rule": "Retain cash-request-4822 and the original operation ID before sending."},
    {"id": "B", "label": "Replacement transfer worker", "release_point": "The software call site that proposes a replacement for the same transfer.", "identity_rule": "Use the same source-owned transfer identity. A different route or operation ID does not create capacity."}
  ],
  "existing_controls": {
    "status": "not_evaluated_in_this_sample",
    "finding": "This sample does not establish that a customer's existing idempotency, ledger or reservation is insufficient.",
    "comparison_needed": "Record whether existing controls preserve the shared reservation and original identity through unresolved outcomes, restarts and every included replacement path."
  },
  "observations": [
    {"case": "Original outcome unresolved", "replacement": "HOLD", "expected": "Reserve the full principal. Block the replacement.", "meaning": "The replacement stayed on hold while the original outcome remained unresolved.", "customer_evidence_needed": "Identify both controlled release points and the remaining ways the original can pay."},
    {"case": "Original create reply lost", "replacement": "HOLD until original resolved", "expected": "Look up the retained original operation. Do not resend create.", "meaning": "Original lookup retained the attempt identity without another financial create.", "customer_evidence_needed": "Verify that the application persists its operation ID before sending and retains it after restart."},
    {"case": "Original closed; approval stale", "replacement": "HOLD", "expected": "Closure alone does not approve a replacement.", "meaning": "An approval issued before retained closure did not permit replacement release.", "customer_evidence_needed": "Identify authoritative closure evidence and the issuer of a newer signed approval."},
    {"case": "Original closed; fresh replacement validated", "replacement": "ACCEPT", "expected": "Reobserve the original and validate the exact replacement.", "meaning": "One simulated replacement was reserved under a newer postclosure approval. Settlement remained unconfirmed.", "customer_evidence_needed": "Separately qualify provider closure semantics and the customer's complete release path."},
    {"case": "Accepted replacement still unresolved", "replacement": "HOLD", "expected": "Keep the replacement's principal reserved.", "meaning": "Another path or request could not create a second allocation while the accepted replacement could still pay.", "customer_evidence_needed": "Include every retry and rescue path in the shared control boundary."},
    {"case": "Obligation paid", "replacement": "REFUSE", "expected": "Paid history consumes the obligation.", "meaning": "A new route, request or approval did not permit another full-principal payment.", "customer_evidence_needed": "Confirm authoritative paid evidence and retained history for the actual provider path."}
  ],
  "remaining_conditions": [
    "Customer-path integration and provider qualification remain open.",
    "Common transfer mapping, existing controls and actual software call sites have not been evaluated in this sample.",
    "Manual or unconnected release paths remain outside coverage.",
    "Native bank connections, production operations, availability and customer economic value are not established."
  ],
  "written_next_decision": "Confirm the common transfer mapping and retained original identity, then agree any further provider qualification before considering enforcement.",
  "next_actions": [
    {"owner": "Customer engineer", "action": "Map the two software release points.", "completion_condition": "One source-owned transfer identity and retained operation IDs are documented for both paths."},
    {"owner": "Customer payment owner", "action": "Assign the recovery evidence owner.", "completion_condition": "The required original-outcome evidence, escalation procedure and excluded paths have accountable owners."},
    {"owner": "Customer team and HALTSEAL", "action": "Decide whether to continue the integration.", "completion_condition": "Review the actual findings against the existing controls; accept a next scope or keep the current controls. Native qualification requires a separate agreement."}
  ],
  "production_approval": false
}