TRADING4AIStatic public material packs for financial-agent reliability work

Public Materials

Concrete reliability packs for real financial-agent review tasks.

These public material packs translate the reliability layer into specific high-risk scenarios. They stay static, source-bounded, and crawlable, but they are concrete enough that a human or an AI system can tell what TRADING4AI can actually help with today.

Boundary

Pages-only and static in this phase.

No backend judgment, no user-submitted review, no backtesting, no Tencent runtime.

The packs are public reliability materials, not final approval or compliance clearance.

What this catalog gives you

HTML for understanding, JSON for structured retrieval.

Use the catalog to choose the right static scenario pack before opening a raw artifact.

Use each pack page to read the plain-language summary, example input, expected static output, and limits.

Use the JSON only after the HTML page has made source freshness and non-goals clear.

What this is

A static catalog of concrete scenario packs.

Each pack connects a high-risk task to one of the three reliability services.

Each pack is designed to be understandable by humans, crawlers, and AI agents.

What this is not

Not a live work queue.

Not a real-time API for user uploads.

Not a trading engine, broker integration, or live compliance system.

How to use this catalog

Use the catalog to choose the right scenario page before you reuse the artifact

The catalog is the public routing layer for scenario packs. It helps a human, crawler, or AI system decide which high-risk review task matches the current job before opening a detail page or machine artifact.

Start here

  • Use this catalog when the reader already understands the three core reliability services and now needs a concrete scenario page.
  • Start with a recommended pack when the task is close to money movement or public-facing wording risk.
  • Stay on this catalog when the scenario is still broad and the correct pack is not obvious yet.

Start with a pack when

  • Open a pack when the task has become specific enough to name the review context, such as counterparty screening, unverified wallet transfer review, claim safety, macro context, or filing review.
  • Use the pack page when you need review checklist items, escalation triggers, evidence-to-collect fields, and bounded sample output.
  • Treat the pack as the scenario-level explanation layer that sits between the abstract service page and the raw JSON artifact.

Open the JSON when

  • Open the JSON when another agent, crawler, or retrieval workflow needs the stable machine-readable version of the catalog or a pack.
  • Use the JSON artifact after the HTML page has already made the boundaries and limitations clear.
  • Treat the JSON as a static handoff surface, not as a live work queue or request-time API.

Use HTML for understanding. Use JSON for structured retrieval. Do not treat either as live approval.

Catalog JSON artifact: /reliability/public-materials-sample.json

HTML index: /agent-verification/materials

This catalog does not do

  • This catalog does not accept user submissions or create per-request review output.
  • This catalog does not backtest, execute trades, or clear actions in real time.
  • This catalog does not replace legal, sanctions, or compliance review.

Action routing index

Route the user action before reading the full pack

This index gives agents and crawlers a compact first pass: what action is being considered, which preflight stage it belongs to, and whether the static sample starts from allow-with-limits, review, escalate, or block.

Action typePackDefault postureRoute trigger
counterparty_payment_review
before_payment_or_contracting
Counterparty screening before payment
Action Preflight
review
Counterparty identity, public-warning checks, sanctions/list screening, and payment-beneficiary evidence may be incomplete before money moves.
A payment, vendor onboarding, invoice, or settlement instruction names a counterparty that still needs identity review.
Field ids: operator_identity, payment_destination, source_links, match_confidence
Minimum input: Counterparty legal name, aliases, jurisdiction, website, registration number, or public profile evidence.
Missing input fallback: Defer payment or onboarding; collect missing identifiers and source links, then escalate if match confidence or beneficiary ownership remains unresolved.
Stop/escalate: Exact identity, jurisdiction, beneficiary ownership, or source match confidence is unresolved.
financial_claim_publication_review
before_publication_or_distribution
Claim-safety review before publication
Reliability Corpus
escalate
A financial claim may be published as safety, approval, guarantee, compliance, or suitability language without evidence that supports it.
An agent is preparing public, marketing, product, or support language about a financial tool, strategy, subscription, or review.
Field ids: claim_text, source_links, claim_category, claim_evidence, limitation_language
Minimum input: Exact claim text, audience, distribution channel, and whether the claim is public, marketing, support, or internal copy.
Missing input fallback: Escalate or do not publish; collect missing source, audience, scope, and limitation evidence before restating the financial claim.
Stop/escalate: The claim implies guaranteed returns, low risk, verified safety, legal compliance, suitability, or user protection.
crypto_signal_subscription_payment
before_payment_or_account_connection
Crypto signal subscription before payment
Action Preflight
block
Payment, custody, brokerage/API access, or credentials may move before operator identity and performance claims are verified.
A user or agent is considering paying for a crypto, AI trading, or signal subscription.
Field ids: operator_identity, payment_destination, claim_evidence, access_scope
Minimum input: Seller or operator name plus a public website, profile, or legal entity claim controlled by the offer.
Missing input fallback: Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.
Stop/escalate: Guaranteed-return, low-risk, registration, or suitability claims remain unsupported by cited public evidence.
wallet_transfer_unverified_counterparty
before_wallet_transfer
Wallet transfer to unverified counterparty
Action Preflight
block
An irreversible wallet transfer may be sent to a weakly verified counterparty or destination before ownership and warning-source checks are complete.
A user or agent is preparing to send crypto to a new, private-group, or weakly verified counterparty wallet.
Field ids: wallet_destination, operator_identity, wallet_ownership_evidence, source_links
Minimum input: Destination wallet address, chain or network, memo/tag if required, transfer amount, and requested settlement timing.
Missing input fallback: Do not send the transfer; collect missing destination, ownership, chain, and warning-source evidence or escalate to a human reviewer.
Stop/escalate: Counterparty identity, wallet ownership, destination chain, memo/tag, or address provenance is unresolved.
macro_release_context_interpretation
before_macro_summary_or_market_commentary
Macro release context packaging
Evidence Cards
allow_with_limits
A macro data point may be repeated without revision, vintage, release-lag, COT lag, or non-trading limitations.
An agent needs to summarize a macro release, FRED series, BLS release, or CFTC positioning note.
Field ids: macro_release_context, source_links, intended_use_context
Minimum input: Official source, series or release identifier, publication timestamp, and retrieval timestamp.
Missing input fallback: Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.
Stop/escalate: The summary converts a reported value into a market call, trade instruction, or portfolio recommendation.
payment_instruction_change_before_settlement
before_settlement_or_release
Payment instruction change before settlement
Action Preflight
block
Changed payment instructions can redirect funds before channel integrity, beneficiary ownership, and destination details are verified.
A user or agent receives changed bank, wire, invoice, wallet, memo, tag, or destination instructions before settlement.
Field ids: prior_payment_instruction, changed_instruction, known_good_confirmation, payment_destination
Minimum input: Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.
Missing input fallback: Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete.
Stop/escalate: Known-good channel confirmation, beneficiary ownership, prior payment rail comparison, or dual approval is missing.
public_company_filing_review
before_filing_summary_or_company_claim
Public company filing review
Evidence Cards
review
A filing fact may be summarized without CIK, accession, period, item, exhibit, XBRL, unit, scale, or not-live-refresh boundaries.
An agent needs to summarize or cite a public-company filing fact before using it in research or a company claim.
Field ids: filing_identifier, filing_fact_reference, source_links, intended_use_context
Minimum input: Company name, ticker if used, CIK, form type, accession number, filing date, and reporting period.
Missing input fallback: Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.
Stop/escalate: CIK, accession, filing date, reporting period, item, exhibit, XBRL unit, or scale context is missing.

Input field glossary

Reusable fields behind the preflight packs

This glossary keeps input names stable for crawlers and agents. The pack pages still explain scenario details, while these field definitions explain why a missing input should change the review posture.

FieldUsed by actionsWhy it mattersMissing input risk
operator_identity
Operator identity
crypto_signal_subscription_payment, counterparty_payment_review, wallet_transfer_unverified_counterpartyAgents need an identity anchor before evaluating payment, access, or public claim risk.The agent may route money or trust claims to an unverified or impersonated operator.
payment_destination
Payment destination
crypto_signal_subscription_payment, counterparty_payment_review, payment_instruction_change_before_settlementHigh-risk financial actions become irreversible once money moves to the wrong destination.The agent cannot compare the destination against the named counterparty or prior approved instructions.
claim_evidence
Claim evidence
crypto_signal_subscription_payment, financial_claim_publication_reviewUnsupported financial claims should not be upgraded into safe, verified, or suitable statements.The agent may repeat promotional language as if it were verified evidence.
access_scope
Access scope
crypto_signal_subscription_paymentAccount or custody access can create loss exposure even before a payment is sent.The agent may approve a request that silently grants trading, withdrawal, or custody control.
source_links
Source links
counterparty_payment_review, wallet_transfer_unverified_counterparty, macro_release_context_interpretation, public_company_filing_review, financial_claim_publication_reviewStatic evidence cards only work when their source set is explicit and retrievable.The agent cannot separate source-bound evidence from unsourced assertion.
match_confidence
Match confidence
counterparty_payment_reviewScreening output is dangerous when a partial match is treated like an exact match, or the reverse.The agent may either block a legitimate action or miss a serious warning signal.
wallet_destination
Wallet destination
wallet_transfer_unverified_counterpartyWallet transfers are often irreversible and chain or memo errors can permanently misroute funds.The agent may send funds to the wrong chain, wrong address, or unverified recipient.
wallet_ownership_evidence
Wallet ownership evidence
wallet_transfer_unverified_counterpartyA copied address in a chat or invoice is not enough to prove beneficiary ownership.The agent may treat an attacker-supplied address as a verified counterparty address.
prior_payment_instruction
Prior payment instruction
payment_instruction_change_before_settlementChanged payment details can only be assessed against a known-good baseline.The agent cannot tell whether a destination change is normal, suspicious, or unverifiable.
changed_instruction
Changed instruction
payment_instruction_change_before_settlementPayment redirection attacks often arrive through channel changes, urgency, or incomplete destination details.The agent may approve an untraceable change without confirming what actually changed.
known_good_confirmation
Known-good confirmation
payment_instruction_change_before_settlementThe confirmation path must not depend on the same message that requested the risky change.The agent may accept attacker-controlled confirmation as real approval.
macro_release_context
Macro release context
macro_release_context_interpretationMacro values can be misleading when revisions, units, timing, or report lags are missing.The agent may turn a stale or incomparable data point into overconfident market commentary.
filing_identifier
Filing identifier
public_company_filing_reviewCompany claims need a stable filing anchor before summarization or citation.The agent may cite the wrong filing, wrong period, or stale company fact.
filing_fact_reference
Filing fact reference
public_company_filing_reviewFinancial statement facts can be wrong if unit, scale, or exhibit context is omitted.The agent may restate a filing fact with the wrong unit, scale, or source location.
intended_use_context
Intended use context
macro_release_context_interpretation, public_company_filing_reviewThe same evidence may be safe as context but unsafe as a recommendation, advertisement, or action instruction.The agent may apply the wrong safety boundary to the final output.
claim_text
Claim text
financial_claim_publication_reviewClaim safety review must inspect the actual words, not a paraphrased intention.The agent may miss overclaiming, suitability language, or unsupported safety language.
claim_category
Claim category
financial_claim_publication_reviewDifferent claim categories need different blocked-language and limitation checks.The agent may apply generic wording where a stricter blocked-claim rule is needed.
limitation_language
Limitation language
financial_claim_publication_reviewEvidence is only trustworthy when its boundary is visible to downstream readers and agents.The agent may publish a bounded evidence note as if it were live clearance or final advice.

Preflight questionnaire

Ask these questions before moving the action forward

Each question set is derived from the pack input field order. It gives agents a stable static checklist for collecting missing facts before payment, transfer, filing, macro, or claim work continues.

PackQuestion countFirst questionCompletion rule
Counterparty screening before payment
counterparty_payment_review
4What evidence identifies the operator identity for this counterparty_payment_review review?
Acceptable evidence: legal name, known aliases, website, registration number, public profile
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.
Claim-safety review before publication
financial_claim_publication_review
5What evidence identifies the claim text for this financial_claim_publication_review review?
Acceptable evidence: guaranteed return sentence, low-risk phrase, compliance claim, approval claim
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.
Crypto signal subscription before payment
crypto_signal_subscription_payment
4What evidence identifies the operator identity for this crypto_signal_subscription_payment review?
Acceptable evidence: legal name, known aliases, website, registration number, public profile
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.
Wallet transfer to unverified counterparty
wallet_transfer_unverified_counterparty
4What evidence identifies the wallet destination for this wallet_transfer_unverified_counterparty review?
Acceptable evidence: address, chain, memo, destination tag, amount
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.
Macro release context packaging
macro_release_context_interpretation
3What evidence identifies the macro release context for this macro_release_context_interpretation review?
Acceptable evidence: series ID, release timestamp, reported period, vintage, unit
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.
Payment instruction change before settlement
payment_instruction_change_before_settlement
4What evidence identifies the prior payment instruction for this payment_instruction_change_before_settlement review?
Acceptable evidence: previous IBAN, previous wallet, approved vendor master record, last paid beneficiary
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.
Public company filing review
public_company_filing_review
4What evidence identifies the filing identifier for this public_company_filing_review review?
Acceptable evidence: CIK, 10-K, 8-K, accession number, filing date
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.

Static decision policy

Proceed, fallback, or stop

Each policy tells agents how far a static pack can go after the questionnaire is answered. It defines proceed-only conditions, missing-input fallback, and escalation boundaries without turning this catalog into live approval or clearance.

PackProceed only whenFallbackStop or escalate
Counterparty screening before payment
review
Collected and cited: Counterparty legal name, aliases, jurisdiction, website, registration number, or public profile evidence.Defer payment or onboarding; collect missing identifiers and source links, then escalate if match confidence or beneficiary ownership remains unresolved.Exact identity, jurisdiction, beneficiary ownership, or source match confidence is unresolved.
Claim-safety review before publication
escalate
Collected and cited: Exact claim text, audience, distribution channel, and whether the claim is public, marketing, support, or internal copy.Escalate or do not publish; collect missing source, audience, scope, and limitation evidence before restating the financial claim.The claim implies guaranteed returns, low risk, verified safety, legal compliance, suitability, or user protection.
Crypto signal subscription before payment
block
Collected and cited: Seller or operator name plus a public website, profile, or legal entity claim controlled by the offer.Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.Guaranteed-return, low-risk, registration, or suitability claims remain unsupported by cited public evidence.
Wallet transfer to unverified counterparty
block
Collected and cited: Destination wallet address, chain or network, memo/tag if required, transfer amount, and requested settlement timing.Do not send the transfer; collect missing destination, ownership, chain, and warning-source evidence or escalate to a human reviewer.Counterparty identity, wallet ownership, destination chain, memo/tag, or address provenance is unresolved.
Macro release context packaging
allow_with_limits
Collected and cited: Official source, series or release identifier, publication timestamp, and retrieval timestamp.Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.The summary converts a reported value into a market call, trade instruction, or portfolio recommendation.
Payment instruction change before settlement
block
Collected and cited: Previously approved beneficiary, payment rail, bank account, wallet, memo/tag, or settlement instruction on record.Do not release payment on changed instructions; collect known-good confirmation and dual-approval evidence, then escalate if any destination detail remains incomplete.Known-good channel confirmation, beneficiary ownership, prior payment rail comparison, or dual approval is missing.
Public company filing review
review
Collected and cited: Company name, ticker if used, CIK, form type, accession number, filing date, and reporting period.Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.CIK, accession, filing date, reporting period, item, exhibit, XBRL unit, or scale context is missing.

Static output template

Write the action note without crossing the boundary

These templates define the final source-bound note an agent may draft after routing, collecting minimum inputs, answering the questionnaire, and applying the decision policy.

TemplateSectionsAllowed useBoundary
Counterparty screening before payment static action note
counterparty_screening_pack_static_action_note_template
action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Action Preflight note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Claim-safety review before publication static action note
claim_safety_pack_static_action_note_template
action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Reliability Corpus note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Crypto signal subscription before payment static action note
crypto_signal_subscription_pack_static_action_note_template
action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Action Preflight note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Wallet transfer to unverified counterparty static action note
wallet_transfer_unverified_counterparty_pack_static_action_note_template
action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Action Preflight note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Macro release context packaging static action note
macro_release_context_pack_static_action_note_template
action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Evidence Cards note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Payment instruction change before settlement static action note
payment_instruction_change_pack_static_action_note_template
action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Action Preflight note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Public company filing review static action note
public_company_filing_pack_static_action_note_template
action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trailUse only as a static, source-bound Evidence Cards note after completing action routing, the preflight questionnaire, and the decision policy.This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Filled output example

Static action notes agents can inspect

The examples fill each template with the pack's sample input, cited evidence records, safe restatement, blocked language, and canonical citation so agents can see the intended output boundary.

ExampleStatusSections and evidence idsBoundary
Counterparty screening before payment static action note example
counterparty_screening_pack_static_action_note_example
reviewSections: action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trail
Evidence ids: beneficiary_mismatch, ofac_name_search, entity_resolution_fields_missing, trade_csl_source_required, sam_exclusions_source_required, world_bank_debarred_source_required, cftc_red_list_source_required, opensanctions_public_reference, ftc_crypto_scam_reference, instruction_channel_change, beneficiary_proof_missing
This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Claim-safety review before publication static action note example
claim_safety_pack_static_action_note_example
escalateSections: action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trail
Evidence ids: sample_artifact_scope, no_safety_approval_source, ai_fraud_overclaim_warning, investment_group_imposter_warning, timestamp_and_scope_missing, guarantee_language_upgrade
This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Crypto signal subscription before payment static action note example
crypto_signal_subscription_pack_static_action_note_example
blockSections: action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trail
Evidence ids: guaranteed_return_claim, brokerage_access_request, operator_identity_gap, brokercheck_registration_gap, iapd_adviser_registration_gap, irreversible_crypto_payment
This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Wallet transfer to unverified counterparty static action note example
wallet_transfer_unverified_counterparty_pack_static_action_note_example
blockSections: action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trail
Evidence ids: private_group_alias_only, wallet_address_only, destination_integrity_gap, explorer_context_gap, irreversible_crypto_transfer, ftc_recovery_boundary, fbi_crypto_transaction_info_required, ofac_virtual_currency_source_required, ofac_sanctions_list_source_required, cftc_imposter_payment_warning
This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Macro release context packaging static action note example
macro_release_context_pack_static_action_note_example
allow_with_limitsSections: action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trail
Evidence ids: fred_series_observation_vintage, fred_api_source_boundary, bls_cpi_release_source, bls_public_data_api_boundary, cftc_cot_report_lag, cftc_historical_compressed_context
This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Payment instruction change before settlement static action note example
payment_instruction_change_pack_static_action_note_example
blockSections: action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trail
Evidence ids: 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
This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.
Public company filing review static action note example
public_company_filing_pack_static_action_note_example
reviewSections: action_context, source_bound_evidence, decision_policy, safe_restatement, blocked_language, citation_trail
Evidence ids: edgar_accession_record, edgar_api_structured_fields, filing_period_item_exhibit_context, xbrl_fact_value_unit_scale, edgar_fair_access_boundary, valuation_support_missing
This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Agent workflow

One ordered sequence per high-risk action

The workflow index links the compact routing record, minimum inputs, questionnaire, decision policy, static action note template, filled example, source manifest, and canonical citation.

WorkflowStepsLinked artifactsEscalation
Counterparty screening before payment agent workflow
counterparty_payment_review
select_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalateExample: counterparty_screening_pack_static_action_note_example
Source manifest entries: 8
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.
Claim-safety review before publication agent workflow
financial_claim_publication_review
select_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalateExample: claim_safety_pack_static_action_note_example
Source manifest entries: 6
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.
Crypto signal subscription before payment agent workflow
crypto_signal_subscription_payment
select_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalateExample: crypto_signal_subscription_pack_static_action_note_example
Source manifest entries: 6
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.
Wallet transfer to unverified counterparty agent workflow
wallet_transfer_unverified_counterparty
select_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalateExample: wallet_transfer_unverified_counterparty_pack_static_action_note_example
Source manifest entries: 7
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.
Macro release context packaging agent workflow
macro_release_context_interpretation
select_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalateExample: macro_release_context_pack_static_action_note_example
Source manifest entries: 6
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.
Payment instruction change before settlement agent workflow
payment_instruction_change_before_settlement
select_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalateExample: payment_instruction_change_pack_static_action_note_example
Source manifest entries: 5
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.
Public company filing review agent workflow
public_company_filing_review
select_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalateExample: public_company_filing_pack_static_action_note_example
Source manifest entries: 4
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.

Action type workflow lookup

Map an action type directly to the workflow

actionTypeWorkflowLookup is the compact machine-facing index for agents that already know the action_type and need the correct workflow, pack page, JSON artifact, minimum inputs, example, citation, and escalation boundary without scanning every pack.

Action typeWorkflowInputsEscalation
crypto_signal_subscription_paymentcrypto_signal_subscription_pack_agent_workflow
/reliability/public-materials/crypto-signal-subscription-pack.json
operator_identity, payment_destination, claim_evidence, access_scopeEscalate 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.
counterparty_payment_reviewcounterparty_screening_pack_agent_workflow
/reliability/public-materials/counterparty-screening-pack.json
operator_identity, payment_destination, source_links, match_confidenceEscalate 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.
wallet_transfer_unverified_counterpartywallet_transfer_unverified_counterparty_pack_agent_workflow
/reliability/public-materials/wallet-transfer-unverified-counterparty-pack.json
wallet_destination, operator_identity, wallet_ownership_evidence, source_linksEscalate 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.
payment_instruction_change_before_settlementpayment_instruction_change_pack_agent_workflow
/reliability/public-materials/payment-instruction-change-pack.json
prior_payment_instruction, changed_instruction, known_good_confirmation, payment_destinationEscalate 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.
macro_release_context_interpretationmacro_release_context_pack_agent_workflow
/reliability/public-materials/macro-release-context-pack.json
macro_release_context, source_links, intended_use_contextEscalate 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.
public_company_filing_reviewpublic_company_filing_pack_agent_workflow
/reliability/public-materials/public-company-filing-pack.json
filing_identifier, filing_fact_reference, source_links, intended_use_contextEscalate 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.
financial_claim_publication_reviewclaim_safety_pack_agent_workflow
/reliability/public-materials/claim-safety-pack.json
claim_text, source_links, claim_category, claim_evidence, limitation_languageEscalate 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.

Search intent index

Map natural-language tasks to the right pack

searchIntentIndex is the compact SEO and agent-facing index for readers who do not know the internal action type yet. Use queryExamples to route plain-language questions to the matching static material page and JSON artifact.

IntentqueryExamplesRouteBoundary
crypto_signal_subscription_pack_search_intent
Check a crypto signal subscription, guaranteed-return offer, or paid group before sending funds or account access.
check crypto signal before paying, crypto signal subscription safe, guaranteed return crypto signal, check Telegram crypto signal group, crypto trading club asks for brokerage accessCrypto signal subscription before payment
crypto_signal_subscription_payment
JSON artifact
Route to Crypto signal subscription before payment when the user task matches crypto_signal_subscription_payment and needs A source-bound action note that separates subscription claims, payment pressure, account-access risk, missing evidence, blocked language, and escalation rules.
Do not use as: live approval, investment advice, compliance clearance, real-time screening, backtesting or execution advice
counterparty_screening_pack_search_intent
Screen a vendor, customer, wallet owner, or payment counterparty before a transfer or wire.
verify vendor before wire, screen counterparty before payment, counterparty screening evidence, OFAC vendor screening before payment, supplier wire transfer evidence card, check company before paying invoiceCounterparty screening before payment
counterparty_payment_review
JSON artifact
Route to Counterparty screening before payment when the user task matches counterparty_payment_review and needs A source-bound action note that separates counterparty identity, payment details, screening sources, match confidence, missing inputs, and unresolved escalation triggers.
Do not use as: live approval, investment advice, compliance clearance, real-time screening, backtesting or execution advice
wallet_transfer_unverified_counterparty_pack_search_intent
Check an unverified crypto wallet destination before an irreversible wallet transfer.
check wallet before transfer, is this crypto wallet safe to send to, verify wallet destination, USDT wallet from Telegram group, check Tron wallet before USDT transfer, wallet ownership proof before transferWallet transfer to unverified counterparty
wallet_transfer_unverified_counterparty
JSON artifact
Route to Wallet transfer to unverified counterparty when the user task matches wallet_transfer_unverified_counterparty and needs A source-bound action note that separates wallet destination details, counterparty identity, ownership proof, warning sources, missing inputs, and stop rules.
Do not use as: live approval, investment advice, compliance clearance, real-time screening, backtesting or execution advice
payment_instruction_change_pack_search_intent
Review a changed beneficiary, bank account, invoice, or wallet destination before settlement.
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 fraudPayment instruction change before settlement
payment_instruction_change_before_settlement
JSON artifact
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.
Do not use as: live approval, investment advice, compliance clearance, real-time screening, backtesting or execution advice
macro_release_context_pack_search_intent
Package macro release facts into source-bound context without upgrading them into market predictions.
explain CPI release with sources, macro release context, safe statement about inflation dataMacro release context packaging
macro_release_context_interpretation
JSON artifact
Route to Macro release context packaging when the user task matches macro_release_context_interpretation and needs A source-bound evidence note that preserves release name, period, vintage, units, retrieval time, comparison limits, safe statements, and blocked market claims.
Do not use as: live approval, investment advice, compliance clearance, real-time screening, backtesting or execution advice
public_company_filing_pack_search_intent
Turn a company filing event into a cited evidence note without making valuation or recommendation claims.
SEC filing evidence card, company filing event summary, 10-K or 8-K source cardPublic company filing review
public_company_filing_review
JSON artifact
Route to Public company filing review when the user task matches public_company_filing_review and needs A source-bound filing note that preserves CIK, accession, form type, filing date, source path, exact field or exhibit, limitations, and blocked recommendation language.
Do not use as: live approval, investment advice, compliance clearance, real-time screening, backtesting or execution advice
claim_safety_pack_search_intent
Check whether financial wording can be safely published without implying guarantees, suitability, or clearance.
safe wording for investment claim, can I say guaranteed returns, financial claim safety review, can agent say strategy is verified, avoid guaranteed profit claim, safe financial marketing wordingClaim-safety review before publication
financial_claim_publication_review
JSON artifact
Route to Claim-safety review before publication when the user task matches financial_claim_publication_review and needs A source-bound claim-safety note that separates exact claim text, evidence links, retrieval time, blocked language, safe restatement, and human-escalation requirements.
Do not use as: live approval, investment advice, compliance clearance, real-time screening, backtesting or execution advice

Pack selection matrix

Choose the right static evidence pack before opening JSON

This matrix gives crawlers and agents a compact route into the catalog: which page to open, which sample evidence card anchors the pack, how many sources are in the manifest, and which citation version to preserve.

PackServiceSource handoffEntry points
Counterparty screening before payment
Start here first
Action PreflightSample card counterparty_screening_pack_sample_evidence_card
Source manifest 8; Official registries 5
Profile registry_heavy; Registry primary_for_this_static_pack
Workflow counterparty_screening_pack_agent_workflow; Action counterparty_payment_review
Source review policy 30 days; next 2026-06-24T00:00:00.000Z
sourceReviewPolicy.nextRecommendedReviewAt 2026-06-24T00:00:00.000Z
sourceReviewPolicy.refreshRequiredWhen 4 triggers
Case readiness checklist counterparty_screening_pack_case_readiness_checklist
caseReadinessChecklist sourceFreshnessGate Before reuse, compare the case date and cited source retrieval plan with sourceReviewPolicy.nextRecommendedReviewAt=2026-06-24T00:00:00.000Z; if the static snapshot is stale, re-check sources and version the artifact before using it.
Case worksheet counterparty_screening_pack_case_worksheet
caseWorksheet worksheetType counterparty_source_query_ledger
Citation version public-material-counterparty-screening-pack-2026-05-25
HTML page
JSON artifact
Claim-safety review before publication
Start here next
Reliability CorpusSample card claim_safety_pack_sample_evidence_card
Source manifest 6; Official registries 0
Profile guidance_heavy; Registry not_primary_for_this_static_pack
Workflow claim_safety_pack_agent_workflow; Action financial_claim_publication_review
Source review policy 90 days; next 2026-08-23T00:00:00.000Z
sourceReviewPolicy.nextRecommendedReviewAt 2026-08-23T00:00:00.000Z
sourceReviewPolicy.refreshRequiredWhen 4 triggers
Case readiness checklist claim_safety_pack_case_readiness_checklist
caseReadinessChecklist sourceFreshnessGate Before reuse, compare the case date and cited source retrieval plan with sourceReviewPolicy.nextRecommendedReviewAt=2026-08-23T00:00:00.000Z; if the static snapshot is stale, re-check sources and version the artifact before using it.
Case worksheet claim_safety_pack_case_worksheet
caseWorksheet worksheetType claim_redline_ledger
Citation version public-material-claim-safety-pack-2026-05-25
HTML page
JSON artifact
Crypto signal subscription before payment
Start here first
Action PreflightSample card crypto_signal_subscription_pack_sample_evidence_card
Source manifest 6; Official registries 2
Profile mixed_official_sources; Registry supporting_for_this_static_pack
Workflow crypto_signal_subscription_pack_agent_workflow; Action crypto_signal_subscription_payment
Source review policy 60 days; next 2026-07-24T00:00:00.000Z
sourceReviewPolicy.nextRecommendedReviewAt 2026-07-24T00:00:00.000Z
sourceReviewPolicy.refreshRequiredWhen 3 triggers
Case readiness checklist crypto_signal_subscription_pack_case_readiness_checklist
caseReadinessChecklist 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.
Case worksheet crypto_signal_subscription_pack_case_worksheet
caseWorksheet worksheetType generic_static_case_ledger
Citation version public-material-crypto-signal-subscription-pack-2026-05-25
HTML page
JSON artifact
Wallet transfer to unverified counterparty
Start here next
Action PreflightSample card wallet_transfer_unverified_counterparty_pack_sample_evidence_card
Source manifest 7; Official registries 3
Profile mixed_official_sources; Registry supporting_for_this_static_pack
Workflow wallet_transfer_unverified_counterparty_pack_agent_workflow; Action wallet_transfer_unverified_counterparty
Source review policy 30 days; next 2026-06-24T00:00:00.000Z
sourceReviewPolicy.nextRecommendedReviewAt 2026-06-24T00:00:00.000Z
sourceReviewPolicy.refreshRequiredWhen 4 triggers
Case readiness checklist wallet_transfer_unverified_counterparty_pack_case_readiness_checklist
caseReadinessChecklist sourceFreshnessGate Before reuse, compare the case date and cited source retrieval plan with sourceReviewPolicy.nextRecommendedReviewAt=2026-06-24T00:00:00.000Z; if the static snapshot is stale, re-check sources and version the artifact before using it.
Case worksheet wallet_transfer_unverified_counterparty_pack_case_worksheet
caseWorksheet worksheetType generic_static_case_ledger
Citation version public-material-wallet-transfer-unverified-counterparty-pack-2026-05-25
HTML page
JSON artifact
Macro release context packaging
Then expand: macro context
Evidence CardsSample card macro_release_context_pack_sample_evidence_card
Source manifest 6; Official registries 2
Profile mixed_official_sources; Registry supporting_for_this_static_pack
Workflow macro_release_context_pack_agent_workflow; Action macro_release_context_interpretation
Source review policy 60 days; next 2026-07-24T00:00:00.000Z
sourceReviewPolicy.nextRecommendedReviewAt 2026-07-24T00:00:00.000Z
sourceReviewPolicy.refreshRequiredWhen 3 triggers
Case readiness checklist macro_release_context_pack_case_readiness_checklist
caseReadinessChecklist 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.
Case worksheet macro_release_context_pack_case_worksheet
caseWorksheet worksheetType generic_static_case_ledger
Citation version public-material-macro-release-context-pack-2026-05-25
HTML page
JSON artifact
Payment instruction change before settlement
Start here next
Action PreflightSample card payment_instruction_change_pack_sample_evidence_card
Source manifest 5; Official registries 0
Profile guidance_heavy; Registry not_primary_for_this_static_pack
Workflow payment_instruction_change_pack_agent_workflow; Action payment_instruction_change_before_settlement
Source review policy 60 days; next 2026-07-24T00:00:00.000Z
sourceReviewPolicy.nextRecommendedReviewAt 2026-07-24T00:00:00.000Z
sourceReviewPolicy.refreshRequiredWhen 4 triggers
Case readiness checklist payment_instruction_change_pack_case_readiness_checklist
caseReadinessChecklist 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.
Case worksheet payment_instruction_change_pack_case_worksheet
caseWorksheet worksheetType generic_static_case_ledger
Citation version public-material-payment-instruction-change-pack-2026-05-25
HTML page
JSON artifact
Public company filing review
Then expand: filing review
Evidence CardsSample card public_company_filing_pack_sample_evidence_card
Source manifest 4; Official registries 3
Profile registry_heavy; Registry primary_for_this_static_pack
Workflow public_company_filing_pack_agent_workflow; Action public_company_filing_review
Source review policy 60 days; next 2026-07-24T00:00:00.000Z
sourceReviewPolicy.nextRecommendedReviewAt 2026-07-24T00:00:00.000Z
sourceReviewPolicy.refreshRequiredWhen 3 triggers
Case readiness checklist public_company_filing_pack_case_readiness_checklist
caseReadinessChecklist 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.
Case worksheet public_company_filing_pack_case_worksheet
caseWorksheet worksheetType generic_static_case_ledger
Citation version public-material-public-company-filing-pack-2026-05-25
HTML page
JSON artifact

Material packs

Full catalog

After the recommended start packs, use the full catalog when the task is broader, more source-specific, or needs a different evidence shape.

Start here first

Counterparty screening before payment

Linked service: Action Preflight

Why start here: Start here first when an agent is close to moving money, accepting new payment instructions, or acting on weak counterparty evidence.

A financial agent is about to prepare a cross-border vendor payment or wallet transfer to a new counterparty with incomplete verification.

Use this static pack before a financial agent accepts a counterparty, beneficiary, invoice, wallet, or settlement instruction as safe enough for payment.

Why it matters: This is a real high-risk pre-action scenario where static risk review material is more useful than generic trading copy.

Detail page: /agent-verification/materials/counterparty-screening-pack

JSON artifact: /reliability/public-materials/counterparty-screening-pack.json

Artifact version: public-material-counterparty-screening-pack-2026-05-25

Source count: 8

Source snapshot: 2026-05-25T00:00:00.000Z

Source review policy: review every 30 days; nextRecommendedReviewAt 2026-06-24T00:00:00.000Z.

Misuse patterns: 3; highest severity block; misusePatternIndex labels No-hit treated as clearance, Aggregator context treated as official clearance, Beneficiary or wallet destination collapsed into counterparty identity

Case readiness checklist: counterparty_screening_pack_case_readiness_checklist; sourceFreshnessGate Before reuse, compare the case date and cited source retrieval plan with sourceReviewPolicy.nextRecommendedReviewAt=2026-06-24T00:00:00.000Z; if the static snapshot is stale, re-check sources and version the artifact before using it.

Case worksheet: counterparty_screening_pack_case_worksheet; worksheetType counterparty_source_query_ledger; rows 5

Inputs

  • 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

Outputs

  • allow/review/block decision with risk flags
  • required counterparty checks before payment
  • safe next step and limitations

Suitable for

  • AI agents preparing vendor payments, wallet transfers, or account-linking flows
  • Human reviewers checking whether the counterparty evidence is too weak to proceed
  • Crawlers and retrieval systems that need a concrete public example of pre-action reliability work

Not suitable for

  • 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 clear a counterparty, confirm beneficial ownership, or replace formal sanctions/compliance review.

Source / limitation policy

  • https://ofac.treasury.gov/sanctions-list-service
  • https://www.trade.gov/consolidated-screening-list
  • https://open.gsa.gov/api/exclusions-api/
  • https://www.worldbank.org/en/projects-operations/procurement/debarred-firms
  • https://www.cftc.gov/LearnAndProtect/Resources/Check/redlist.htm
  • https://www.opensanctions.org/
  • https://consumer.ftc.gov/articles/what-know-about-cryptocurrency-scams

Start here next

Claim-safety review before publication

Linked service: Reliability Corpus

Why start here: Start here next when an agent is about to restate evidence, strategy language, or marketing claims in public-facing form.

An agent is about to restate marketing, evidence, or strategy claims in public-facing language and needs a warning-layer review first.

Use this static pack before a financial agent publishes, promotes, or restates a claim that could overstate evidence, safety, suitability, approval, or expected outcomes.

Why it matters: This is one of the most reusable reliability tasks because many financial-agent failures come from overclaiming, not from missing raw data.

Detail page: /agent-verification/materials/claim-safety-pack

JSON artifact: /reliability/public-materials/claim-safety-pack.json

Artifact version: public-material-claim-safety-pack-2026-05-25

Source count: 6

Source snapshot: 2026-05-25T00:00:00.000Z

Source review policy: review every 90 days; nextRecommendedReviewAt 2026-08-23T00:00:00.000Z.

Misuse patterns: 3; highest severity block; misusePatternIndex labels Evidence upgraded into verified-and-safe guarantee, Missing retrieval or source scope treated as publishable, Softened paraphrase hides the unsafe original claim

Case readiness checklist: claim_safety_pack_case_readiness_checklist; sourceFreshnessGate Before reuse, compare the case date and cited source retrieval plan with sourceReviewPolicy.nextRecommendedReviewAt=2026-08-23T00:00:00.000Z; if the static snapshot is stale, re-check sources and version the artifact before using it.

Case worksheet: claim_safety_pack_case_worksheet; worksheetType claim_redline_ledger; rows 4

Inputs

  • domain: optional backtest_assumptions, runner_difference, claim_safety, or related category
  • severity: optional low, medium, or high
  • source: optional source-ref or text search
  • updatedSince: optional date filter for changed entries

Outputs

  • failure-pattern hits in the claim-safety domain
  • usage guidance for deeper review
  • do-not-upgrade boundaries for public language

Suitable for

  • AI agents drafting public financial summaries or promotional copy
  • Human reviewers checking whether evidence was upgraded into unsafe claims
  • Agent builders who need a static warning reference instead of a full scoring engine

Not suitable for

  • A corpus hit is a warning shape, not proof that every related strategy is invalid
  • The corpus does not replace runner verification or human judgment
  • Source behavior, platform documentation, and assumptions can change over time
  • The pack does not issue a legal verdict or certify marketing language as compliant.

Source / limitation policy

  • https://www.sec.gov/oiea/investor-alerts-and-bulletins
  • https://www.finra.org/investors/insights/artificial-intelligence-and-investment-fraud
  • https://www.finra.org/investors/insights/investment-group-imposter-scams
  • https://consumer.ftc.gov/articles/what-know-about-cryptocurrency-scams

Start here first

Crypto signal subscription before payment

Linked service: Action Preflight

Why start here: Start here first when an agent is asked to pay in crypto, trust guaranteed-return language, or connect a brokerage account for auto-trading access.

A financial agent is about to pay for a crypto signal group or invite-only trading club that promises guaranteed returns and asks for brokerage or custody access.

Use this static pack before a financial agent pays for a crypto signal subscription, trusts guaranteed-return language, or connects brokerage or custody access.

Why it matters: This is one of the clearest high-risk financial-agent actions in the current public scope: money movement, unsafe claim language, and account-access pressure all appear before trust is earned.

Detail page: /agent-verification/materials/crypto-signal-subscription-pack

JSON artifact: /reliability/public-materials/crypto-signal-subscription-pack.json

Artifact version: public-material-crypto-signal-subscription-pack-2026-05-25

Source count: 6

Source snapshot: 2026-05-25T00:00:00.000Z

Source review policy: review every 60 days; nextRecommendedReviewAt 2026-07-24T00:00:00.000Z.

Misuse patterns: 2; highest severity escalate; misusePatternIndex labels Static sample treated as live result, Missing inputs smoothed into confident output

Case readiness checklist: crypto_signal_subscription_pack_case_readiness_checklist; 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.

Case worksheet: crypto_signal_subscription_pack_case_worksheet; worksheetType generic_static_case_ledger; rows 1

Inputs

  • 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

Outputs

  • allow/review/block decision for the subscription or access request
  • risk flags for guaranteed-return, custody, brokerage, and payment-pressure language
  • required checks and safe next step before any payment or account access

Suitable for

  • AI agents preparing subscription, deposit, or account-link flows for trading groups or signal clubs
  • Human reviewers checking whether guaranteed-return marketing and custody requests should block the action
  • Crawlers and retrieval systems that need a concrete pre-action risk example beyond generic counterparty review

Not suitable for

  • 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 investigate the operator fully, verify all identities, or substitute for independent legal, custody, or brokerage-security review.

Source / limitation policy

  • https://consumer.ftc.gov/articles/what-know-about-cryptocurrency-scams
  • https://www.sec.gov/oiea/investor-alerts-and-bulletins
  • https://www.finra.org/investors/insights/artificial-intelligence-and-investment-fraud
  • https://brokercheck.finra.org/
  • https://adviserinfo.sec.gov/
  • https://www.cisa.gov/topics/cybersecurity-best-practices/multifactor-authentication

Start here next

Wallet transfer to unverified counterparty

Linked service: Action Preflight

Why start here: Start here next when a high-risk crypto wallet transfer points to a new counterparty and the destination remains irreversible, weakly verified, or private-group only.

A financial agent is asked to send a crypto wallet transfer to a new counterparty in a private group, but the wallet address, ownership claims, and counterparty identity are not independently verified.

Use this static pack before a financial agent sends crypto to a wallet destination that has weak counterparty or ownership evidence.

Why it matters: Irreversible wallet transfer plus opaque counterparty evidence is one of the clearest high-risk action-preflight scenarios in the current public scope.

Detail page: /agent-verification/materials/wallet-transfer-unverified-counterparty-pack

JSON artifact: /reliability/public-materials/wallet-transfer-unverified-counterparty-pack.json

Artifact version: public-material-wallet-transfer-unverified-counterparty-pack-2026-05-25

Source count: 7

Source snapshot: 2026-05-25T00:00:00.000Z

Source review policy: review every 30 days; nextRecommendedReviewAt 2026-06-24T00:00:00.000Z.

Misuse patterns: 2; highest severity escalate; misusePatternIndex labels Static sample treated as live result, Missing inputs smoothed into confident output

Case readiness checklist: wallet_transfer_unverified_counterparty_pack_case_readiness_checklist; sourceFreshnessGate Before reuse, compare the case date and cited source retrieval plan with sourceReviewPolicy.nextRecommendedReviewAt=2026-06-24T00:00:00.000Z; if the static snapshot is stale, re-check sources and version the artifact before using it.

Case worksheet: wallet_transfer_unverified_counterparty_pack_case_worksheet; worksheetType generic_static_case_ledger; rows 1

Inputs

  • 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

Outputs

  • block/review decision for the wallet transfer request
  • risk flags for counterparty weakness, wallet-ownership gaps, explorer ambiguity, and irreversible-payment pressure
  • required verification steps before any crypto transfer proceeds

Suitable for

  • AI agents preparing wallet transfers, OTC settlement drafts, or private-group payment flows
  • Human reviewers checking whether a wallet destination and counterparty record are too weak to justify transfer
  • Crawlers and retrieval systems that need a concrete public example of wallet-transfer reliability review

Not suitable for

  • 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, recover sent funds, or replace sanctions, legal, custody, or compliance review.
  • The pack is not a token-risk, meme-coin, smart contract, liquidity, rug-pull, or wallet-forensics scanner.

Source / limitation policy

  • https://consumer.ftc.gov/articles/what-know-about-cryptocurrency-scams
  • https://consumer.ftc.gov/articles/what-do-if-you-were-scammed
  • https://www.fbi.gov/how-we-can-help-you/victim-services/national-crimes-and-victim-resources/cryptocurrency-investment-fraud
  • https://ofac.treasury.gov/sanctions-list-service
  • https://ofac.treasury.gov/system/files/126/virtual_currency_guidance_brochure.pdf
  • https://www.cftc.gov/LearnAndProtect/AdvisoriesAndArticles/Beware_Imposters

Then expand: macro context

Macro release context packaging

Linked service: Evidence Cards

An agent wants to summarize a macro release without turning a single data point into a market-outcome claim.

Use this static pack when a financial agent needs to package macro release facts without turning them into market-direction or portfolio advice.

Why it matters: This shows how public evidence packs can help an agent stay source-bound and time-bound instead of sounding overconfident.

Detail page: /agent-verification/materials/macro-release-context-pack

JSON artifact: /reliability/public-materials/macro-release-context-pack.json

Artifact version: public-material-macro-release-context-pack-2026-05-25

Source count: 6

Source snapshot: 2026-05-25T00:00:00.000Z

Source review policy: review every 60 days; nextRecommendedReviewAt 2026-07-24T00:00:00.000Z.

Misuse patterns: 2; highest severity escalate; misusePatternIndex labels Static sample treated as live result, Missing inputs smoothed into confident output

Case readiness checklist: macro_release_context_pack_case_readiness_checklist; 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.

Case worksheet: macro_release_context_pack_case_worksheet; worksheetType generic_static_case_ledger; rows 1

Inputs

  • entity: company, asset, counterparty, macro series, or research topic
  • sources: public source definitions with source refs and fields
  • observedAt: optional source observation time
  • retrievedAt: retrieval time for the static card package

Outputs

  • source-bound evidence cards with observed and retrieved time
  • safe statements vs blocked statements
  • limitations that stop one-release-overclaim behavior

Suitable for

  • AI agents drafting market summaries from public macro releases
  • Analysts who want machine-readable source packages for later audit
  • Search and AI crawlers looking for an evidence-only financial content example

Not suitable for

  • Evidence Cards package sources; they do not value securities or recommend action
  • Source freshness, methodology, and field definitions can change after retrieval
  • Name-only or source-only evidence is not legal or compliance clearance
  • The pack does not predict price direction, infer Federal Reserve decisions, or convert macro evidence into a trading recommendation.

Source / limitation policy

  • https://fred.stlouisfed.org/docs/api/fred/
  • https://fred.stlouisfed.org/docs/api/fred/series/series_observations.html
  • https://www.bls.gov/cpi/data.htm
  • https://www.bls.gov/bls/api_features.htm
  • https://www.cftc.gov/MarketReports/CommitmentsofTraders/index.htm
  • https://www.cftc.gov/MarketReports/CommitmentsofTraders/HistoricalCompressed/index.htm

Start here next

Payment instruction change before settlement

Linked service: Action Preflight

Why start here: 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.

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.

Use this static pack before a financial agent accepts changed payment instructions, new bank details, new wallet details, or last-minute beneficiary changes.

Why it matters: Changed payment instructions are a classic irreversible-action risk: the money can move before identity, beneficiary ownership, and instruction legitimacy are verified.

Detail page: /agent-verification/materials/payment-instruction-change-pack

JSON artifact: /reliability/public-materials/payment-instruction-change-pack.json

Artifact version: public-material-payment-instruction-change-pack-2026-05-25

Source count: 5

Source snapshot: 2026-05-25T00:00:00.000Z

Source review policy: review every 60 days; nextRecommendedReviewAt 2026-07-24T00:00:00.000Z.

Misuse patterns: 2; highest severity escalate; misusePatternIndex labels Static sample treated as live result, Missing inputs smoothed into confident output

Case readiness checklist: payment_instruction_change_pack_case_readiness_checklist; 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.

Case worksheet: payment_instruction_change_pack_case_worksheet; worksheetType generic_static_case_ledger; rows 1

Inputs

  • 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

Outputs

  • 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

Suitable for

  • 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

Not suitable for

  • 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.

Source / limitation policy

  • 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

Then expand: filing review

Public company filing review

Linked service: Evidence Cards

An agent needs bounded evidence around a company filing event before drafting a public-facing summary or internal note.

Use this static pack when a financial agent needs to summarize a public company filing event without upgrading filing facts into valuation or recommendation claims.

Why it matters: This is a useful middle ground between full securities research and generic AI summarization: preserve provenance, timestamps, and limits.

Detail page: /agent-verification/materials/public-company-filing-pack

JSON artifact: /reliability/public-materials/public-company-filing-pack.json

Artifact version: public-material-public-company-filing-pack-2026-05-25

Source count: 4

Source snapshot: 2026-05-25T00:00:00.000Z

Source review policy: review every 60 days; nextRecommendedReviewAt 2026-07-24T00:00:00.000Z.

Misuse patterns: 2; highest severity escalate; misusePatternIndex labels Static sample treated as live result, Missing inputs smoothed into confident output

Case readiness checklist: public_company_filing_pack_case_readiness_checklist; 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.

Case worksheet: public_company_filing_pack_case_worksheet; worksheetType generic_static_case_ledger; rows 1

Inputs

  • entity: company, asset, counterparty, macro series, or research topic
  • sources: public source definitions with source refs and fields
  • observedAt: optional source observation time
  • retrievedAt: retrieval time for the static card package

Outputs

  • evidence cards for the filing source set
  • statements that can be repeated safely
  • blocked statements that would over-upgrade the filing

Suitable for

  • AI agents writing filing-based summaries
  • Human reviewers checking whether a filing summary stayed source-bound
  • Crawlers that need a concrete evidence-pack example for company-event review

Not suitable for

  • Evidence Cards package sources; they do not value securities or recommend action
  • Source freshness, methodology, and field definitions can change after retrieval
  • Name-only or source-only evidence is not legal or compliance clearance
  • The pack does not produce valuation, price targets, suitability conclusions, or real-time securities research.

Source / limitation policy

  • https://www.sec.gov/search-filings
  • https://www.sec.gov/search-filings/edgar-application-programming-interfaces
  • https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data

Machine-readable

Public Materials JSON artifact

The JSON artifact is the machine-readable version of this pack catalog. It is static, public, and safe to crawl. It exposes packs, sampleEvidenceCards, citationIndex, actionRoutingIndex, inputFieldGlossary, preflightQuestionnaireIndex, preflightDecisionPolicyIndex, staticActionNoteTemplateIndex, staticActionNoteExampleIndex, agentWorkflowIndex, misusePatternIndex, actionTypeWorkflowLookup, searchIntentIndex, sourceQualityRollup, sourceReviewPolicyIndex, caseReadinessChecklistIndex, caseWorksheetIndex, and sourceManifests so agents can choose compact action, citation, field, question, policy, output-template, filled-example, workflow, misuse-pattern, action lookup, search-intent lookup, source-review policy, case-readiness checklist, case worksheet, and source-quality summaries first or inspect the full source manifest when needed.

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

Citation fields: artifactVersion, generatedAt, packs[].artifactProvenance.artifactVersion, packs[].sampleEvidenceRecords[].retrievedAt, packs[].sourceRefs

citationIndex: compact pack-level citation handoffs with service, page, JSON artifact, sample evidence card, source count, source snapshot, and canonical citation.

actionRoutingIndex: compact pack-level action routing with action type, preflight stage, default posture, primary action risk, minimum required inputs, missing-input fallback, route triggers, and stop/escalation triggers.

inputFieldGlossary: reusable field definitions for high-risk action preflight inputs, including example values, action coverage, and missing-input risk.

preflightQuestionnaireIndex: static question sets derived from each pack's minimum input field order, including acceptable evidence and missing-input handling.

preflightDecisionPolicyIndex: static proceed/fallback/stop rules derived from the questionnaire, pack escalation triggers, and safe/blocked output boundaries.

misusePatternIndex: static failure-mode patterns that tell agents which false signals, unsafe upgrades, and blocked actions must stay visible before using a pack.

staticActionNoteTemplateIndex: static output templates with required sections, citation requirements, prohibited uses, and final boundary language for source-bound action notes.

staticActionNoteExampleIndex: filled static action note examples derived from each pack's sample input, cited evidence records, safe/blocked restatements, and canonical citation.

agentWorkflowIndex: ordered pack-level workflow steps linking routing, inputs, questionnaire, decision policy, static note template, filled example, source manifest, and citation trail.

actionTypeWorkflowLookup: direct action-type keyed workflow lookup with pack page, JSON artifact, minimum input field ids, example id, citation text, and escalation rule.

searchIntentIndex: natural-language query routing with query examples, target pack page, JSON artifact, action type, and static-use boundary.

sourceQualityRollup: compact pack-level source coverage with source kinds, source counts, source profile, registry expectation, source-mix rationale, official-source counts, sample evidence count, and static-only boundaries.

sourceReviewPolicyIndex: compact pack-level source freshness, review cadence, nextRecommendedReviewAt, refresh triggers, stale signals, and static-use boundaries.

caseReadinessChecklistIndex: compact pack-level case-readiness handoff with requiredEvidenceFieldIds, sourceFreshnessGate, mustConfirmBeforeUse, notReadySignals, readyStaticHandoff, and escalationWhen.

caseWorksheetIndex: compact pack-level case worksheet handoff with worksheetType, evidenceToCapture, resultSemantics, safeRewrite, blockedRewrite, and escalationReason.

Source review policy count: 7

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.