TRADING4AIStatic public material pack for financial-agent reliability review

Public Material Pack

Crypto signal subscription before payment

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.

Open JSON artifactPublic Materials IndexReliability Home

Boundary

Pages-only static material in this phase.

No backend judgment, no backtesting, no Tencent runtime, and no user-submitted verification queue.

This pack is public review guidance, not compliance clearance or final approval.

Plain-language summary

Read this before treating the pack as evidence

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

Example input

A user asks whether they should pay USDT for a private crypto signal group that promises guaranteed monthly returns and asks for brokerage access.

Expected static output

A source-bound action note that separates subscription claims, payment pressure, account-access risk, missing evidence, blocked language, and escalation rules.

Best used when

  • A crypto, AI trading, or signal subscription request appears before money or account access moves.
  • The agent needs to preserve guaranteed-return, custody, brokerage, payment, and operator-identity gaps before advising any next step.

Not used for

  • Live screening, live compliance clearance, or request-time approval.
  • Trading, backtesting, execution, investment advice, or legal advice.

Source freshness

This pack preserves a static source snapshot and citation trail; it does not fetch fresh third-party data at request time.

Agent reading hint

Read the HTML page first for boundaries, then use the JSON artifact for structured retrieval.

Why this pack exists

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.

Linked service: Action Preflight

Pack id: crypto_signal_subscription_pack

What this is not

Not a live review queue.

Not a request-time API.

Not a buy/sell/execute system.

Not a legal, sanctions, or compliance verdict.

Inputs / outputs

Stable contract for this scenario pack

Each pack stays readable for both humans and crawlers by using the same stable, bounded sections.

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

How to use this pack

Read the scenario boundary before you reuse the sample output

This page explains a single review scenario. Use it to understand what evidence the scenario needs, what a bounded output looks like, and when the reader should stop, escalate, or move to a linked artifact.

Use this pack when

  • Use this pack when the task already matches this scenario: 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 it when the reader needs a bounded checklist, sample evidence records, and an example of safe versus blocked language.
  • Treat Crypto signal subscription before payment as a scenario-specific public review guide that sits on top of the linked Action Preflight service.

Stop at this pack when

  • Stop at this pack when you need a public, static explanation of what should be checked and how the review should be framed.
  • Stop here when the goal is to teach a crawler, agent, or human reviewer the shape of the evidence rather than produce a live decision.
  • Escalate beyond this pack when the case becomes ambiguous, private, high-value, or legally sensitive.

Move to the linked artifact when

  • Open the linked JSON artifact when another system needs the stable machine-readable pack payload.
  • Move to the related service page when the task needs the broader service contract instead of only this scenario.
  • Treat the related artifacts as public references and handoff surfaces, not as live approval records.

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

Linked service page: Action Preflight

This pack does not do

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

Usage fit

Where this pack helps and where it stops

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

Delivery shape

What a real static review package needs to collect and return

These sections make the pack more than a scenario description. They define the minimum evidence set, the bounded outputs the review should return, and the citation rules that keep the result trustworthy.

Evidence to collect

  • The exact subscription pitch, payment instructions, wallet or payment destination, and any guaranteed-return or low-risk wording the user saw.
  • Whether the flow requests brokerage login, API keys, exchange credentials, wallet custody, remote-control software, or a signed authorization.
  • Named operator, company, domain, channel, and payment destination details, plus BrokerCheck, IAPD, and official-domain evidence where a registration or advisory claim is made.
  • Terms, refund language, custody scope, verified channel evidence, and any mismatch between the offer claims and the evidence that supports them.

Delivery outputs

  • A bounded evidence summary and source manifest that separate the offer claims from the public-source facts actually confirmed.
  • A block-or-review recommendation when payment pressure, guaranteed-return language, operator identity, registration claims, or custody access requests remain unresolved.
  • A concrete no-payment and no-connection checklist before any crypto payment, brokerage connection, API authorization, credential sharing, or custody handoff occurs.
  • Safe language explaining that the pack flags risk and missing evidence; it does not clear the operator, approve the subscription, or verify suitability.

Decision matrix

  • Operator identity and payment pressure row

    Status: unresolved

    Evidence fields: operator_identity, payment_destination, access_scope

    Source requirement: Record the seller or operator identity, payment destination, and any pressure to reveal brokerage, custody, or API access before any money or access moves.

    Allowed static use: Use this row to anchor the payment-pressure review and keep the operator identity boundary visible in a static pack.

    Blocked upgrade: Do not upgrade a subscription pitch into verified, safe, suitable, compliant, or guaranteed access.

    Agent action: Hold payment and access approval; verify identity and claim evidence or escalate.

  • Performance and guarantee claim row

    Status: warning

    Evidence fields: claim_evidence, source_links

    Source requirement: Record the exact return, low-risk, registration, refund, or guarantee claim and the public evidence or disclosure that is supposed to support it.

    Allowed static use: Use only as source-bound claim review and limitation-preserving restatement for the offer.

    Blocked upgrade: Do not say the signal subscription is proven, safe, approved, or guaranteed to perform.

    Agent action: Preserve the claim as evidence-only and escalate unsupported or guarantee language.

  • Account access and custody scope row

    Status: unresolved

    Evidence fields: access_scope, operator_identity, source_links

    Source requirement: Record any API key, brokerage login, custody, withdrawal, or automation access requested and the channel that requested it.

    Allowed static use: Use this row as a static access-scope evidence boundary that keeps account-control risk visible.

    Blocked upgrade: Do not convert access-scope text into a safe connection approval or a custody-compliant grant.

    Agent action: Refuse automatic access approval and route the request to review.

  • Official guidance and warning-source row

    Status: confirmed

    Evidence fields: source_links, claim_evidence

    Source requirement: Record official guidance, disclosure, warning, and registry links that explain why the offer is risky or unsupported.

    Allowed static use: Use cited guidance as a bounded warning layer for the request without claiming live clearance.

    Blocked upgrade: Do not treat warning-source citations as clearance or endorsement.

    Agent action: Preserve official-source citations and stop at the warning boundary.

Citation rules

  • Keep the offer wording tied to the exact claim text, source URL, and retrieval time whenever it is repeated.
  • Do not convert absence of proof-of-fraud into trust, safety, or approval language.
  • If custody, credentials, or brokerage access are requested, keep that risk visible in every summary rather than hiding it behind marketing copy.
  • Never restate the pack as evidence that the operator is safe, verified, or suitable for automatic trading.

Static sample deliverable

What a bounded review output can look like

These sample fields make the pack feel closer to a real deliverable: a sample input summary, concrete evidence records, and a bounded output that stays inside static-review limits.

Sample input summary

Draft subscription request: pay USDT to join a private crypto signal club that promises guaranteed monthly returns and asks the user to connect a brokerage account for auto-trading.

Sample evidence records

  • Offer headline promises guaranteed monthly returns with low or no downside

    Status: warning

    Source: FINRA artificial intelligence and investment fraud

    Retrieved: 2026-05-25T00:00:00.000Z

    FINRA artificial intelligence and investment fraud guidance supports treating AI or automated-investment promises as warning material, not proof of returns.

  • The operator asks for brokerage connection or API-key style access before trust is established

    Status: warning

    Source: CISA multi-factor authentication guidance

    Retrieved: 2026-05-25T00:00:00.000Z

    Credential, API, and account-access requests expand the blast radius beyond a content subscription and require separate account-security review.

  • No independently cited public source confirms the operator identity behind the private group

    Status: unresolved

    Source: SEC investor alerts and bulletins

    Retrieved: 2026-05-25T00:00:00.000Z

    A chat alias and payment wallet alone do not establish operator legitimacy.

  • BrokerCheck lookup evidence is missing for any broker or brokerage-registration claim in the subscription pitch

    Status: unresolved

    Source: FINRA BrokerCheck

    Retrieved: 2026-05-25T00:00:00.000Z

    A missing or unmatched BrokerCheck result does not prove fraud, but it prevents the agent from treating a broker claim as verified.

  • IAPD lookup evidence is missing for any investment-adviser or advisory-service claim in the subscription pitch

    Status: unresolved

    Source: SEC Investment Adviser Public Disclosure (IAPD)

    Retrieved: 2026-05-25T00:00:00.000Z

    A registration lookup is source evidence, not approval to pay or connect an account; missing evidence keeps the offer blocked.

  • Payment is requested in crypto through an irreversible wallet transfer with no bounded refund evidence

    Status: warning

    Source: FTC cryptocurrency scam guidance

    Retrieved: 2026-05-25T00:00:00.000Z

    Irreversible payment increases the cost of acting before verification is complete.

Evidence Card sample

Crypto signal subscription before payment sample evidence card

Review verdict: block

Checked the subscription pitch, registration lookup requirements, and cited public warning sources at the listed retrieval time; do not pay, do not connect brokerage/API/custody access, and treat the operator as not cleared because guaranteed-return claims, irreversible crypto payment pressure, and account-access risks remain unresolved.

Citation block

  • artifactVersion=public-material-crypto-signal-subscription-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/crypto-signal-subscription-pack
  • artifactPath=/reliability/public-materials/crypto-signal-subscription-pack.json

Key findings

  • warning: Offer headline promises guaranteed monthly returns with low or no downside (FINRA artificial intelligence and investment fraud guidance supports treating AI or automated-investment promises as warning material, not proof of returns.)
  • warning: The operator asks for brokerage connection or API-key style access before trust is established (Credential, API, and account-access requests expand the blast radius beyond a content subscription and require separate account-security review.)
  • unresolved: No independently cited public source confirms the operator identity behind the private group (A chat alias and payment wallet alone do not establish operator legitimacy.)
  • unresolved: BrokerCheck lookup evidence is missing for any broker or brokerage-registration claim in the subscription pitch (A missing or unmatched BrokerCheck result does not prove fraud, but it prevents the agent from treating a broker claim as verified.)
  • unresolved: IAPD lookup evidence is missing for any investment-adviser or advisory-service claim in the subscription pitch (A registration lookup is source evidence, not approval to pay or connect an account; missing evidence keeps the offer blocked.)
  • warning: Payment is requested in crypto through an irreversible wallet transfer with no bounded refund evidence (Irreversible payment increases the cost of acting before verification is complete.)

Required disclosures

  • 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 investigate the operator fully, verify all identities, or substitute for independent legal, custody, or brokerage-security review.
  • No cited source verifies the operator identity behind the private group well enough to justify payment or account access.
  • The offer language upgrades marketing claims into guaranteed outcomes without evidence that can support them.
  • The requested brokerage or custody access would expand risk before the subscription itself is validated.

Do not claim

  • This crypto signal group is safe.
  • The guaranteed-return subscription is approved for payment.
  • The operator is verified and the brokerage connection can proceed automatically.

Action routing

actionRouting type: crypto_signal_subscription_payment

Preflight stage: before_payment_or_account_connection

Default posture: block

Primary action risk: Payment, custody, brokerage/API access, or credentials may move before operator identity and performance claims are verified.

Minimum input field ids: operator_identity, payment_destination, claim_evidence, access_scope

Minimum required inputs

  • Seller or operator name plus a public website, profile, or legal entity claim controlled by the offer.
  • Requested payment destination and rail, including wallet, account, invoice, subscription link, or checkout page.
  • Evidence supporting performance, risk, registration, custody, account-access, and refund claims.
  • Any requested API key, brokerage login, custody permission, private-channel instruction, or automation access.

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.

Route when

  • A user or agent is considering paying for a crypto, AI trading, or signal subscription.
  • The offer includes guaranteed-return, low-risk, custody, brokerage connection, API key, or private-channel pressure.

Stop or escalate when

  • Guaranteed-return, low-risk, registration, or suitability claims remain unsupported by cited public evidence.
  • Payment destination, operator identity, custody scope, or account-access request is unresolved.

Search intent

Intent id: crypto_signal_subscription_pack_search_intent

User task: Check a crypto signal subscription, guaranteed-return offer, or paid group before sending funds or account access.

Route reason: 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.

queryExamples: check crypto signal before paying, crypto signal subscription safe, guaranteed return crypto signal, check Telegram crypto signal group, crypto trading club asks for brokerage access

Use when

  • A user or agent is considering paying for a crypto, AI trading, or signal subscription.
  • A crypto, AI trading, or signal subscription request appears before money or account access moves.
  • Read the HTML page first for boundaries, then use the JSON artifact for structured retrieval.

Do not use as

  • live approval
  • investment advice
  • compliance clearance
  • real-time screening
  • backtesting or execution advice

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.

Input field glossary

operator_identity: The seller, operator, issuer, vendor, or organization identity behind the request. Missing input risk: The agent may route money or trust claims to an unverified or impersonated operator.

payment_destination: The bank account, wallet address, checkout link, invoice beneficiary, or settlement rail that would receive funds. Missing input risk: The agent cannot compare the destination against the named counterparty or prior approved instructions.

claim_evidence: Source material supporting performance, risk, registration, approval, compliance, or safety claims. Missing input risk: The agent may repeat promotional language as if it were verified evidence.

access_scope: Credentials, API permissions, custody permissions, brokerage access, or automation rights being requested. Missing input risk: The agent may approve a request that silently grants trading, withdrawal, or custody control.

Preflight questionnaire

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.

operator_identity: What evidence identifies the operator identity for this crypto_signal_subscription_payment review? Acceptable evidence: legal name, known aliases, website, registration number, public profile. If missing: The agent may route money or trust claims to an unverified or impersonated operator. Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.

payment_destination: What evidence identifies the payment destination for this crypto_signal_subscription_payment review? Acceptable evidence: bank account, wallet address, subscription checkout URL, invoice beneficiary. If missing: The agent cannot compare the destination against the named counterparty or prior approved instructions. Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.

claim_evidence: What evidence identifies the claim evidence for this crypto_signal_subscription_payment review? Acceptable evidence: performance report, registration page, risk disclosure, audit statement. If missing: The agent may repeat promotional language as if it were verified evidence. Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.

access_scope: What evidence identifies the access scope for this crypto_signal_subscription_payment review? Acceptable evidence: API key scope, brokerage login request, withdrawal permission, custody authorization. If missing: The agent may approve a request that silently grants trading, withdrawal, or custody control. Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.

Decision policy

Default posture: block

Allowed static output: Checked the subscription pitch, registration lookup requirements, and cited public warning sources at the listed retrieval time; do not pay, do not connect brokerage/API/custody access, and treat the operator as not cleared because guaranteed-return claims, irreversible crypto payment pressure, and account-access risks remain unresolved.

Blocked static output: This crypto signal group is verified, safe, registered, suitable for users, guaranteed to return profits, and approved for automatic trading access.

Proceed only when

  • Collected and cited: Seller or operator name plus a public website, profile, or legal entity claim controlled by the offer.
  • Collected and cited: Requested payment destination and rail, including wallet, account, invoice, subscription link, or checkout page.
  • Collected and cited: Evidence supporting performance, risk, registration, custody, account-access, and refund claims.
  • Collected and cited: Any requested API key, brokerage login, custody permission, private-channel instruction, or automation access.

Fallback when missing inputs

Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.

Stop or escalate when

  • Guaranteed-return, low-risk, registration, or suitability claims remain unsupported by cited public evidence.
  • Payment destination, operator identity, custody scope, or account-access request is unresolved.
  • The offer promises guaranteed returns, low-risk certainty, or safety without evidence that can support those claims.
  • The user is asked to share brokerage credentials, API keys, custody rights, or remote-control access before trust is established.
  • Payment must be made in irreversible crypto or under urgency pressure before key facts can be verified.

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.

Decision guardrails

escalate: One or more minimum inputs are missing or uncited: Seller or operator name plus a public website, profile, or legal entity claim controlled by the offer.; Requested payment destination and rail, including wallet, account, invoice, subscription link, or checkout page.; Evidence supporting performance, risk, registration, custody, account-access, and refund claims.; Any requested API key, brokerage login, custody permission, private-channel instruction, or automation access.. Required action: Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains. Allowed output: Checked the subscription pitch, registration lookup requirements, and cited public warning sources at the listed retrieval time; do not pay, do not connect brokerage/API/custody access, and treat the operator as not cleared because guaranteed-return claims, irreversible crypto payment pressure, and account-access risks remain unresolved. Blocked upgrade: This crypto signal group is verified, safe, registered, suitable for users, guaranteed to return profits, and approved for automatic trading access. Human review required: yes.

block: Any stop-or-escalate trigger applies: Guaranteed-return, low-risk, registration, or suitability claims remain unsupported by cited public evidence.; Payment destination, operator identity, custody scope, or account-access request is unresolved.; The offer promises guaranteed returns, low-risk certainty, or safety without evidence that can support those claims.; The user is asked to share brokerage credentials, API keys, custody rights, or remote-control access before trust is established.; Payment must be made in irreversible crypto or under urgency pressure before key facts can be verified.. Required action: Stop automatic action, keep the unresolved risk visible, and route the item to human review before payment, publication, execution, or downstream trust transfer. Allowed output: The reviewed offer includes guaranteed-return and account-access risk signals that keep the action blocked pending human review. This pack can describe what was checked and what remains unresolved, but it does not verify the operator or approve payment. Irreversible crypto payment and pre-trust custody requests remain visible risk factors even if some public details are present. Blocked upgrade: This crypto signal group is safe. The guaranteed-return subscription is approved for payment. The operator is verified and the brokerage connection can proceed automatically. Human review required: yes.

allow_with_limits: All minimum inputs are collected, cited, and no stop-or-escalate trigger applies; the output still remains a bounded static material summary. Required action: Emit only source-bound, timestamped, limitation-preserving static output and carry unresolved items into the final note. Allowed output: Checked the subscription pitch, registration lookup requirements, and cited public warning sources at the listed retrieval time; do not pay, do not connect brokerage/API/custody access, and treat the operator as not cleared because guaranteed-return claims, irreversible crypto payment pressure, and account-access risks remain unresolved. Blocked upgrade: This crypto signal group is verified, safe, registered, suitable for users, guaranteed to return profits, and approved for automatic trading access. Human review required: no.

Misuse patterns

escalate: Static sample treated as live result. False signal: The static pack contains a sample output, so the agent treats it as a fresh review of a new user request. Why misleading: Static public materials are pre-generated examples and do not fetch fresh sources, inspect private user data, or perform request-time judgment. Safe alternative: Use the pack as a format and boundary reference, then collect fresh source-bound evidence before making a case-specific note. Blocked agent action: Do not present the static sample as live approval, clearance, execution advice, or a completed review of the current case. Evidence fields: operator_identity, payment_destination, claim_evidence, access_scope.

warning: Missing inputs smoothed into confident output. False signal: The agent has partial source context and writes a fluent summary that hides missing required inputs. Why misleading: A fluent summary can transfer trust while required identifiers, source links, timestamps, or match semantics remain missing. Safe alternative: Name missing inputs explicitly and apply the pack's missing-input fallback instead of upgrading the posture. Blocked agent action: Do not turn incomplete evidence into confident public language, payment action, publication, transfer, or downstream trust. Evidence fields: operator_identity, payment_destination, claim_evidence, access_scope.

Static action note template

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

Required sections

  • action_context: State the action type, preflight stage, default posture, and collected minimum inputs: Seller or operator name plus a public website, profile, or legal entity claim controlled by the offer.; Requested payment destination and rail, including wallet, account, invoice, subscription link, or checkout page.; Evidence supporting performance, risk, registration, custody, account-access, and refund claims.; Any requested API key, brokerage login, custody permission, private-channel instruction, or automation access..
  • source_bound_evidence: List only cited evidence collected for this pack: The exact subscription pitch, payment instructions, wallet or payment destination, and any guaranteed-return or low-risk wording the user saw.; Whether the flow requests brokerage login, API keys, exchange credentials, wallet custody, remote-control software, or a signed authorization.; Named operator, company, domain, channel, and payment destination details, plus BrokerCheck, IAPD, and official-domain evidence where a registration or advisory claim is made.; Terms, refund language, custody scope, verified channel evidence, and any mismatch between the offer claims and the evidence that supports them..
  • decision_policy: Apply fallback 'Do not approve payment or account connection; collect the missing identity, payment, access, and claim evidence, then escalate if urgency or pressure remains.' and stop/escalate when any policy trigger applies.
  • safe_restatement: Use bounded language no stronger than: Checked the subscription pitch, registration lookup requirements, and cited public warning sources at the listed retrieval time; do not pay, do not connect brokerage/API/custody access, and treat the operator as not cleared because guaranteed-return claims, irreversible crypto payment pressure, and account-access risks remain unresolved.
  • blocked_language: Do not restate or imply: This crypto signal group is verified, safe, registered, suitable for users, guaranteed to return profits, and approved for automatic trading access.
  • citation_trail: Preserve citation requirements: Keep the offer wording tied to the exact claim text, source URL, and retrieval time whenever it is repeated.; Do not convert absence of proof-of-fraud into trust, safety, or approval language.; If custody, credentials, or brokerage access are requested, keep that risk visible in every summary rather than hiding it behind marketing copy.; Never restate the pack as evidence that the operator is safe, verified, or suitable for automatic trading..

Static action note example

Example id: crypto_signal_subscription_pack_static_action_note_example

Note status: block

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

This is a static action note template, not approval, not live screening, not backtesting, not execution advice, and not a clearance decision.

Filled sections

  • action_context: Draft subscription request: pay USDT to join a private crypto signal club that promises guaranteed monthly returns and asks the user to connect a brokerage account for auto-trading. Action type: crypto_signal_subscription_payment. Default posture: block. Minimum inputs: Seller or operator name plus a public website, profile, or legal entity claim controlled by the offer.; Requested payment destination and rail, including wallet, account, invoice, subscription link, or checkout page.; Evidence supporting performance, risk, registration, custody, account-access, and refund claims.; Any requested API key, brokerage login, custody permission, private-channel instruction, or automation access..
  • source_bound_evidence: warning: Offer headline promises guaranteed monthly returns with low or no downside. FINRA artificial intelligence and investment fraud guidance supports treating AI or automated-investment promises as warning material, not proof of returns. warning: The operator asks for brokerage connection or API-key style access before trust is established. Credential, API, and account-access requests expand the blast radius beyond a content subscription and require separate account-security review. unresolved: No independently cited public source confirms the operator identity behind the private group. A chat alias and payment wallet alone do not establish operator legitimacy. unresolved: BrokerCheck lookup evidence is missing for any broker or brokerage-registration claim in the subscription pitch. A missing or unmatched BrokerCheck result does not prove fraud, but it prevents the agent from treating a broker claim as verified. unresolved: IAPD lookup evidence is missing for any investment-adviser or advisory-service claim in the subscription pitch. A registration lookup is source evidence, not approval to pay or connect an account; missing evidence keeps the offer blocked. warning: Payment is requested in crypto through an irreversible wallet transfer with no bounded refund evidence. Irreversible payment increases the cost of acting before verification is complete.
  • decision_policy: block: The sample subscription should not proceed because guaranteed-return claims, irreversible crypto payment, and pre-trust brokerage access requests remain unresolved. Unresolved items: No cited source verifies the operator identity behind the private group well enough to justify payment or account access.; The offer language upgrades marketing claims into guaranteed outcomes without evidence that can support them.; The requested brokerage or custody access would expand risk before the subscription itself is validated. Required follow-up: Do not pay or connect brokerage access until the operator identity, custody scope, and refund terms are independently verified.; Capture the exact marketing claims and any account-access request in the final evidence card before restating the offer.; Escalate to human review if the user is still considering payment after the guaranteed-return and custody risks are explained..
  • safe_restatement: Checked the subscription pitch, registration lookup requirements, and cited public warning sources at the listed retrieval time; do not pay, do not connect brokerage/API/custody access, and treat the operator as not cleared because guaranteed-return claims, irreversible crypto payment pressure, and account-access risks remain unresolved.
  • blocked_language: This crypto signal group is verified, safe, registered, suitable for users, guaranteed to return profits, and approved for automatic trading access.
  • citation_trail: Crypto signal subscription before payment, public-material-crypto-signal-subscription-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/crypto-signal-subscription-pack Citation requirements: Keep the offer wording tied to the exact claim text, source URL, and retrieval time whenever it is repeated.; Do not convert absence of proof-of-fraud into trust, safety, or approval language.; If custody, credentials, or brokerage access are requested, keep that risk visible in every summary rather than hiding it behind marketing copy.; Never restate the pack as evidence that the operator is safe, verified, or suitable for automatic trading..

Agent workflow

Workflow id: crypto_signal_subscription_pack_agent_workflow

Step ids: select_pack, collect_minimum_inputs, answer_preflight_questionnaire, apply_decision_policy, draft_static_action_note, cite_and_escalate

Linked example: crypto_signal_subscription_pack_static_action_note_example

Canonical citation: Crypto signal subscription before payment, public-material-crypto-signal-subscription-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/crypto-signal-subscription-pack

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.

Source quality

sourceQuality pack id: crypto_signal_subscription_pack

Action type: crypto_signal_subscription_payment

Workflow id: crypto_signal_subscription_pack_agent_workflow

Source kinds: official_guidance, official_registry

Source manifest count: 6

Official registry sources: 2

Official guidance sources: 4

Source quality profile: mixed_official_sources

Registry coverage expectation: supporting_for_this_static_pack

This pack mixes official guidance, public registries, sample context, and JSON artifacts; agents should use the profile to route review without treating source counts as clearance.

Agent source use

  • Use source kinds and counts as retrieval hints before opening the full source manifest.
  • Preserve sourceSnapshotAt, retrievedAt, limitations, and source roles in downstream summaries.
  • Do not treat a mixed source profile as live screening, approval, clearance, or execution advice.

Sample evidence records: 6

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

Boundary: static_source_manifest_not_live_screening

Source review policy

sourceReviewPolicy.nextRecommendedReviewAt: 2026-07-24T00:00:00.000Z

Review cadence: 60 days

Review mode: manual_public_source_recheck_required

Catalog field: sourceReviewPolicyIndex

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.

Refresh triggers (sourceReviewPolicy.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.

Case readiness checklist

caseReadinessChecklist: 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.

Default posture: block

Must confirm before use

  • Collected and cited every minimum input field: operator_identity, payment_destination, claim_evidence, access_scope.
  • 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.

Not ready signals

  • One or more required evidence fields are missing, uncited, or unresolved: operator_identity, payment_destination, claim_evidence, access_scope.
  • 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.

Ready static handoff

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

Case worksheet

caseWorksheet: crypto_signal_subscription_pack_case_worksheet

worksheetType: generic_static_case_ledger

Treat this worksheet as complete only when every row preserves source/citation fields, result semantics, safe rewrite, blocked rewrite, and escalation reason.

Static case scope row · TRADING4AI public material pack

Capture the case summary, source links, required input fields, sample evidence record references, audience or action context, and any unresolved source gaps before reuse.

Result semantics: Treat the row as an exact static-sample match, partial match, no-hit, unresolved match, or out-of-scope match before producing any handoff.

Unsafe category: static sample upgraded into live approval, safety, suitability, or execution guidance

Safe restatement: the static pack can describe cited evidence, unresolved items, source limitations, and a bounded next step at the listed retrieval time.

Do not say this static sample is verified, safe, compliant, suitable, approved, cleared, guaranteed, or permission to proceed.

Source manifest handoff

Sample evidence card id: crypto_signal_subscription_pack_sample_evidence_card

Source manifest entries: 6

Official registry sources: 2

Source quality boundary: static_source_manifest_not_live_screening

Canonical citation artifact version: public-material-crypto-signal-subscription-pack-2026-05-25

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

This is a static citation handoff for retrieval. It records cited sources, source roles, evidence links, and limitations without turning the pack into live clearance or approval.

Machine summary

Pack: crypto_signal_subscription_pack

Page: https://trading4ai.com/agent-verification/materials/crypto-signal-subscription-pack

Artifact: https://trading4ai.com/reliability/public-materials/crypto-signal-subscription-pack.json

Action type: crypto_signal_subscription_payment

Default posture: block

Minimum input fields: operator_identity, payment_destination, claim_evidence, access_scope

Decision matrix rows: 4

Evidence verification steps: 5

Misuse patterns: 2

Canonical citation: Crypto signal subscription before payment, public-material-crypto-signal-subscription-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/crypto-signal-subscription-pack

Agent use

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

Do not use as

  • live screening
  • payment approval
  • compliance clearance
  • trading or execution advice
  • proof that a counterparty, wallet, claim, filing, or macro interpretation is safe

Decision matrix labels

  • Operator identity and payment pressure row
  • Performance and guarantee claim row
  • Account access and custody scope row
  • Official guidance and warning-source row

Evidence verification step labels

  • Source manifest verification
  • Evidence record linkage check
  • Decision matrix boundary check
  • Canonical citation and timestamp check
  • Human escalation and blocked-upgrade check

Misuse pattern labels

  • Static sample treated as live result
  • Missing inputs smoothed into confident output

Evidence verification recipe

Pack: crypto_signal_subscription_pack

Default posture: block

Static only: yes

  • Source manifest verification

    Verification action: Check the static source manifest before citing this pack. Source kinds: official_guidance, official_registry. Source labels: FINRA artificial intelligence and investment fraud, CISA multi-factor authentication guidance, SEC investor alerts and bulletins, FINRA BrokerCheck, SEC Investment Adviser Public Disclosure (IAPD), FTC cryptocurrency scam guidance.

    Trust boundary: The source manifest is a static citation map, not live clearance, approval, compliance review, execution advice, or backtesting evidence.

    Failure mode: If a cited source, retrieval time, source role, or evidence record link is missing, keep the output bounded and escalate before upgrading the claim.

    Required citation fields: sourceManifest[].url, sourceManifest[].retrievedAt, sourceManifest[].kind, sampleEvidenceRecords[].id

  • Evidence record linkage check

    Verification action: Match each sample evidence record to a sourceManifest evidenceRecordIds entry, then preserve the record status, note, source label, source URL, and retrievedAt value.

    Trust boundary: 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.

    Failure mode: If a record cannot be linked to its source manifest row, do not reuse it as evidence and keep the final output unresolved.

    Required citation fields: sampleEvidenceRecords[].id, sampleEvidenceRecords[].status, sampleEvidenceRecords[].sourceUrl, sampleEvidenceRecords[].retrievedAt, sourceManifest[].evidenceRecordIds

  • Decision matrix boundary check

    Verification action: Read all 4 decision matrix rows and carry their allowedStaticUse, blockedUpgrade, and agentAction fields into any downstream summary.

    Trust boundary: Decision matrix rows define allowed static reuse and blocked upgrades; they are not automatic live approval, live screening, compliance sign-off, or execution permission.

    Failure mode: If a downstream sentence conflicts with a blockedUpgrade row, block or rewrite the sentence and escalate when money, publication, or user action is involved.

    Required citation fields: decisionMatrix[].matrixId, decisionMatrix[].status, decisionMatrix[].allowedStaticUse, decisionMatrix[].blockedUpgrade

  • Canonical citation and timestamp check

    Verification action: Preserve the canonical citation text, artifact version, generatedAt, staticSnapshotAt, sourceSnapshotAt, and all source retrievedAt values when citing this pack.

    Trust boundary: A citation proves the static artifact and source snapshot were recorded; it does not prove the facts are current beyond the listed timestamps.

    Failure mode: If artifact version, generatedAt, sourceSnapshotAt, or source retrievedAt values are removed, the output is no longer evidence-bound.

    Required citation fields: canonicalCitation.recommendedCitationText, artifactProvenance.artifactVersion, artifactProvenance.generatedAt, canonicalCitation.sourceSnapshotAt, sourceManifest[].retrievedAt

  • Human escalation and blocked-upgrade check

    Verification action: Compare the final output with the pack's blockedStatements, sampleReviewOutput.blockedRestatement, escalationTriggers, and actionTaxonomy.stopOrEscalateWhen fields.

    Trust boundary: 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.

    Failure mode: 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.

    Required citation fields: canonicalCitation.recommendedCitationText, artifactProvenance.artifactVersion, blockedStatements[], sampleReviewOutput.blockedRestatement, escalationTriggers[], actionTaxonomy.stopOrEscalateWhen[]

Cite this pack

Crypto signal subscription before payment, public-material-crypto-signal-subscription-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/crypto-signal-subscription-pack

Page: https://trading4ai.com/agent-verification/materials/crypto-signal-subscription-pack

Artifact: https://trading4ai.com/reliability/public-materials/crypto-signal-subscription-pack.json

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

Source manifest

  • FINRA artificial intelligence and investment fraud

    URL: https://www.finra.org/investors/insights/artificial-intelligence-and-investment-fraud

    Kind: official_guidance; role: primary_warning; retrieved: 2026-05-25T00:00:00.000Z

    Evidence records: guaranteed_return_claim

    Supports: Offer headline promises guaranteed monthly returns with low or no downside / 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.

    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.
  • CISA multi-factor authentication guidance

    URL: https://www.cisa.gov/topics/cybersecurity-best-practices/multifactor-authentication

    Kind: official_guidance; role: primary_warning; retrieved: 2026-05-25T00:00:00.000Z

    Evidence records: brokerage_access_request

    Supports: The operator asks for brokerage connection or API-key style access before trust is established / 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.

    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.
  • SEC investor alerts and bulletins

    URL: https://www.sec.gov/oiea/investor-alerts-and-bulletins

    Kind: official_guidance; role: official_reference; retrieved: 2026-05-25T00:00:00.000Z

    Evidence records: operator_identity_gap

    Supports: No independently cited public source confirms the operator identity behind the private group / 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.

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

    URL: https://brokercheck.finra.org/

    Kind: official_registry; role: supporting_reference; retrieved: 2026-05-25T00:00:00.000Z

    Evidence records: brokercheck_registration_gap

    Supports: BrokerCheck lookup evidence is missing for any broker or brokerage-registration claim in the subscription pitch / 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.

    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.
  • SEC Investment Adviser Public Disclosure (IAPD)

    URL: https://adviserinfo.sec.gov/

    Kind: official_registry; role: official_reference; retrieved: 2026-05-25T00:00:00.000Z

    Evidence records: iapd_adviser_registration_gap

    Supports: IAPD lookup evidence is missing for any investment-adviser or advisory-service claim in the subscription pitch / 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.

    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.
  • FTC cryptocurrency scam guidance

    URL: https://consumer.ftc.gov/articles/what-know-about-cryptocurrency-scams

    Kind: official_guidance; role: primary_warning; retrieved: 2026-05-25T00:00:00.000Z

    Evidence records: irreversible_crypto_payment

    Supports: Payment is requested in crypto through an irreversible wallet transfer with no bounded refund evidence / 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.

    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.

Sample bounded output

Verdict: block

The sample subscription should not proceed because guaranteed-return claims, irreversible crypto payment, and pre-trust brokerage access requests remain unresolved.

Safe restatement: Checked the subscription pitch, registration lookup requirements, and cited public warning sources at the listed retrieval time; do not pay, do not connect brokerage/API/custody access, and treat the operator as not cleared because guaranteed-return claims, irreversible crypto payment pressure, and account-access risks remain unresolved.

Blocked restatement: This crypto signal group is verified, safe, registered, suitable for users, guaranteed to return profits, and approved for automatic trading access.

Unresolved items

  • No cited source verifies the operator identity behind the private group well enough to justify payment or account access.
  • The offer language upgrades marketing claims into guaranteed outcomes without evidence that can support them.
  • The requested brokerage or custody access would expand risk before the subscription itself is validated.

Required follow-up

  • Do not pay or connect brokerage access until the operator identity, custody scope, and refund terms are independently verified.
  • Capture the exact marketing claims and any account-access request in the final evidence card before restating the offer.
  • Escalate to human review if the user is still considering payment after the guaranteed-return and custody risks are explained.

Review boundaries

How this pack should be used in practice

These sections turn the pack into a bounded public review aid: what to check, when to escalate, and which statements must stay inside evidence limits.

Review checklist

  • Record the exact pitch, guaranteed-return wording, automation claim, payment route, and subscription deadline before summarizing the offer.
  • Check whether the offer asks for brokerage credentials, custody delegation, API keys, wallet access, or irreversible wallet payment before trust is established.
  • Check whether any named broker, adviser, company, or operator can be matched to BrokerCheck, IAPD, official domain evidence, or another source you can cite rather than a chat alias only.
  • State clearly what remains unverified before any payment, deposit, brokerage connection, API authorization, or custody handoff goes forward.

Escalation triggers

  • The offer promises guaranteed returns, low-risk certainty, or safety without evidence that can support those claims.
  • The user is asked to share brokerage credentials, API keys, custody rights, or remote-control access before trust is established.
  • Payment must be made in irreversible crypto or under urgency pressure before key facts can be verified.

Safe to repeat

  • The reviewed offer includes guaranteed-return and account-access risk signals that keep the action blocked pending human review.
  • This pack can describe what was checked and what remains unresolved, but it does not verify the operator or approve payment.
  • Irreversible crypto payment and pre-trust custody requests remain visible risk factors even if some public details are present.

Blocked claims

  • This crypto signal group is safe.
  • The guaranteed-return subscription is approved for payment.
  • The operator is verified and the brokerage connection can proceed automatically.

Machine-readable

Static JSON artifact

The JSON artifact is the stable machine-facing handoff surface for this pack. It is static, public, and safe to crawl.

Artifact provenance

schemaVersion: trading4ai-public-reliability-v1

artifactVersion: public-material-crypto-signal-subscription-pack-2026-05-25

generatedAt: 2026-05-25T00:00:00.000Z

staticSnapshotAt: 2026-05-25T00:00:00.000Z

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

Citation fields: artifactVersion, generatedAt, sampleEvidenceRecords[].retrievedAt, sampleReviewOutput.verdict, sourceRefs

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.