{
  "status": "success",
  "data": {
    "contract": {
      "id": "public-materials",
      "name": "Public Materials",
      "summary": "A static catalog of concrete reliability scenario packs that connect TRADING4AI's public services to high-risk financial review tasks.",
      "htmlPath": "/agent-verification/materials",
      "artifactPath": "/reliability/public-materials-sample.json",
      "artifactProvenance": {
        "schemaVersion": "trading4ai-public-reliability-v1",
        "artifactVersion": "public-materials-sample-2026-05-25",
        "generatedAt": "2026-05-25T00:00:00.000Z",
        "staticSnapshotAt": "2026-05-25T00:00:00.000Z",
        "artifactUrl": "/reliability/public-materials-sample.json",
        "citationFields": [
          "artifactVersion",
          "generatedAt",
          "packs[].artifactProvenance.artifactVersion",
          "packs[].sampleEvidenceRecords[].retrievedAt",
          "packs[].sourceRefs"
        ],
        "howToCite": [
          "When citing the catalog, preserve artifactVersion, generatedAt, and the pack-specific artifact URLs you actually used.",
          "Open the HTML page first for scope and limitations, then cite the JSON artifact as a static pack catalog rather than a live review service."
        ]
      },
      "usageRules": {
        "stayAtServiceLayerWhen": [
          "Stay on the service page when the task is still broad and the agent has not yet identified the exact review scenario.",
          "Use the service layer first when the main need is to understand the general contract, output shape, and boundary language for Action Preflight, Evidence Cards, or Reliability Corpus.",
          "Do not jump straight to a pack when the action, source set, or publication claim is still too vague to name a concrete review context."
        ],
        "openScenarioPackWhen": [
          "Open the scenario pack when the task already maps to a concrete review job such as counterparty screening, wallet-transfer review, macro release packaging, filing review, or claim-safety review.",
          "Use the pack when the reader needs scenario-level checklist items, evidence-to-collect fields, and bounded safe-versus-blocked language examples.",
          "Treat the pack as the middle layer between the generic service page and the raw machine-readable JSON artifact."
        ],
        "useJsonArtifactWhen": [
          "Use the JSON artifact only after the HTML page has made the scope, limitations, and non-goals clear.",
          "Download the JSON when another agent, crawler, or retrieval workflow needs the stable machine-readable handoff surface rather than the explanatory page.",
          "Treat the JSON as a static artifact for retrieval and audit, not as a live work queue, runtime API, or request-time review service."
        ],
        "escalateToHumanReviewWhen": [
          "Escalate to human review when the case is high-value, private, legally sensitive, or close to irreversible money movement.",
          "Escalate when the evidence stays incomplete, the wording upgrades partial evidence into certainty, or the pack itself says unresolved items remain.",
          "Do not treat any static page or JSON artifact as approval, clearance, or final compliance judgment."
        ]
      },
      "delivery": "static_html_plus_static_json_artifact",
      "staticOnly": true,
      "runtimeApi": false,
      "backtesting": false,
      "tencentBackendRequired": false
    },
    "pack": {
      "id": "payment_instruction_change_pack",
      "slug": "payment-instruction-change-pack",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "packArtifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "artifactProvenance": {
        "schemaVersion": "trading4ai-public-reliability-v1",
        "artifactVersion": "public-material-payment-instruction-change-pack-2026-05-25",
        "generatedAt": "2026-05-25T00:00:00.000Z",
        "staticSnapshotAt": "2026-05-25T00:00:00.000Z",
        "artifactUrl": "/reliability/public-materials/payment-instruction-change-pack.json",
        "citationFields": [
          "artifactVersion",
          "generatedAt",
          "sampleEvidenceRecords[].retrievedAt",
          "sampleReviewOutput.verdict",
          "sourceRefs"
        ],
        "howToCite": [
          "When citing this pack, preserve artifactVersion, generatedAt, sampleEvidenceRecords[].retrievedAt, and sourceRefs together.",
          "Do not turn the pack into payment approval, safety clearance, or compliance sign-off."
        ]
      },
      "title": "Payment instruction change before settlement",
      "recommendedStart": true,
      "startHereReason": "Start here first when a beneficiary, bank account, or wallet destination changes shortly before payment and the instruction arrives through a weak or unverified channel.",
      "readingOrderLabel": "Start here next",
      "serviceId": "action-preflight",
      "serviceName": "Action Preflight",
      "actionTaxonomy": {
        "actionType": "payment_instruction_change_before_settlement",
        "preflightStage": "before_settlement_or_release",
        "defaultPosture": "block",
        "primaryActionRisk": "Changed payment instructions can redirect funds before channel integrity, beneficiary ownership, and destination details are verified.",
        "routeWhen": [
          "A user or agent receives changed bank, wire, invoice, wallet, memo, tag, or destination instructions before settlement.",
          "The request includes urgency, secrecy, channel mismatch, beneficiary mismatch, or newly introduced payment rails."
        ],
        "stopOrEscalateWhen": [
          "Known-good channel confirmation, beneficiary ownership, prior payment rail comparison, or dual approval is missing.",
          "SWIFT, IBAN, routing, account number, wallet chain, memo, tag, destination tag, or settlement cut-off details are incomplete."
        ],
        "minimumInputFieldIds": [
          "prior_payment_instruction",
          "changed_instruction",
          "known_good_confirmation",
          "payment_destination"
        ],
        "minimumRequiredInputs": [
          "Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.",
          "New or changed instruction details, including channel received, timestamp, sender identity, and exact destination fields.",
          "Known-good confirmation channel and second-approver evidence that is independent of the changed instruction.",
          "Settlement amount, cut-off time, jurisdiction, and whether the change creates urgency or secrecy pressure."
        ],
        "missingInputFallback": "Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete."
      },
      "scenario": "A financial agent is asked to settle an invoice using new bank or wallet instructions that arrived shortly before cut-off through a channel that was not previously verified.",
      "whyItMatters": "Changed payment instructions are a classic irreversible-action risk: the money can move before identity, beneficiary ownership, and instruction legitimacy are verified.",
      "intendedUsers": [
        "AI agents preparing invoice settlement, treasury handoff, or vendor-payment steps",
        "Human reviewers checking whether new beneficiary or wallet instructions should block payment until verified",
        "Crawlers and retrieval systems that need a concrete public example of payment-change review before settlement"
      ],
      "inputShape": [
        "intendedAction: the action the agent or user is considering",
        "counterparty: optional provider, wallet, company, app, or group name",
        "claims: one or more claims the agent saw or wants to repeat",
        "paymentMethod: optional card, bank, crypto, brokerage, or unspecified rail",
        "assetClass: optional equity, crypto, fund, macro, or other label"
      ],
      "outputShape": [
        "allow/review/block decision for the payment-change request",
        "risk flags for channel mismatch, beneficiary mismatch, urgency pressure, and unverified wallet or bank details",
        "required verification steps before any settlement proceeds"
      ],
      "limitations": [
        "Runs as a static/client-side demo in this phase, not a server-side decision service",
        "Does not prove an action is legal, safe, suitable, profitable, or compliant",
        "High-risk or ambiguous actions still require qualified human review",
        "The pack does not verify beneficial ownership, authenticate the sender fully, or replace treasury, legal, banking, or sanctions workflows."
      ],
      "sourceRefs": [
        "https://www.cisa.gov/news-events/news/business-email-compromise",
        "https://consumer.ftc.gov/consumer-alerts",
        "https://www.fbi.gov/how-we-can-help-you/scams-and-safety/common-frauds-and-scams/business-email-compromise",
        "https://www.fincen.gov/resources/statutes-regulations/guidance/advisory-financial-institutions-e-mail-compromise-fraud"
      ],
      "reviewChecklist": [
        "Compare the new beneficiary, bank account, or wallet destination against the previously verified vendor record or invoice file.",
        "Verify the instruction through a known-good channel such as a stored vendor portal, signed contact route, or previously validated finance contact.",
        "Record every mismatch in beneficiary name, domain, invoice metadata, SWIFT or IBAN, routing and account number, wallet chain, memo, tag, or destination tag before restating the request.",
        "Check whether settlement cut-off pressure bypasses known-good channel confirmation, dual approval, or treasury review.",
        "Keep the payment blocked until ownership, channel legitimacy, and urgency claims are resolved by human review."
      ],
      "evidenceToCollect": [
        "The original invoice, prior beneficiary record, and the exact changed payment instruction text or attachment.",
        "The verified channel history showing which email domain, portal, phone number, or wallet record was previously trusted.",
        "The prior payment rail and destination-integrity fields: SWIFT or IBAN, routing number, account number, wallet address, wallet chain, memo, tag, destination tag, and settlement cut-off.",
        "Any bank letter, supplier-portal confirmation, signed change notice, or dual-approval record tying the new beneficiary or wallet to the known counterparty.",
        "Timestamped notes for every mismatch across beneficiary name, account number, wallet address, invoice number, approver, and approval chain."
      ],
      "deliveryOutputs": [
        "A bounded summary of what changed across beneficiary, channel, and invoice metadata.",
        "A block-or-review recommendation that keeps settlement paused while key evidence remains unresolved.",
        "A concrete destination-integrity checklist covering bank rail fields, wallet rail fields, known-good channel proof, dual-control review, and settlement hold status.",
        "Safe wording that states the evidence status without upgrading it into approval or counterparty clearance."
      ],
      "citationRules": [
        "Tie every restated payment-change fact to the exact source note, invoice record, or warning source plus retrieval time.",
        "Separate observed mismatches from interpretation; do not convert a partial match, no-hit result, or silence into trust.",
        "Keep beneficiary, channel, and ownership uncertainty visible in every summary until the change is independently verified.",
        "Never restate this pack as evidence that the new payment instruction is safe, approved, or compliant."
      ],
      "sampleInputSummary": "Draft settlement request: an accounts-payable agent receives new wire and wallet instructions for an existing supplier two hours before cut-off, with a note saying the old finance contact should not be called.",
      "sampleEvidenceRecords": [
        {
          "id": "beneficiary_name_mismatch",
          "label": "The changed beneficiary name no longer matches the supplier name on the last verified invoice and onboarding record",
          "status": "warning",
          "sourceLabel": "Verified supplier record (sample)",
          "sourceUrl": "/agent-verification/materials/payment-instruction-change-pack",
          "retrievedAt": "2026-05-25T00:00:00.000Z",
          "note": "The new instruction swaps the stored supplier entity for a new payee name that has not been independently tied to the vendor."
        },
        {
          "id": "unverified_channel_switch",
          "label": "The payment-change request arrived from a new email thread and was not confirmed in the previously trusted supplier portal",
          "status": "warning",
          "sourceLabel": "Supplier portal verification log (sample)",
          "sourceUrl": "/agent-verification/materials/payment-instruction-change-pack",
          "retrievedAt": "2026-05-25T00:00:00.000Z",
          "note": "The approved settlement workflow uses the supplier portal, but the change request came from a side-channel message."
        },
        {
          "id": "ownership_proof_missing",
          "label": "No signed bank letter, portal confirmation, or wallet-ownership record ties the new destination to the claimed supplier",
          "status": "unresolved",
          "sourceLabel": "Payment instruction change pack boundary note",
          "sourceUrl": "/agent-verification/materials/payment-instruction-change-pack",
          "retrievedAt": "2026-05-25T00:00:00.000Z",
          "note": "The request includes urgency language but no document that proves the beneficiary or wallet change is legitimate."
        },
        {
          "id": "destination_integrity_gap",
          "label": "Destination-integrity fields are incomplete across SWIFT, IBAN, routing, account number, wallet chain, memo, tag, and destination tag",
          "status": "unresolved",
          "sourceLabel": "Payment instruction change pack destination-integrity checklist",
          "sourceUrl": "/agent-verification/materials/payment-instruction-change-pack",
          "retrievedAt": "2026-05-25T00:00:00.000Z",
          "note": "The agent cannot compare the prior payment rail to the new bank or wallet destination because key account number, wallet chain, memo, and destination tag fields are missing."
        },
        {
          "id": "urgency_and_secrecy_pressure",
          "label": "The message asks for same-day settlement and says the old finance contact should not be called",
          "status": "warning",
          "sourceLabel": "CISA Business Email Compromise guidance",
          "sourceUrl": "https://www.cisa.gov/news-events/news/business-email-compromise",
          "retrievedAt": "2026-05-25T00:00:00.000Z",
          "note": "Urgency plus secrecy is a clear escalation signal, not supporting evidence for the payment change."
        },
        {
          "id": "fbi_bec_source_required",
          "label": "FBI Business Email Compromise (BEC) guidance remains a required reference for payment-instruction change risk",
          "status": "warning",
          "sourceLabel": "FBI Business Email Compromise guidance",
          "sourceUrl": "https://www.fbi.gov/how-we-can-help-you/scams-and-safety/common-frauds-and-scams/business-email-compromise",
          "retrievedAt": "2026-05-25T00:00:00.000Z",
          "note": "The FBI source supports treating changed payment instructions and compromised communication channels as high-risk; this static pack does not run a live fraud check."
        },
        {
          "id": "ftc_consumer_alert_source_required",
          "label": "FTC consumer alert coverage remains relevant when payment instructions arrive through suspicious or impersonation-style channels",
          "status": "warning",
          "sourceLabel": "FTC consumer alerts",
          "sourceUrl": "https://consumer.ftc.gov/consumer-alerts",
          "retrievedAt": "2026-05-25T00:00:00.000Z",
          "note": "The FTC source is public warning context for suspicious payment and impersonation patterns; it does not approve a changed payment instruction or clear a beneficiary."
        },
        {
          "id": "fincen_email_compromise_source_required",
          "label": "FinCEN e-mail compromise fraud advisory remains a required reference for suspicious wire-transfer instruction changes",
          "status": "unresolved",
          "sourceLabel": "FinCEN e-mail compromise fraud advisory for financial institutions",
          "sourceUrl": "https://www.fincen.gov/resources/statutes-regulations/guidance/advisory-financial-institutions-e-mail-compromise-fraud",
          "retrievedAt": "2026-05-25T00:00:00.000Z",
          "note": "The FinCEN advisory is cited as official guidance for wire and e-mail compromise patterns; the sample does not replace bank, treasury, or compliance review."
        }
      ],
      "sampleReviewOutput": {
        "verdict": "block",
        "summary": "The changed payment instruction remains blocked because beneficiary ownership, channel legitimacy, and urgency pressure are unresolved.",
        "unresolvedItems": [
          "The new beneficiary or wallet destination is not independently tied to the previously verified supplier identity.",
          "The instruction change did not arrive through the known-good portal or verified finance contact path.",
          "No ownership document or signed change record supports the new destination before settlement.",
          "FBI BEC and FinCEN e-mail compromise guidance are source requirements for this pattern, not live clearance results."
        ],
        "requiredFollowUp": [
          "Reconfirm the payment change through a previously verified vendor channel or portal before any settlement proceeds.",
          "Capture the exact beneficiary mismatch, timing pressure, channel mismatch, and official BEC/wire-fraud warning references in the final evidence note.",
          "Escalate to human treasury review and keep payment blocked until the ownership chain and approval route are verified."
        ],
        "safeRestatement": "Checked the changed payment instruction against the cited sample records and warning sources at the listed retrieval time; settlement remains blocked and under settlement hold because beneficiary, known-good channel, destination integrity, ownership, and dual approval checks are still unresolved.",
        "blockedRestatement": "The new payment instruction is verified, safe, and approved for settlement."
      },
      "escalationTriggers": [
        "The beneficiary, bank account, or wallet destination changes shortly before settlement.",
        "The change request arrives through a side channel, new domain, forwarded thread, or private message instead of the known approved route.",
        "The request uses urgency, secrecy, or exception language to discourage verification through the normal approval path."
      ],
      "safeStatements": [
        "The payment-change request is still blocked because the new destination has not been independently matched to the known supplier record.",
        "This pack can describe what changed and what was checked, but it does not approve the new instruction or clear the counterparty.",
        "Urgency or secrecy language remains a risk flag until the beneficiary and channel are independently verified."
      ],
      "blockedStatements": [
        "The new payment instruction is safe.",
        "The changed beneficiary is verified and settlement can proceed.",
        "No further review is needed because the new account details were sent before cut-off."
      ],
      "relatedArtifacts": [
        {
          "label": "Action Preflight page",
          "href": "/agent-verification/action-preflight",
          "kind": "html_page"
        },
        {
          "label": "Action Preflight JSON sample",
          "href": "/reliability/action-preflight-sample.json",
          "kind": "json_artifact"
        },
        {
          "label": "Counterparty Screening pack",
          "href": "/agent-verification/materials/counterparty-screening-pack",
          "kind": "html_page"
        },
        {
          "label": "Counterparty Screening JSON sample",
          "href": "/reliability/public-materials/counterparty-screening-pack.json",
          "kind": "json_artifact"
        }
      ],
      "artifactPath": "/reliability/action-preflight-sample.json",
      "plainLanguageSummary": "Use this static pack before a financial agent accepts changed payment instructions, new bank details, new wallet details, or last-minute beneficiary changes.",
      "exampleUserInput": "A user asks whether they should follow a new invoice, bank account, or wallet instruction that arrived shortly before settlement.",
      "expectedStaticOutput": "A source-bound action note that compares the previous approved instruction with the changed instruction, confirmation channel, mismatch evidence, and escalation boundary.",
      "bestUsedWhen": [
        "A payment instruction changes close to settlement or arrives through a side channel.",
        "The agent needs to preserve previous approved beneficiary data and independent confirmation requirements before acting."
      ],
      "notUsedFor": [
        "Live screening, live compliance clearance, or request-time approval.",
        "Trading, backtesting, execution, investment advice, or legal advice."
      ],
      "sourceFreshnessNote": "This pack preserves a static source snapshot and citation trail; it does not fetch fresh third-party data at request time.",
      "agentReadingHint": "Read the HTML page first for boundaries, then use the JSON artifact for structured retrieval.",
      "decisionMatrix": [
        {
          "matrixId": "payment_instruction_change_pack_prior_instruction_row",
          "label": "Prior payment instruction row",
          "status": "confirmed",
          "evidenceFieldIds": [
            "prior_payment_instruction",
            "source_links"
          ],
          "sourceRequirement": "Record the previously approved beneficiary, bank, wallet, memo/tag, and settlement instruction as the comparison baseline.",
          "allowedStaticUse": "Use as the known-good baseline for comparing the changed instruction against the previously approved record.",
          "blockedUpgrade": "Do not treat the prior instruction as evidence that the new instruction is automatically safe.",
          "agentAction": "Preserve the baseline and compare every changed field before payment moves."
        },
        {
          "matrixId": "payment_instruction_change_pack_changed_instruction_row",
          "label": "Changed instruction and sender row",
          "status": "warning",
          "evidenceFieldIds": [
            "changed_instruction",
            "source_links"
          ],
          "sourceRequirement": "Record the new bank or wallet details, sender identity, channel, timestamp, and urgency context that introduced the change.",
          "allowedStaticUse": "Use as a source-bound record of what changed and how it arrived.",
          "blockedUpgrade": "Do not treat a changed instruction as legitimate just because it looks similar to the baseline.",
          "agentAction": "Keep the change visible and stop if the sender or channel is not trusted."
        },
        {
          "matrixId": "payment_instruction_change_pack_confirmation_row",
          "label": "Independent confirmation row",
          "status": "unresolved",
          "evidenceFieldIds": [
            "known_good_confirmation",
            "source_links"
          ],
          "sourceRequirement": "Record the call-back number, portal confirmation, second approver, or other known-good channel used to verify the change.",
          "allowedStaticUse": "Use the known-good channel row to distinguish independent confirmation from attacker-controlled confirmation.",
          "blockedUpgrade": "Do not convert a reply in the same thread or the same sender chain into approval.",
          "agentAction": "Escalate until the change is confirmed through an independent channel."
        },
        {
          "matrixId": "payment_instruction_change_pack_urgency_and_timing_row",
          "label": "Urgency and timing risk row",
          "status": "warning",
          "evidenceFieldIds": [
            "changed_instruction",
            "known_good_confirmation"
          ],
          "sourceRequirement": "Record whether the instruction changed shortly before settlement, with urgency pressure, or with incomplete destination details.",
          "allowedStaticUse": "Use urgency and timing as static risk context, not as a reason to move faster.",
          "blockedUpgrade": "Do not convert urgency or deadline pressure into a safe or compliant approval path.",
          "agentAction": "Hold the change for review when urgency appears before independent confirmation."
        }
      ]
    },
    "sampleEvidenceCard": {
      "cardId": "payment_instruction_change_pack_sample_evidence_card",
      "cardTitle": "Payment instruction change before settlement sample evidence card",
      "evidenceLevel": "static_public_sample",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "reviewVerdict": "block",
      "sourceBoundSummary": "Checked the changed payment instruction against the cited sample records and warning sources at the listed retrieval time; settlement remains blocked and under settlement hold because beneficiary, known-good channel, destination integrity, ownership, and dual approval checks are still unresolved.",
      "sourceRefs": [
        "https://www.cisa.gov/news-events/news/business-email-compromise",
        "https://consumer.ftc.gov/consumer-alerts",
        "https://www.fbi.gov/how-we-can-help-you/scams-and-safety/common-frauds-and-scams/business-email-compromise",
        "https://www.fincen.gov/resources/statutes-regulations/guidance/advisory-financial-institutions-e-mail-compromise-fraud"
      ],
      "canonicalCitation": {
        "pageUrl": "https://trading4ai.com/agent-verification/materials/payment-instruction-change-pack",
        "artifactUrl": "https://trading4ai.com/reliability/public-materials/payment-instruction-change-pack.json",
        "artifactVersion": "public-material-payment-instruction-change-pack-2026-05-25",
        "generatedAt": "2026-05-25T00:00:00.000Z",
        "staticSnapshotAt": "2026-05-25T00:00:00.000Z",
        "sourceSnapshotAt": "2026-05-25T00:00:00.000Z",
        "recommendedCitationText": "Payment instruction change before settlement, public-material-payment-instruction-change-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/payment-instruction-change-pack"
      },
      "citationBlock": [
        "artifactVersion=public-material-payment-instruction-change-pack-2026-05-25",
        "generatedAt=2026-05-25T00:00:00.000Z",
        "staticSnapshotAt=2026-05-25T00:00:00.000Z",
        "sampleEvidenceRetrievedAt=2026-05-25T00:00:00.000Z",
        "pagePath=/agent-verification/materials/payment-instruction-change-pack",
        "artifactPath=/reliability/public-materials/payment-instruction-change-pack.json"
      ],
      "keyFindings": [
        "warning: The changed beneficiary name no longer matches the supplier name on the last verified invoice and onboarding record (The new instruction swaps the stored supplier entity for a new payee name that has not been independently tied to the vendor.)",
        "warning: The payment-change request arrived from a new email thread and was not confirmed in the previously trusted supplier portal (The approved settlement workflow uses the supplier portal, but the change request came from a side-channel message.)",
        "unresolved: No signed bank letter, portal confirmation, or wallet-ownership record ties the new destination to the claimed supplier (The request includes urgency language but no document that proves the beneficiary or wallet change is legitimate.)",
        "unresolved: Destination-integrity fields are incomplete across SWIFT, IBAN, routing, account number, wallet chain, memo, tag, and destination tag (The agent cannot compare the prior payment rail to the new bank or wallet destination because key account number, wallet chain, memo, and destination tag fields are missing.)",
        "warning: The message asks for same-day settlement and says the old finance contact should not be called (Urgency plus secrecy is a clear escalation signal, not supporting evidence for the payment change.)",
        "warning: FBI Business Email Compromise (BEC) guidance remains a required reference for payment-instruction change risk (The FBI source supports treating changed payment instructions and compromised communication channels as high-risk; this static pack does not run a live fraud check.)",
        "warning: FTC consumer alert coverage remains relevant when payment instructions arrive through suspicious or impersonation-style channels (The FTC source is public warning context for suspicious payment and impersonation patterns; it does not approve a changed payment instruction or clear a beneficiary.)",
        "unresolved: FinCEN e-mail compromise fraud advisory remains a required reference for suspicious wire-transfer instruction changes (The FinCEN advisory is cited as official guidance for wire and e-mail compromise patterns; the sample does not replace bank, treasury, or compliance review.)"
      ],
      "requiredDisclosures": [
        "Static public sample only; not a live review, approval, compliance clearance, or request-time judgment.",
        "Runs as a static/client-side demo in this phase, not a server-side decision service",
        "Does not prove an action is legal, safe, suitable, profitable, or compliant",
        "High-risk or ambiguous actions still require qualified human review",
        "The pack does not verify beneficial ownership, authenticate the sender fully, or replace treasury, legal, banking, or sanctions workflows.",
        "The new beneficiary or wallet destination is not independently tied to the previously verified supplier identity.",
        "The instruction change did not arrive through the known-good portal or verified finance contact path.",
        "No ownership document or signed change record supports the new destination before settlement.",
        "FBI BEC and FinCEN e-mail compromise guidance are source requirements for this pattern, not live clearance results."
      ],
      "doNotClaim": [
        "The new payment instruction is safe.",
        "The changed beneficiary is verified and settlement can proceed.",
        "No further review is needed because the new account details were sent before cut-off."
      ]
    },
    "actionRouting": {
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement",
      "serviceId": "action-preflight",
      "serviceName": "Action Preflight",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "actionType": "payment_instruction_change_before_settlement",
      "preflightStage": "before_settlement_or_release",
      "defaultPosture": "block",
      "primaryActionRisk": "Changed payment instructions can redirect funds before channel integrity, beneficiary ownership, and destination details are verified.",
      "routeWhen": [
        "A user or agent receives changed bank, wire, invoice, wallet, memo, tag, or destination instructions before settlement.",
        "The request includes urgency, secrecy, channel mismatch, beneficiary mismatch, or newly introduced payment rails."
      ],
      "stopOrEscalateWhen": [
        "Known-good channel confirmation, beneficiary ownership, prior payment rail comparison, or dual approval is missing.",
        "SWIFT, IBAN, routing, account number, wallet chain, memo, tag, destination tag, or settlement cut-off details are incomplete."
      ],
      "minimumInputFieldIds": [
        "prior_payment_instruction",
        "changed_instruction",
        "known_good_confirmation",
        "payment_destination"
      ],
      "minimumRequiredInputs": [
        "Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.",
        "New or changed instruction details, including channel received, timestamp, sender identity, and exact destination fields.",
        "Known-good confirmation channel and second-approver evidence that is independent of the changed instruction.",
        "Settlement amount, cut-off time, jurisdiction, and whether the change creates urgency or secrecy pressure."
      ],
      "missingInputFallback": "Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete."
    },
    "inputFieldGlossary": [
      {
        "fieldId": "prior_payment_instruction",
        "label": "Prior payment instruction",
        "description": "The last approved beneficiary, bank, wallet, rail, memo/tag, or settlement instruction on record.",
        "whyItMatters": "Changed payment details can only be assessed against a known-good baseline.",
        "exampleValues": [
          "previous IBAN",
          "previous wallet",
          "approved vendor master record",
          "last paid beneficiary"
        ],
        "usedByActionTypes": [
          "payment_instruction_change_before_settlement"
        ],
        "missingInputRisk": "The agent cannot tell whether a destination change is normal, suspicious, or unverifiable."
      },
      {
        "fieldId": "changed_instruction",
        "label": "Changed instruction",
        "description": "The new payment instruction plus sender, channel, timestamp, destination fields, and urgency context.",
        "whyItMatters": "Payment redirection attacks often arrive through channel changes, urgency, or incomplete destination details.",
        "exampleValues": [
          "new account number",
          "new wallet",
          "email timestamp",
          "sender identity",
          "changed settlement rail"
        ],
        "usedByActionTypes": [
          "payment_instruction_change_before_settlement"
        ],
        "missingInputRisk": "The agent may approve an untraceable change without confirming what actually changed."
      },
      {
        "fieldId": "known_good_confirmation",
        "label": "Known-good confirmation",
        "description": "Independent confirmation through a previously trusted channel or second approver.",
        "whyItMatters": "The confirmation path must not depend on the same message that requested the risky change.",
        "exampleValues": [
          "call-back number on file",
          "vendor portal confirmation",
          "second approver",
          "known contact channel"
        ],
        "usedByActionTypes": [
          "payment_instruction_change_before_settlement"
        ],
        "missingInputRisk": "The agent may accept attacker-controlled confirmation as real approval."
      },
      {
        "fieldId": "payment_destination",
        "label": "Payment destination",
        "description": "The bank account, wallet address, checkout link, invoice beneficiary, or settlement rail that would receive funds.",
        "whyItMatters": "High-risk financial actions become irreversible once money moves to the wrong destination.",
        "exampleValues": [
          "bank account",
          "wallet address",
          "subscription checkout URL",
          "invoice beneficiary"
        ],
        "usedByActionTypes": [
          "crypto_signal_subscription_payment",
          "counterparty_payment_review",
          "payment_instruction_change_before_settlement"
        ],
        "missingInputRisk": "The agent cannot compare the destination against the named counterparty or prior approved instructions."
      }
    ],
    "preflightQuestionnaire": {
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement",
      "actionType": "payment_instruction_change_before_settlement",
      "preflightStage": "before_settlement_or_release",
      "defaultPosture": "block",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "completionRule": "Answer every question with source-bound evidence before upgrading the review posture; if any required input is missing, apply the missing-input fallback and do not treat the static pack as approval.",
      "questions": [
        {
          "fieldId": "prior_payment_instruction",
          "label": "Prior payment instruction",
          "prompt": "What evidence identifies the prior payment instruction for this payment_instruction_change_before_settlement review?",
          "acceptableEvidence": [
            "previous IBAN",
            "previous wallet",
            "approved vendor master record",
            "last paid beneficiary"
          ],
          "ifMissing": "The agent cannot tell whether a destination change is normal, suspicious, or unverifiable. Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete."
        },
        {
          "fieldId": "changed_instruction",
          "label": "Changed instruction",
          "prompt": "What evidence identifies the changed instruction for this payment_instruction_change_before_settlement review?",
          "acceptableEvidence": [
            "new account number",
            "new wallet",
            "email timestamp",
            "sender identity",
            "changed settlement rail"
          ],
          "ifMissing": "The agent may approve an untraceable change without confirming what actually changed. Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete."
        },
        {
          "fieldId": "known_good_confirmation",
          "label": "Known-good confirmation",
          "prompt": "What evidence identifies the known-good confirmation for this payment_instruction_change_before_settlement review?",
          "acceptableEvidence": [
            "call-back number on file",
            "vendor portal confirmation",
            "second approver",
            "known contact channel"
          ],
          "ifMissing": "The agent may accept attacker-controlled confirmation as real approval. Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete."
        },
        {
          "fieldId": "payment_destination",
          "label": "Payment destination",
          "prompt": "What evidence identifies the payment destination for this payment_instruction_change_before_settlement review?",
          "acceptableEvidence": [
            "bank account",
            "wallet address",
            "subscription checkout URL",
            "invoice beneficiary"
          ],
          "ifMissing": "The agent cannot compare the destination against the named counterparty or prior approved instructions. Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete."
        }
      ]
    },
    "preflightDecisionPolicy": {
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement",
      "actionType": "payment_instruction_change_before_settlement",
      "defaultPosture": "block",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "proceedOnlyWhen": [
        "Collected and cited: Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.",
        "Collected and cited: New or changed instruction details, including channel received, timestamp, sender identity, and exact destination fields.",
        "Collected and cited: Known-good confirmation channel and second-approver evidence that is independent of the changed instruction.",
        "Collected and cited: Settlement amount, cut-off time, jurisdiction, and whether the change creates urgency or secrecy pressure."
      ],
      "fallbackWhenMissingInputs": "Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete.",
      "stopOrEscalateWhen": [
        "Known-good channel confirmation, beneficiary ownership, prior payment rail comparison, or dual approval is missing.",
        "SWIFT, IBAN, routing, account number, wallet chain, memo, tag, destination tag, or settlement cut-off details are incomplete.",
        "The beneficiary, bank account, or wallet destination changes shortly before settlement.",
        "The change request arrives through a side channel, new domain, forwarded thread, or private message instead of the known approved route.",
        "The request uses urgency, secrecy, or exception language to discourage verification through the normal approval path."
      ],
      "allowedStaticOutput": "Checked the changed payment instruction against the cited sample records and warning sources at the listed retrieval time; settlement remains blocked and under settlement hold because beneficiary, known-good channel, destination integrity, ownership, and dual approval checks are still unresolved.",
      "blockedStaticOutput": "The new payment instruction is verified, safe, and approved for settlement.",
      "humanEscalationRule": "Escalate to human review when any stop-or-escalate rule applies, when required evidence is missing, or when the requested action would treat this static pack as approval, clearance, execution advice, or live screening."
    },
    "decisionGuardrails": [
      {
        "packId": "payment_instruction_change_pack",
        "guardrailId": "payment_instruction_change_pack_missing_minimum_inputs",
        "severity": "escalate",
        "condition": "One or more minimum inputs are missing or uncited: Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.; New or changed instruction details, including channel received, timestamp, sender identity, and exact destination fields.; Known-good confirmation channel and second-approver evidence that is independent of the changed instruction.; Settlement amount, cut-off time, jurisdiction, and whether the change creates urgency or secrecy pressure..",
        "requiredAgentAction": "Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete.",
        "allowedStaticOutput": "Checked the changed payment instruction against the cited sample records and warning sources at the listed retrieval time; settlement remains blocked and under settlement hold because beneficiary, known-good channel, destination integrity, ownership, and dual approval checks are still unresolved.",
        "blockedOutputUpgrade": "The new payment instruction is verified, safe, and approved for settlement.",
        "evidenceFieldIds": [
          "prior_payment_instruction",
          "changed_instruction",
          "known_good_confirmation",
          "payment_destination"
        ],
        "sourceBoundary": "Static public material only; preserve source URLs, retrieval time, artifact version, limitations, and unresolved items. Do not upgrade this pack into live clearance, approval, execution advice, compliance sign-off, or backtesting.",
        "humanReviewRequired": true
      },
      {
        "packId": "payment_instruction_change_pack",
        "guardrailId": "payment_instruction_change_pack_stop_or_escalate_trigger",
        "severity": "block",
        "condition": "Any stop-or-escalate trigger applies: Known-good channel confirmation, beneficiary ownership, prior payment rail comparison, or dual approval is missing.; SWIFT, IBAN, routing, account number, wallet chain, memo, tag, destination tag, or settlement cut-off details are incomplete.; The beneficiary, bank account, or wallet destination changes shortly before settlement.; The change request arrives through a side channel, new domain, forwarded thread, or private message instead of the known approved route.; The request uses urgency, secrecy, or exception language to discourage verification through the normal approval path..",
        "requiredAgentAction": "Stop automatic action, keep the unresolved risk visible, and route the item to human review before payment, publication, execution, or downstream trust transfer.",
        "allowedStaticOutput": "The payment-change request is still blocked because the new destination has not been independently matched to the known supplier record. This pack can describe what changed and what was checked, but it does not approve the new instruction or clear the counterparty. Urgency or secrecy language remains a risk flag until the beneficiary and channel are independently verified.",
        "blockedOutputUpgrade": "The new payment instruction is safe. The changed beneficiary is verified and settlement can proceed. No further review is needed because the new account details were sent before cut-off.",
        "evidenceFieldIds": [
          "prior_payment_instruction",
          "changed_instruction",
          "known_good_confirmation",
          "payment_destination"
        ],
        "sourceBoundary": "Static public material only; preserve source URLs, retrieval time, artifact version, limitations, and unresolved items. Do not upgrade this pack into live clearance, approval, execution advice, compliance sign-off, or backtesting.",
        "humanReviewRequired": true
      },
      {
        "packId": "payment_instruction_change_pack",
        "guardrailId": "payment_instruction_change_pack_safe_static_output_boundary",
        "severity": "allow_with_limits",
        "condition": "All minimum inputs are collected, cited, and no stop-or-escalate trigger applies; the output still remains a bounded static material summary.",
        "requiredAgentAction": "Emit only source-bound, timestamped, limitation-preserving static output and carry unresolved items into the final note.",
        "allowedStaticOutput": "Checked the changed payment instruction against the cited sample records and warning sources at the listed retrieval time; settlement remains blocked and under settlement hold because beneficiary, known-good channel, destination integrity, ownership, and dual approval checks are still unresolved.",
        "blockedOutputUpgrade": "The new payment instruction is verified, safe, and approved for settlement.",
        "evidenceFieldIds": [
          "prior_payment_instruction",
          "changed_instruction",
          "known_good_confirmation",
          "payment_destination"
        ],
        "sourceBoundary": "Static public material only; preserve source URLs, retrieval time, artifact version, limitations, and unresolved items. Do not upgrade this pack into live clearance, approval, execution advice, compliance sign-off, or backtesting.",
        "humanReviewRequired": false
      }
    ],
    "staticActionNoteTemplate": {
      "packId": "payment_instruction_change_pack",
      "templateId": "payment_instruction_change_pack_static_action_note_template",
      "title": "Payment instruction change before settlement",
      "actionType": "payment_instruction_change_before_settlement",
      "defaultPosture": "block",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "outputName": "Payment instruction change before settlement static action note",
      "allowedUse": "Use only as a static, source-bound Action Preflight note after completing action routing, the preflight questionnaire, and the decision policy.",
      "minimumInputFieldIds": [
        "prior_payment_instruction",
        "changed_instruction",
        "known_good_confirmation",
        "payment_destination"
      ],
      "evidenceToCollect": [
        "The original invoice, prior beneficiary record, and the exact changed payment instruction text or attachment.",
        "The verified channel history showing which email domain, portal, phone number, or wallet record was previously trusted.",
        "The prior payment rail and destination-integrity fields: SWIFT or IBAN, routing number, account number, wallet address, wallet chain, memo, tag, destination tag, and settlement cut-off.",
        "Any bank letter, supplier-portal confirmation, signed change notice, or dual-approval record tying the new beneficiary or wallet to the known counterparty.",
        "Timestamped notes for every mismatch across beneficiary name, account number, wallet address, invoice number, approver, and approval chain."
      ],
      "deliveryOutputs": [
        "A bounded summary of what changed across beneficiary, channel, and invoice metadata.",
        "A block-or-review recommendation that keeps settlement paused while key evidence remains unresolved.",
        "A concrete destination-integrity checklist covering bank rail fields, wallet rail fields, known-good channel proof, dual-control review, and settlement hold status.",
        "Safe wording that states the evidence status without upgrading it into approval or counterparty clearance."
      ],
      "sections": [
        {
          "sectionId": "action_context",
          "title": "Action context",
          "required": true,
          "guidance": "State the action type, preflight stage, default posture, and collected minimum inputs: Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.; New or changed instruction details, including channel received, timestamp, sender identity, and exact destination fields.; Known-good confirmation channel and second-approver evidence that is independent of the changed instruction.; Settlement amount, cut-off time, jurisdiction, and whether the change creates urgency or secrecy pressure.."
        },
        {
          "sectionId": "source_bound_evidence",
          "title": "Source-bound evidence",
          "required": true,
          "guidance": "List only cited evidence collected for this pack: The original invoice, prior beneficiary record, and the exact changed payment instruction text or attachment.; The verified channel history showing which email domain, portal, phone number, or wallet record was previously trusted.; The prior payment rail and destination-integrity fields: SWIFT or IBAN, routing number, account number, wallet address, wallet chain, memo, tag, destination tag, and settlement cut-off.; Any bank letter, supplier-portal confirmation, signed change notice, or dual-approval record tying the new beneficiary or wallet to the known counterparty.; Timestamped notes for every mismatch across beneficiary name, account number, wallet address, invoice number, approver, and approval chain.."
        },
        {
          "sectionId": "decision_policy",
          "title": "Decision policy",
          "required": true,
          "guidance": "Apply fallback 'Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete.' and stop/escalate when any policy trigger applies."
        },
        {
          "sectionId": "safe_restatement",
          "title": "Safe restatement",
          "required": true,
          "guidance": "Use bounded language no stronger than: Checked the changed payment instruction against the cited sample records and warning sources at the listed retrieval time; settlement remains blocked and under settlement hold because beneficiary, known-good channel, destination integrity, ownership, and dual approval checks are still unresolved."
        },
        {
          "sectionId": "blocked_language",
          "title": "Blocked language",
          "required": true,
          "guidance": "Do not restate or imply: The new payment instruction is verified, safe, and approved for settlement."
        },
        {
          "sectionId": "citation_trail",
          "title": "Citation trail",
          "required": true,
          "guidance": "Preserve citation requirements: Tie every restated payment-change fact to the exact source note, invoice record, or warning source plus retrieval time.; Separate observed mismatches from interpretation; do not convert a partial match, no-hit result, or silence into trust.; Keep beneficiary, channel, and ownership uncertainty visible in every summary until the change is independently verified.; Never restate this pack as evidence that the new payment instruction is safe, approved, or compliant.."
        }
      ],
      "citationRequirements": [
        "Tie every restated payment-change fact to the exact source note, invoice record, or warning source plus retrieval time.",
        "Separate observed mismatches from interpretation; do not convert a partial match, no-hit result, or silence into trust.",
        "Keep beneficiary, channel, and ownership uncertainty visible in every summary until the change is independently verified.",
        "Never restate this pack as evidence that the new payment instruction is safe, approved, or compliant."
      ],
      "prohibitedUses": [
        "The new payment instruction is safe.",
        "The changed beneficiary is verified and settlement can proceed.",
        "No further review is needed because the new account details were sent before cut-off."
      ],
      "finalBoundaryStatement": "This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision."
    },
    "staticActionNoteExample": {
      "packId": "payment_instruction_change_pack",
      "exampleId": "payment_instruction_change_pack_static_action_note_example",
      "templateId": "payment_instruction_change_pack_static_action_note_template",
      "title": "Payment instruction change before settlement static action note example",
      "actionType": "payment_instruction_change_before_settlement",
      "defaultPosture": "block",
      "noteStatus": "block",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "sourceSnapshotAt": "2026-05-25T00:00:00.000Z",
      "citedEvidenceRecordIds": [
        "beneficiary_name_mismatch",
        "unverified_channel_switch",
        "ownership_proof_missing",
        "destination_integrity_gap",
        "urgency_and_secrecy_pressure",
        "fbi_bec_source_required",
        "ftc_consumer_alert_source_required",
        "fincen_email_compromise_source_required"
      ],
      "sections": [
        {
          "sectionId": "action_context",
          "title": "Action context",
          "body": "Draft settlement request: an accounts-payable agent receives new wire and wallet instructions for an existing supplier two hours before cut-off, with a note saying the old finance contact should not be called. Action type: payment_instruction_change_before_settlement. Default posture: block. Minimum inputs: Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.; New or changed instruction details, including channel received, timestamp, sender identity, and exact destination fields.; Known-good confirmation channel and second-approver evidence that is independent of the changed instruction.; Settlement amount, cut-off time, jurisdiction, and whether the change creates urgency or secrecy pressure..",
          "citationPointers": [
            "sampleInputSummary",
            "actionTaxonomy",
            "minimumRequiredInputs"
          ]
        },
        {
          "sectionId": "source_bound_evidence",
          "title": "Source-bound evidence",
          "body": "warning: The changed beneficiary name no longer matches the supplier name on the last verified invoice and onboarding record. The new instruction swaps the stored supplier entity for a new payee name that has not been independently tied to the vendor. warning: The payment-change request arrived from a new email thread and was not confirmed in the previously trusted supplier portal. The approved settlement workflow uses the supplier portal, but the change request came from a side-channel message. unresolved: No signed bank letter, portal confirmation, or wallet-ownership record ties the new destination to the claimed supplier. The request includes urgency language but no document that proves the beneficiary or wallet change is legitimate. unresolved: Destination-integrity fields are incomplete across SWIFT, IBAN, routing, account number, wallet chain, memo, tag, and destination tag. The agent cannot compare the prior payment rail to the new bank or wallet destination because key account number, wallet chain, memo, and destination tag fields are missing. warning: The message asks for same-day settlement and says the old finance contact should not be called. Urgency plus secrecy is a clear escalation signal, not supporting evidence for the payment change. warning: FBI Business Email Compromise (BEC) guidance remains a required reference for payment-instruction change risk. The FBI source supports treating changed payment instructions and compromised communication channels as high-risk; this static pack does not run a live fraud check. warning: FTC consumer alert coverage remains relevant when payment instructions arrive through suspicious or impersonation-style channels. The FTC source is public warning context for suspicious payment and impersonation patterns; it does not approve a changed payment instruction or clear a beneficiary. unresolved: FinCEN e-mail compromise fraud advisory remains a required reference for suspicious wire-transfer instruction changes. The FinCEN advisory is cited as official guidance for wire and e-mail compromise patterns; the sample does not replace bank, treasury, or compliance review.",
          "citationPointers": [
            "beneficiary_name_mismatch:/agent-verification/materials/payment-instruction-change-pack",
            "unverified_channel_switch:/agent-verification/materials/payment-instruction-change-pack",
            "ownership_proof_missing:/agent-verification/materials/payment-instruction-change-pack",
            "destination_integrity_gap:/agent-verification/materials/payment-instruction-change-pack",
            "urgency_and_secrecy_pressure:https://www.cisa.gov/news-events/news/business-email-compromise",
            "fbi_bec_source_required:https://www.fbi.gov/how-we-can-help-you/scams-and-safety/common-frauds-and-scams/business-email-compromise",
            "ftc_consumer_alert_source_required:https://consumer.ftc.gov/consumer-alerts",
            "fincen_email_compromise_source_required:https://www.fincen.gov/resources/statutes-regulations/guidance/advisory-financial-institutions-e-mail-compromise-fraud"
          ]
        },
        {
          "sectionId": "decision_policy",
          "title": "Decision policy",
          "body": "block: The changed payment instruction remains blocked because beneficiary ownership, channel legitimacy, and urgency pressure are unresolved. Unresolved items: The new beneficiary or wallet destination is not independently tied to the previously verified supplier identity.; The instruction change did not arrive through the known-good portal or verified finance contact path.; No ownership document or signed change record supports the new destination before settlement.; FBI BEC and FinCEN e-mail compromise guidance are source requirements for this pattern, not live clearance results. Required follow-up: Reconfirm the payment change through a previously verified vendor channel or portal before any settlement proceeds.; Capture the exact beneficiary mismatch, timing pressure, channel mismatch, and official BEC/wire-fraud warning references in the final evidence note.; Escalate to human treasury review and keep payment blocked until the ownership chain and approval route are verified..",
          "citationPointers": [
            "sampleReviewOutput.verdict",
            "sampleReviewOutput.unresolvedItems",
            "sampleReviewOutput.requiredFollowUp"
          ]
        },
        {
          "sectionId": "safe_restatement",
          "title": "Safe restatement",
          "body": "Checked the changed payment instruction against the cited sample records and warning sources at the listed retrieval time; settlement remains blocked and under settlement hold because beneficiary, known-good channel, destination integrity, ownership, and dual approval checks are still unresolved.",
          "citationPointers": [
            "sampleReviewOutput.safeRestatement"
          ]
        },
        {
          "sectionId": "blocked_language",
          "title": "Blocked language",
          "body": "The new payment instruction is verified, safe, and approved for settlement.",
          "citationPointers": [
            "sampleReviewOutput.blockedRestatement",
            "blockedStatements"
          ]
        },
        {
          "sectionId": "citation_trail",
          "title": "Citation trail",
          "body": "Payment instruction change before settlement, public-material-payment-instruction-change-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/payment-instruction-change-pack Citation requirements: Tie every restated payment-change fact to the exact source note, invoice record, or warning source plus retrieval time.; Separate observed mismatches from interpretation; do not convert a partial match, no-hit result, or silence into trust.; Keep beneficiary, channel, and ownership uncertainty visible in every summary until the change is independently verified.; Never restate this pack as evidence that the new payment instruction is safe, approved, or compliant..",
          "citationPointers": [
            "artifactVersion:public-material-payment-instruction-change-pack-2026-05-25",
            "sourceSnapshotAt:2026-05-25T00:00:00.000Z",
            "/reliability/public-materials/payment-instruction-change-pack.json"
          ]
        }
      ],
      "finalBoundaryStatement": "This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision."
    },
    "agentWorkflow": {
      "packId": "payment_instruction_change_pack",
      "workflowId": "payment_instruction_change_pack_agent_workflow",
      "title": "Payment instruction change before settlement agent workflow",
      "serviceId": "action-preflight",
      "serviceName": "Action Preflight",
      "actionType": "payment_instruction_change_before_settlement",
      "defaultPosture": "block",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "stepIds": [
        "select_pack",
        "collect_minimum_inputs",
        "answer_preflight_questionnaire",
        "apply_decision_policy",
        "draft_static_action_note",
        "cite_and_escalate"
      ],
      "minimumInputFieldIds": [
        "prior_payment_instruction",
        "changed_instruction",
        "known_good_confirmation",
        "payment_destination"
      ],
      "questionCount": 4,
      "linkedArtifacts": {
        "actionRoutingActionType": "payment_instruction_change_before_settlement",
        "preflightQuestionnairePackId": "payment_instruction_change_pack",
        "preflightDecisionPolicyPackId": "payment_instruction_change_pack",
        "staticActionNoteTemplateId": "payment_instruction_change_pack_static_action_note_template",
        "staticActionNoteExampleId": "payment_instruction_change_pack_static_action_note_example",
        "sourceManifestCount": 5,
        "canonicalCitationText": "Payment instruction change before settlement, public-material-payment-instruction-change-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/payment-instruction-change-pack"
      },
      "recommendedUse": [
        "Select this workflow when the action type matches the user's requested financial action.",
        "Collect every minimum input field before upgrading the posture or drafting user-facing language.",
        "Use the filled static action note example as a format reference, not as a live decision for a new user request."
      ],
      "nonGoals": [
        "This workflow is not a live screening, approval, clearance, execution, trading, backtesting, or compliance decision.",
        "This workflow does not fetch fresh third-party sources or validate user-submitted data at request time.",
        "This workflow does not replace qualified human review for high-risk payments, transfers, claims, filings, or macro interpretation."
      ],
      "escalationRule": "Escalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees."
    },
    "machineSummary": {
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement",
      "serviceId": "action-preflight",
      "serviceName": "Action Preflight",
      "actionType": "payment_instruction_change_before_settlement",
      "defaultPosture": "block",
      "pageUrl": "https://trading4ai.com/agent-verification/materials/payment-instruction-change-pack",
      "artifactUrl": "https://trading4ai.com/reliability/public-materials/payment-instruction-change-pack.json",
      "sourceSnapshotAt": "2026-05-25T00:00:00.000Z",
      "minimumInputFieldIds": [
        "prior_payment_instruction",
        "changed_instruction",
        "known_good_confirmation",
        "payment_destination"
      ],
      "agentUse": [
        "Open the HTML page first for scope, limitations, source freshness, and scenario fit.",
        "Use the JSON artifact for structured retrieval after the page boundary is understood.",
        "Carry the canonical citation, source snapshot, limitations, and unresolved items into downstream summaries."
      ],
      "doNotUseAs": [
        "live screening",
        "payment approval",
        "compliance clearance",
        "trading or execution advice",
        "proof that a counterparty, wallet, claim, filing, or macro interpretation is safe"
      ],
      "decisionMatrixCount": 4,
      "decisionMatrixLabels": [
        "Prior payment instruction row",
        "Changed instruction and sender row",
        "Independent confirmation row",
        "Urgency and timing risk row"
      ],
      "evidenceVerificationStepCount": 5,
      "evidenceVerificationStepLabels": [
        "Source manifest verification",
        "Evidence record linkage check",
        "Decision matrix boundary check",
        "Canonical citation and timestamp check",
        "Human escalation and blocked-upgrade check"
      ],
      "misusePatternCount": 2,
      "misusePatternLabels": [
        "Static sample treated as live result",
        "Missing inputs smoothed into confident output"
      ],
      "sourceReviewPolicy": {
        "policyId": "payment_instruction_change_pack_source_review_policy",
        "packId": "payment_instruction_change_pack",
        "title": "Payment instruction change before settlement",
        "serviceId": "action-preflight",
        "serviceName": "Action Preflight",
        "actionType": "payment_instruction_change_before_settlement",
        "staticOnly": true,
        "sourceSnapshotAt": "2026-05-25T00:00:00.000Z",
        "reviewCadenceDays": 60,
        "nextRecommendedReviewAt": "2026-07-24T00:00:00.000Z",
        "freshnessStatus": "current_static_snapshot",
        "sourceReviewMode": "manual_public_source_recheck_required",
        "refreshRequiredWhen": [
          "Any cited official source, registry, guidance page, filing page, or public warning URL changes content, schema, access status, or meaning.",
          "A downstream agent wants to use the static pack for a new counterparty, payment destination, wallet, claim, filing, macro release, or source set.",
          "The current date is past nextRecommendedReviewAt or the artifactVersion / generatedAt fields are removed from the handoff.",
          "The beneficiary, bank rail, wallet destination, known-good confirmation channel, or fraud-warning source differs from the static sample."
        ],
        "staleSignals": [
          "A source URL no longer resolves, redirects to unrelated content, or changes field definitions.",
          "The pack is being reused after nextRecommendedReviewAt without a fresh official-source review.",
          "A user or agent treats this static snapshot as live screening, live clearance, or final approval."
        ],
        "agentActionWhenPastReview": "Re-check the cited official/public sources, preserve new retrieval timestamps, regenerate or version the artifact, and keep the output at review/escalate until source freshness is restored.",
        "staticUseBoundary": "This is a static source-review policy for a pre-generated public material pack; it is not live screening, request-time judgment, compliance clearance, payment approval, or trading advice.",
        "generatedAt": "2026-05-25T00:00:00.000Z"
      },
      "canonicalCitationText": "Payment instruction change before settlement, public-material-payment-instruction-change-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/payment-instruction-change-pack"
    },
    "evidenceVerificationRecipe": {
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement evidence verification recipe",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "defaultPosture": "block",
      "staticOnly": true,
      "steps": [
        {
          "stepId": "payment_instruction_change_pack_source_manifest_verification",
          "label": "Source manifest verification",
          "verificationAction": "Check the static source manifest before citing this pack. Source kinds: sample_page, official_guidance. Source labels: Verified supplier record (sample), CISA Business Email Compromise guidance, FBI Business Email Compromise guidance, FTC consumer alerts, FinCEN e-mail compromise fraud advisory for financial institutions.",
          "trustBoundary": "The source manifest is a static citation map, not live clearance, approval, compliance review, execution advice, or backtesting evidence.",
          "failureMode": "If a cited source, retrieval time, source role, or evidence record link is missing, keep the output bounded and escalate before upgrading the claim.",
          "requiredCitationFields": [
            "sourceManifest[].url",
            "sourceManifest[].retrievedAt",
            "sourceManifest[].kind",
            "sampleEvidenceRecords[].id"
          ]
        },
        {
          "stepId": "payment_instruction_change_pack_evidence_record_linkage",
          "label": "Evidence record linkage check",
          "verificationAction": "Match each sample evidence record to a sourceManifest evidenceRecordIds entry, then preserve the record status, note, source label, source URL, and retrievedAt value.",
          "trustBoundary": "A sample record explains the static example only; it does not prove the current counterparty, claim, payment, wallet, filing, macro release, or subscription is safe.",
          "failureMode": "If a record cannot be linked to its source manifest row, do not reuse it as evidence and keep the final output unresolved.",
          "requiredCitationFields": [
            "sampleEvidenceRecords[].id",
            "sampleEvidenceRecords[].status",
            "sampleEvidenceRecords[].sourceUrl",
            "sampleEvidenceRecords[].retrievedAt",
            "sourceManifest[].evidenceRecordIds"
          ]
        },
        {
          "stepId": "payment_instruction_change_pack_decision_matrix_boundary_check",
          "label": "Decision matrix boundary check",
          "verificationAction": "Read all 4 decision matrix rows and carry their allowedStaticUse, blockedUpgrade, and agentAction fields into any downstream summary.",
          "trustBoundary": "Decision matrix rows define allowed static reuse and blocked upgrades; they are not automatic live approval, live screening, compliance sign-off, or execution permission.",
          "failureMode": "If a downstream sentence conflicts with a blockedUpgrade row, block or rewrite the sentence and escalate when money, publication, or user action is involved.",
          "requiredCitationFields": [
            "decisionMatrix[].matrixId",
            "decisionMatrix[].status",
            "decisionMatrix[].allowedStaticUse",
            "decisionMatrix[].blockedUpgrade"
          ]
        },
        {
          "stepId": "payment_instruction_change_pack_canonical_citation_check",
          "label": "Canonical citation and timestamp check",
          "verificationAction": "Preserve the canonical citation text, artifact version, generatedAt, staticSnapshotAt, sourceSnapshotAt, and all source retrievedAt values when citing this pack.",
          "trustBoundary": "A citation proves the static artifact and source snapshot were recorded; it does not prove the facts are current beyond the listed timestamps.",
          "failureMode": "If artifact version, generatedAt, sourceSnapshotAt, or source retrievedAt values are removed, the output is no longer evidence-bound.",
          "requiredCitationFields": [
            "canonicalCitation.recommendedCitationText",
            "artifactProvenance.artifactVersion",
            "artifactProvenance.generatedAt",
            "canonicalCitation.sourceSnapshotAt",
            "sourceManifest[].retrievedAt"
          ]
        },
        {
          "stepId": "payment_instruction_change_pack_human_escalation_boundary",
          "label": "Human escalation and blocked-upgrade check",
          "verificationAction": "Compare the final output with the pack's blockedStatements, sampleReviewOutput.blockedRestatement, escalationTriggers, and actionTaxonomy.stopOrEscalateWhen fields.",
          "trustBoundary": "Static public material may explain evidence and limitations, but it must not become live clearance, legal compliance, suitability, safety, guarantee, payment approval, publication approval, or trade advice.",
          "failureMode": "If the output asks a user or agent to move money, publish a financial claim, trust a counterparty, or treat the material as live approval, stop and escalate to human review.",
          "requiredCitationFields": [
            "canonicalCitation.recommendedCitationText",
            "artifactProvenance.artifactVersion",
            "blockedStatements[]",
            "sampleReviewOutput.blockedRestatement",
            "escalationTriggers[]",
            "actionTaxonomy.stopOrEscalateWhen[]"
          ]
        }
      ]
    },
    "misusePatterns": [
      {
        "packId": "payment_instruction_change_pack",
        "patternId": "payment_instruction_change_pack_static_sample_as_live_result",
        "label": "Static sample treated as live result",
        "severity": "escalate",
        "falseSignal": "The static pack contains a sample output, so the agent treats it as a fresh review of a new user request.",
        "whyMisleading": "Static public materials are pre-generated examples and do not fetch fresh sources, inspect private user data, or perform request-time judgment.",
        "safeAlternative": "Use the pack as a format and boundary reference, then collect fresh source-bound evidence before making a case-specific note.",
        "blockedAgentAction": "Do not present the static sample as live approval, clearance, execution advice, or a completed review of the current case.",
        "evidenceFieldIds": [
          "prior_payment_instruction",
          "changed_instruction",
          "known_good_confirmation",
          "payment_destination"
        ],
        "relatedDecisionMatrixIds": [
          "payment_instruction_change_pack_prior_instruction_row",
          "payment_instruction_change_pack_changed_instruction_row",
          "payment_instruction_change_pack_confirmation_row",
          "payment_instruction_change_pack_urgency_and_timing_row"
        ],
        "relatedGuardrailIds": [
          "payment_instruction_change_pack_missing_minimum_inputs",
          "payment_instruction_change_pack_stop_or_escalate_trigger",
          "payment_instruction_change_pack_safe_static_output_boundary"
        ]
      },
      {
        "packId": "payment_instruction_change_pack",
        "patternId": "payment_instruction_change_pack_missing_inputs_smoothed_over",
        "label": "Missing inputs smoothed into confident output",
        "severity": "warning",
        "falseSignal": "The agent has partial source context and writes a fluent summary that hides missing required inputs.",
        "whyMisleading": "A fluent summary can transfer trust while required identifiers, source links, timestamps, or match semantics remain missing.",
        "safeAlternative": "Name missing inputs explicitly and apply the pack's missing-input fallback instead of upgrading the posture.",
        "blockedAgentAction": "Do not turn incomplete evidence into confident public language, payment action, publication, transfer, or downstream trust.",
        "evidenceFieldIds": [
          "prior_payment_instruction",
          "changed_instruction",
          "known_good_confirmation",
          "payment_destination"
        ],
        "relatedDecisionMatrixIds": [
          "payment_instruction_change_pack_prior_instruction_row",
          "payment_instruction_change_pack_changed_instruction_row",
          "payment_instruction_change_pack_confirmation_row",
          "payment_instruction_change_pack_urgency_and_timing_row"
        ],
        "relatedGuardrailIds": [
          "payment_instruction_change_pack_missing_minimum_inputs",
          "payment_instruction_change_pack_stop_or_escalate_trigger",
          "payment_instruction_change_pack_safe_static_output_boundary"
        ]
      }
    ],
    "sourceReviewPolicy": {
      "policyId": "payment_instruction_change_pack_source_review_policy",
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement",
      "serviceId": "action-preflight",
      "serviceName": "Action Preflight",
      "actionType": "payment_instruction_change_before_settlement",
      "staticOnly": true,
      "sourceSnapshotAt": "2026-05-25T00:00:00.000Z",
      "reviewCadenceDays": 60,
      "nextRecommendedReviewAt": "2026-07-24T00:00:00.000Z",
      "freshnessStatus": "current_static_snapshot",
      "sourceReviewMode": "manual_public_source_recheck_required",
      "refreshRequiredWhen": [
        "Any cited official source, registry, guidance page, filing page, or public warning URL changes content, schema, access status, or meaning.",
        "A downstream agent wants to use the static pack for a new counterparty, payment destination, wallet, claim, filing, macro release, or source set.",
        "The current date is past nextRecommendedReviewAt or the artifactVersion / generatedAt fields are removed from the handoff.",
        "The beneficiary, bank rail, wallet destination, known-good confirmation channel, or fraud-warning source differs from the static sample."
      ],
      "staleSignals": [
        "A source URL no longer resolves, redirects to unrelated content, or changes field definitions.",
        "The pack is being reused after nextRecommendedReviewAt without a fresh official-source review.",
        "A user or agent treats this static snapshot as live screening, live clearance, or final approval."
      ],
      "agentActionWhenPastReview": "Re-check the cited official/public sources, preserve new retrieval timestamps, regenerate or version the artifact, and keep the output at review/escalate until source freshness is restored.",
      "staticUseBoundary": "This is a static source-review policy for a pre-generated public material pack; it is not live screening, request-time judgment, compliance clearance, payment approval, or trading advice.",
      "generatedAt": "2026-05-25T00:00:00.000Z"
    },
    "caseReadinessChecklist": {
      "checklistId": "payment_instruction_change_pack_case_readiness_checklist",
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement case readiness checklist",
      "serviceId": "action-preflight",
      "serviceName": "Action Preflight",
      "actionType": "payment_instruction_change_before_settlement",
      "defaultPosture": "block",
      "staticOnly": true,
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "requiredEvidenceFieldIds": [
        "prior_payment_instruction",
        "changed_instruction",
        "known_good_confirmation",
        "payment_destination"
      ],
      "sourceFreshnessGate": "Before reuse, compare the case date and cited source retrieval plan with sourceReviewPolicy.nextRecommendedReviewAt=2026-07-24T00:00:00.000Z; if the static snapshot is stale, re-check sources and version the artifact before using it.",
      "mustConfirmBeforeUse": [
        "Collected and cited every minimum input field: prior_payment_instruction, changed_instruction, known_good_confirmation, payment_destination.",
        "Opened the HTML page for scope and limitations, then used the JSON artifact for structured retrieval.",
        "Preserved source URLs, retrieval timestamps, source roles, canonical citation text, and unresolved items in the downstream note.",
        "Checked decisionMatrix, misusePatterns, sourceReviewPolicy, and evidenceVerificationRecipe before upgrading any sentence.",
        "Confirm the pack's source manifest, sample evidence records, decision matrix, and citation rules still match the case being reviewed."
      ],
      "notReadySignals": [
        "One or more required evidence fields are missing, uncited, or unresolved: prior_payment_instruction, changed_instruction, known_good_confirmation, payment_destination.",
        "The case is past sourceReviewPolicy.nextRecommendedReviewAt without a fresh source re-check.",
        "The user or downstream agent asks for approval, clearance, safety, compliance, suitability, execution, payment, publication, or legal/trading advice.",
        "The requested case uses a new counterparty, payment destination, wallet, claim, filing, macro release, source set, or audience that is not covered by the static sample."
      ],
      "readyStaticHandoff": [
        "A bounded static action note or evidence card with citations, source snapshot, unresolved items, and blocked-upgrade language preserved.",
        "A JSON artifact reference plus canonical citation text that another crawler or agent can retrieve without treating it as a live service.",
        "A human-review handoff when the case remains high-risk, private, legally sensitive, or close to money movement or public distribution."
      ],
      "escalationWhen": [
        "Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete.",
        "Escalate to qualified human review when source confidence, match confidence, exact wording, ownership, payment authority, publication risk, or user-specific suitability remains unresolved.",
        "Escalate immediately when a user asks the static pack to approve payment, clear a counterparty, certify compliance, publish a claim as safe, or execute a financial action."
      ]
    },
    "caseWorksheet": {
      "worksheetId": "payment_instruction_change_pack_case_worksheet",
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement case worksheet",
      "worksheetType": "generic_static_case_ledger",
      "serviceId": "action-preflight",
      "serviceName": "Action Preflight",
      "actionType": "payment_instruction_change_before_settlement",
      "staticOnly": true,
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "rows": [
        {
          "rowId": "payment_instruction_change_pack_static_case_scope_row",
          "label": "Static case scope row",
          "sourceLabel": "TRADING4AI public material pack",
          "evidenceToCapture": "Capture the case summary, source links, required input fields, sample evidence record references, audience or action context, and any unresolved source gaps before reuse.",
          "resultSemantics": "Treat the row as an exact static-sample match, partial match, no-hit, unresolved match, or out-of-scope match before producing any handoff.",
          "unsafeTermCategory": "static sample upgraded into live approval, safety, suitability, or execution guidance",
          "safeRewrite": "Safe restatement: the static pack can describe cited evidence, unresolved items, source limitations, and a bounded next step at the listed retrieval time.",
          "blockedRewrite": "Do not say this static sample is verified, safe, compliant, suitable, approved, cleared, guaranteed, or permission to proceed.",
          "escalationReason": "Escalate when the current case, source set, audience, payment destination, publication channel, or requested action differs from the static sample.",
          "linkedEvidenceRecordIds": [
            "beneficiary_name_mismatch"
          ],
          "linkedDecisionMatrixIds": [
            "payment_instruction_change_pack_prior_instruction_row"
          ],
          "blockedUpgrade": "Do not say this static sample is verified, safe, compliant, suitable, approved, cleared, guaranteed, or permission to proceed."
        }
      ],
      "completionRule": "Treat this worksheet as complete only when every row preserves source/citation fields, result semantics, safe rewrite, blocked rewrite, and escalation reason.",
      "boundaries": [
        "This worksheet is a static sample handoff and not a live review, legal verdict, compliance approval, payment clearance, trading advice, or publication approval.",
        "Do not reuse a worksheet row for a new case unless the cited sources, retrieval timestamps, input fields, and source-review policy have been rechecked.",
        "Escalate to qualified human review when any row remains unresolved or the user asks for approval, clearance, suitability, payment, execution, or publication permission."
      ]
    },
    "searchIntent": {
      "intentId": "payment_instruction_change_pack_search_intent",
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement",
      "serviceId": "action-preflight",
      "serviceName": "Action Preflight",
      "actionType": "payment_instruction_change_before_settlement",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "queryExamples": [
        "payment instruction changed before settlement",
        "vendor changed bank account",
        "verify new payment details",
        "invoice bank account changed by email",
        "beneficiary changed before wire",
        "vendor payment instruction change fraud"
      ],
      "userTask": "Review a changed beneficiary, bank account, invoice, or wallet destination before settlement.",
      "routeReason": "Route to Payment instruction change before settlement when the user task matches payment_instruction_change_before_settlement and needs A source-bound action note that compares the previous approved instruction with the changed instruction, confirmation channel, mismatch evidence, and escalation boundary.",
      "useWhen": [
        "A user or agent receives changed bank, wire, invoice, wallet, memo, tag, or destination instructions before settlement.",
        "A payment instruction changes close to settlement or arrives through a side channel.",
        "Read the HTML page first for boundaries, then use the JSON artifact for structured retrieval."
      ],
      "doNotUseAs": [
        "live approval",
        "investment advice",
        "compliance clearance",
        "real-time screening",
        "backtesting or execution advice"
      ],
      "escalationRule": "Escalate to qualified human review when required inputs are missing, source confidence is unresolved, payment or transfer risk is present, or the user asks for approval, clearance, execution, suitability, or compliance guarantees."
    },
    "sourceQuality": {
      "packId": "payment_instruction_change_pack",
      "title": "Payment instruction change before settlement",
      "serviceId": "action-preflight",
      "serviceName": "Action Preflight",
      "actionType": "payment_instruction_change_before_settlement",
      "workflowId": "payment_instruction_change_pack_agent_workflow",
      "pagePath": "/agent-verification/materials/payment-instruction-change-pack",
      "artifactPath": "/reliability/public-materials/payment-instruction-change-pack.json",
      "sourceManifestCount": 5,
      "sourceKinds": [
        "official_guidance",
        "sample_page"
      ],
      "sourceSnapshotAt": "2026-05-25T00:00:00.000Z",
      "officialRegistrySourceCount": 0,
      "officialGuidanceSourceCount": 4,
      "sourceQualityProfile": "guidance_heavy",
      "registryCoverageExpectation": "not_primary_for_this_static_pack",
      "sourceMixRationale": "This pack is guidance-heavy because changed beneficiary, bank, wallet, channel, and settlement-pressure review relies on Business Email Compromise and payment-fraud guidance plus the user's own destination-integrity evidence.",
      "zeroRegistryAllowedReason": "Zero official registry sources is acceptable for this static pack because the core question is Business Email Compromise and payment-instruction integrity, not sanctions-list screening; it is not payment-instruction clearance.",
      "agentSourceUse": [
        "Use official BEC and fraud guidance to keep the changed instruction blocked or under review while destination-integrity evidence is missing.",
        "Compare known-good channel, prior beneficiary, bank or wallet rail fields, dual-control evidence, and settlement cut-off pressure before drafting any user-facing note.",
        "Do not treat guidance-heavy source coverage as a bank validation, treasury approval, sanctions clearance, or safe-to-pay decision."
      ],
      "sourceReviewPolicy": {
        "policyId": "payment_instruction_change_pack_source_review_policy",
        "packId": "payment_instruction_change_pack",
        "title": "Payment instruction change before settlement",
        "serviceId": "action-preflight",
        "serviceName": "Action Preflight",
        "actionType": "payment_instruction_change_before_settlement",
        "staticOnly": true,
        "sourceSnapshotAt": "2026-05-25T00:00:00.000Z",
        "reviewCadenceDays": 60,
        "nextRecommendedReviewAt": "2026-07-24T00:00:00.000Z",
        "freshnessStatus": "current_static_snapshot",
        "sourceReviewMode": "manual_public_source_recheck_required",
        "refreshRequiredWhen": [
          "Any cited official source, registry, guidance page, filing page, or public warning URL changes content, schema, access status, or meaning.",
          "A downstream agent wants to use the static pack for a new counterparty, payment destination, wallet, claim, filing, macro release, or source set.",
          "The current date is past nextRecommendedReviewAt or the artifactVersion / generatedAt fields are removed from the handoff.",
          "The beneficiary, bank rail, wallet destination, known-good confirmation channel, or fraud-warning source differs from the static sample."
        ],
        "staleSignals": [
          "A source URL no longer resolves, redirects to unrelated content, or changes field definitions.",
          "The pack is being reused after nextRecommendedReviewAt without a fresh official-source review.",
          "A user or agent treats this static snapshot as live screening, live clearance, or final approval."
        ],
        "agentActionWhenPastReview": "Re-check the cited official/public sources, preserve new retrieval timestamps, regenerate or version the artifact, and keep the output at review/escalate until source freshness is restored.",
        "staticUseBoundary": "This is a static source-review policy for a pre-generated public material pack; it is not live screening, request-time judgment, compliance clearance, payment approval, or trading advice.",
        "generatedAt": "2026-05-25T00:00:00.000Z"
      },
      "sampleEvidenceRecordCount": 8,
      "boundary": "static_source_manifest_not_live_screening"
    },
    "sourceManifest": [
      {
        "id": "verified_supplier_record_sample_agent_verification_materials_payment_instruction",
        "label": "Verified supplier record (sample)",
        "url": "/agent-verification/materials/payment-instruction-change-pack",
        "kind": "sample_page",
        "citationRole": "sample_context",
        "retrievedAt": "2026-05-25T00:00:00.000Z",
        "evidenceRecordIds": [
          "beneficiary_name_mismatch",
          "unverified_channel_switch",
          "ownership_proof_missing",
          "destination_integrity_gap"
        ],
        "supports": [
          "The changed beneficiary name no longer matches the supplier name on the last verified invoice and onboarding record",
          "The payment-change request arrived from a new email thread and was not confirmed in the previously trusted supplier portal",
          "No signed bank letter, portal confirmation, or wallet-ownership record ties the new destination to the claimed supplier",
          "Destination-integrity fields are incomplete across SWIFT, IBAN, routing, account number, wallet chain, memo, tag, and destination tag"
        ],
        "limitations": [
          "This source entry records what the static sample cites; it does not prove current, complete, or final clearance.",
          "Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow."
        ]
      },
      {
        "id": "cisa_business_email_compromise_guidance_https_www_cisa_gov_news_events_news_busi",
        "label": "CISA Business Email Compromise guidance",
        "url": "https://www.cisa.gov/news-events/news/business-email-compromise",
        "kind": "official_guidance",
        "citationRole": "primary_warning",
        "retrievedAt": "2026-05-25T00:00:00.000Z",
        "evidenceRecordIds": [
          "urgency_and_secrecy_pressure"
        ],
        "supports": [
          "The message asks for same-day settlement and says the old finance contact should not be called",
          "Changed payment instructions are a classic irreversible-action risk: the money can move before identity, beneficiary ownership, and instruction legitimacy are verified."
        ],
        "limitations": [
          "This source entry records what the static sample cites; it does not prove current, complete, or final clearance.",
          "Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow."
        ]
      },
      {
        "id": "fbi_business_email_compromise_guidance_https_www_fbi_gov_how_we_can_help_you_sca",
        "label": "FBI Business Email Compromise guidance",
        "url": "https://www.fbi.gov/how-we-can-help-you/scams-and-safety/common-frauds-and-scams/business-email-compromise",
        "kind": "official_guidance",
        "citationRole": "primary_warning",
        "retrievedAt": "2026-05-25T00:00:00.000Z",
        "evidenceRecordIds": [
          "fbi_bec_source_required"
        ],
        "supports": [
          "FBI Business Email Compromise (BEC) guidance remains a required reference for payment-instruction change risk",
          "Changed payment instructions are a classic irreversible-action risk: the money can move before identity, beneficiary ownership, and instruction legitimacy are verified."
        ],
        "limitations": [
          "This source entry records what the static sample cites; it does not prove current, complete, or final clearance.",
          "Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow."
        ]
      },
      {
        "id": "ftc_consumer_alerts_https_consumer_ftc_gov_consumer_alerts",
        "label": "FTC consumer alerts",
        "url": "https://consumer.ftc.gov/consumer-alerts",
        "kind": "official_guidance",
        "citationRole": "primary_warning",
        "retrievedAt": "2026-05-25T00:00:00.000Z",
        "evidenceRecordIds": [
          "ftc_consumer_alert_source_required"
        ],
        "supports": [
          "FTC consumer alert coverage remains relevant when payment instructions arrive through suspicious or impersonation-style channels",
          "Changed payment instructions are a classic irreversible-action risk: the money can move before identity, beneficiary ownership, and instruction legitimacy are verified."
        ],
        "limitations": [
          "This source entry records what the static sample cites; it does not prove current, complete, or final clearance.",
          "Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow."
        ]
      },
      {
        "id": "fincen_e_mail_compromise_fraud_advisory_for_financial_institutions_https_www_fin",
        "label": "FinCEN e-mail compromise fraud advisory for financial institutions",
        "url": "https://www.fincen.gov/resources/statutes-regulations/guidance/advisory-financial-institutions-e-mail-compromise-fraud",
        "kind": "official_guidance",
        "citationRole": "supporting_reference",
        "retrievedAt": "2026-05-25T00:00:00.000Z",
        "evidenceRecordIds": [
          "fincen_email_compromise_source_required"
        ],
        "supports": [
          "FinCEN e-mail compromise fraud advisory remains a required reference for suspicious wire-transfer instruction changes",
          "Changed payment instructions are a classic irreversible-action risk: the money can move before identity, beneficiary ownership, and instruction legitimacy are verified."
        ],
        "limitations": [
          "This source entry records what the static sample cites; it does not prove current, complete, or final clearance.",
          "Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow."
        ]
      }
    ],
    "canonicalCitation": {
      "pageUrl": "https://trading4ai.com/agent-verification/materials/payment-instruction-change-pack",
      "artifactUrl": "https://trading4ai.com/reliability/public-materials/payment-instruction-change-pack.json",
      "artifactVersion": "public-material-payment-instruction-change-pack-2026-05-25",
      "generatedAt": "2026-05-25T00:00:00.000Z",
      "staticSnapshotAt": "2026-05-25T00:00:00.000Z",
      "sourceSnapshotAt": "2026-05-25T00:00:00.000Z",
      "recommendedCitationText": "Payment instruction change before settlement, public-material-payment-instruction-change-pack-2026-05-25, generated 2026-05-25T00:00:00.000Z, source snapshot 2026-05-25T00:00:00.000Z, https://trading4ai.com/agent-verification/materials/payment-instruction-change-pack"
    },
    "generatedAt": "2026-05-25T00:00:00.000Z"
  },
  "request_id": "public_material_pack_payment-instruction-change-pack_static_artifact_2026_05_25",
  "timestamp": "2026-05-25T00:00:00.000Z"
}
