TRADING4AIStatic public material pack for financial-agent reliability review

Public Material Pack

Macro release context packaging

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

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 when a financial agent needs to package macro release facts without turning them into market-direction or portfolio advice.

Example input

A user asks an agent to explain an inflation, employment, or rate-related release and wants to know what can be safely repeated from cited sources.

Expected static output

A source-bound evidence note that preserves release name, period, vintage, units, retrieval time, comparison limits, safe statements, and blocked market claims.

Best used when

  • A macro fact needs source-bound explanation before publication or reuse.
  • The agent needs to separate reported data from trading, suitability, or market-outcome language.

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 shows how public evidence packs can help an agent stay source-bound and time-bound instead of sounding overconfident.

Linked service: Evidence Cards

Pack id: macro_release_context_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

  • 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

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: An agent wants to summarize a macro release without turning a single data point into a market-outcome claim.
  • Use it when the reader needs a bounded checklist, sample evidence records, and an example of safe versus blocked language.
  • Treat Macro release context packaging as a scenario-specific public review guide that sits on top of the linked Evidence Cards 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/macro-release-context-pack.json

Linked service page: Evidence Cards

This pack does not do

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

Usage fit

Where this pack helps and where it stops

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

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 release, series_id, series name, BLS CPI table or field, and report field being summarized.
  • Observation date, reported value, retrieval time, realtime_start/realtime_end vintage, and any revision-status note.
  • CFTC COT report date, market name, open-interest or positioning field, and historical compressed context when positioning is cited.
  • The immediate comparison context needed to explain the release without inventing a market, policy, or portfolio conclusion.

Delivery outputs

  • A source-bound macro evidence card with series_id, reported value, observation date, vintage, retrieval time, and cited field.
  • A limitation note covering revision risk, release lag, COT report-date lag, and missing comparison context.
  • Safe restatement language that does not convert one release or COT snapshot into a market, trade, or portfolio call.
  • A do-not-claim block showing which macro-to-outcome conclusions remain unsupported.

Decision matrix

  • Release context row

    Status: confirmed

    Evidence fields: macro_release_context, source_links

    Source requirement: Record the release name, series, period, vintage, and retrieval source before summarizing the macro event.

    Allowed static use: Use this row to anchor the release summary to its source-bound context.

    Blocked upgrade: Do not turn a release fact into a trade-outcome claim or market direction promise.

    Agent action: Summarize the release as a bounded fact note and keep outcomes out of the summary.

  • Revision and lag row

    Status: warning

    Evidence fields: macro_release_context, source_links

    Source requirement: Record revisions, lag, units, seasonal adjustment, and comparison basis so the note does not flatten incomparable values.

    Allowed static use: Use the revision and lag row to keep comparability limits visible in the static note.

    Blocked upgrade: Do not say the series proves a market move, portfolio outcome, or trade signal.

    Agent action: Preserve the revision and lag caveats before summarizing the release.

  • Intended use context row

    Status: warning

    Evidence fields: intended_use_context, source_links

    Source requirement: Record whether the output is internal context, public commentary, a user-facing summary, or an action prompt.

    Allowed static use: Use the intended-use row to choose a bounded phrasing level for the output.

    Blocked upgrade: Do not let internal context wording spill into public advice or execution language.

    Agent action: Keep the output bounded to the intended use context and escalate when it would become advice.

  • Not-a-market-claim row

    Status: blocked

    Evidence fields: macro_release_context, intended_use_context

    Source requirement: Record that this pack is a source-bound macro interpretation aid and not a market-outcome predictor.

    Allowed static use: Use the row only for bounded macro explanation and citation handoff.

    Blocked upgrade: Do not call the release proof of price direction, portfolio performance, or market outcome certainty.

    Agent action: Rewrite or block any wording that turns the release into a trade prediction.

Citation rules

  • Name the FRED series_id, BLS CPI release or table field, CFTC report date, and retrieval time whenever repeating a macro fact.
  • Preserve FRED realtime_start/realtime_end vintage context when citing a series observation.
  • Keep the reported macro value separate from CFTC positioning context, later market interpretation, strategy language, or portfolio claims.
  • Do not describe a single release as proof of the next market move, trade outcome, portfolio decision, or policy decision.

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 macro note: summarize a CPI release and explain what the published value shows without turning one print into a market-direction claim.

Sample evidence records

  • FRED series observations identify the series_id, observation date, reported value, realtime_start, and realtime_end vintage

    Status: confirmed

    Source: FRED series observations API documentation

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

    The source supports a time-bound macro observation; it does not support a market outcome or trade conclusion.

  • FRED API documentation remains a source requirement for macro series retrieval and field interpretation

    Status: warning

    Source: FRED API documentation

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

    The API reference supports retrieval mechanics and field names; the static pack does not run a live FRED refresh.

  • BLS CPI data pages provide the CPI release/table source for the reported inflation field

    Status: confirmed

    Source: BLS CPI data

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

    The CPI source can anchor the release field, but it should not be upgraded into a policy or market prediction.

  • BLS public data API features describe machine retrieval behavior without making this sample a live API result

    Status: warning

    Source: BLS public data API features

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

    A downstream agent should preserve the static retrieval time unless it independently fetches and cites a fresh BLS response.

  • CFTC Commitment of Traders context carries a report date and can lag the macro release being summarized

    Status: warning

    Source: CFTC Commitment of Traders

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

    The positioning reference can add context, but it should not be collapsed into the release value or used as a timing signal.

  • CFTC Historical Compressed files can provide prior report context, but they remain contextual evidence only

    Status: warning

    Source: CFTC Historical Compressed COT data

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

    Historical COT context helps compare report dates; it does not prove a future trade outcome.

Evidence Card sample

Macro release context packaging sample evidence card

Review verdict: allow_with_limits

The cited sources report the macro value for the listed series_id and retrieval time; interpretation remains bounded by revision risk, vintage context, and COT lag, and this is not a market or portfolio call.

Citation block

  • artifactVersion=public-material-macro-release-context-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/macro-release-context-pack
  • artifactPath=/reliability/public-materials/macro-release-context-pack.json

Key findings

  • confirmed: FRED series observations identify the series_id, observation date, reported value, realtime_start, and realtime_end vintage (The source supports a time-bound macro observation; it does not support a market outcome or trade conclusion.)
  • warning: FRED API documentation remains a source requirement for macro series retrieval and field interpretation (The API reference supports retrieval mechanics and field names; the static pack does not run a live FRED refresh.)
  • confirmed: BLS CPI data pages provide the CPI release/table source for the reported inflation field (The CPI source can anchor the release field, but it should not be upgraded into a policy or market prediction.)
  • warning: BLS public data API features describe machine retrieval behavior without making this sample a live API result (A downstream agent should preserve the static retrieval time unless it independently fetches and cites a fresh BLS response.)
  • warning: CFTC Commitment of Traders context carries a report date and can lag the macro release being summarized (The positioning reference can add context, but it should not be collapsed into the release value or used as a timing signal.)
  • warning: CFTC Historical Compressed files can provide prior report context, but they remain contextual evidence only (Historical COT context helps compare report dates; it does not prove a future trade outcome.)

Required disclosures

  • Static public sample only; not a live review, approval, compliance clearance, or request-time judgment.
  • 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.
  • A single release does not establish the next market move, portfolio decision, trade outcome, or policy decision.
  • Revision risk, FRED vintage context, BLS release scope, and CFTC report-date lag must stay visible whenever the release is summarized.
  • The static sample does not prove a live FRED, BLS, or CFTC refresh occurred.

Do not claim

  • This release proves the next market move.
  • This data point guarantees a rate decision or trade outcome.
  • The macro evidence alone is enough to recommend a position.

Action routing

actionRouting type: macro_release_context_interpretation

Preflight stage: before_macro_summary_or_market_commentary

Default posture: allow_with_limits

Primary action risk: A macro data point may be repeated without revision, vintage, release-lag, COT lag, or non-trading limitations.

Minimum input field ids: macro_release_context, source_links, intended_use_context

Minimum required inputs

  • Official source, series or release identifier, publication timestamp, and retrieval timestamp.
  • Reported period, vintage or revision status, units, seasonal adjustment, and release lag context.
  • Comparison baseline, previous value, consensus or benchmark if cited, and source limitation notes.
  • Intended use of the output, especially whether it may be reused in market commentary or trading language.

Missing input fallback

Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.

Route when

  • An agent needs to summarize a macro release, FRED series, BLS release, or CFTC positioning note.
  • The output needs evidence-card style source, timestamp, and limitation language before it is reused.

Stop or escalate when

  • The summary converts a reported value into a market call, trade instruction, or portfolio recommendation.
  • Revision risk, publication lag, report-date lag, source scope, or comparison context is missing.

Search intent

Intent id: macro_release_context_pack_search_intent

User task: Package macro release facts into source-bound context without upgrading them into market predictions.

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

queryExamples: explain CPI release with sources, macro release context, safe statement about inflation data

Use when

  • An agent needs to summarize a macro release, FRED series, BLS release, or CFTC positioning note.
  • A macro fact needs source-bound explanation before publication or reuse.
  • 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

macro_release_context: Release, series, period, vintage, unit, seasonal adjustment, lag, and comparison context. Missing input risk: The agent may turn a stale or incomparable data point into overconfident market commentary.

source_links: Official registries, warning pages, filings, releases, or cited public pages used as evidence. Missing input risk: The agent cannot separate source-bound evidence from unsourced assertion.

intended_use_context: Whether the output will be used as internal context, public copy, market commentary, or an action prompt. Missing input risk: The agent may apply the wrong safety boundary to the final output.

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.

macro_release_context: What evidence identifies the macro release context for this macro_release_context_interpretation review? Acceptable evidence: series ID, release timestamp, reported period, vintage, unit. If missing: The agent may turn a stale or incomparable data point into overconfident market commentary. Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.

source_links: What evidence identifies the source links for this macro_release_context_interpretation review? Acceptable evidence: OFAC URL, SEC filing URL, FRED series URL, public warning page. If missing: The agent cannot separate source-bound evidence from unsourced assertion. Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.

intended_use_context: What evidence identifies the intended use context for this macro_release_context_interpretation review? Acceptable evidence: internal note, public summary, market commentary, trade prompt. If missing: The agent may apply the wrong safety boundary to the final output. Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.

Decision policy

Default posture: allow_with_limits

Allowed static output: The cited sources report the macro value for the listed series_id and retrieval time; interpretation remains bounded by revision risk, vintage context, and COT lag, and this is not a market or portfolio call.

Blocked static output: This CPI release proves the next market move and justifies a portfolio trade.

Proceed only when

  • Collected and cited: Official source, series or release identifier, publication timestamp, and retrieval timestamp.
  • Collected and cited: Reported period, vintage or revision status, units, seasonal adjustment, and release lag context.
  • Collected and cited: Comparison baseline, previous value, consensus or benchmark if cited, and source limitation notes.
  • Collected and cited: Intended use of the output, especially whether it may be reused in market commentary or trading language.

Fallback when missing inputs

Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.

Stop or escalate when

  • The summary converts a reported value into a market call, trade instruction, or portfolio recommendation.
  • Revision risk, publication lag, report-date lag, source scope, or comparison context is missing.
  • A single release is being used to justify a strong market-direction claim.
  • The observed time, revision status, or source field is unclear.
  • The summary jumps from one data point to a broad portfolio or trading conclusion.

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: Official source, series or release identifier, publication timestamp, and retrieval timestamp.; Reported period, vintage or revision status, units, seasonal adjustment, and release lag context.; Comparison baseline, previous value, consensus or benchmark if cited, and source limitation notes.; Intended use of the output, especially whether it may be reused in market commentary or trading language.. Required action: Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note. Allowed output: The cited sources report the macro value for the listed series_id and retrieval time; interpretation remains bounded by revision risk, vintage context, and COT lag, and this is not a market or portfolio call. Blocked upgrade: This CPI release proves the next market move and justifies a portfolio trade. Human review required: yes.

escalate: Any stop-or-escalate trigger applies: The summary converts a reported value into a market call, trade instruction, or portfolio recommendation.; Revision risk, publication lag, report-date lag, source scope, or comparison context is missing.; A single release is being used to justify a strong market-direction claim.; The observed time, revision status, or source field is unclear.; The summary jumps from one data point to a broad portfolio or trading conclusion.. 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 cited release reported the stated value at the observed time. This pack gives source-bound context and does not establish what the market must do next. Any interpretation should preserve revision risk and release-specific limitations. Blocked upgrade: This release proves the next market move. This data point guarantees a rate decision or trade outcome. The macro evidence alone is enough to recommend a position. 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: The cited sources report the macro value for the listed series_id and retrieval time; interpretation remains bounded by revision risk, vintage context, and COT lag, and this is not a market or portfolio call. Blocked upgrade: This CPI release proves the next market move and justifies a portfolio trade. 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: macro_release_context, source_links, intended_use_context.

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: macro_release_context, source_links, intended_use_context.

Static action note template

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

Required sections

  • action_context: State the action type, preflight stage, default posture, and collected minimum inputs: Official source, series or release identifier, publication timestamp, and retrieval timestamp.; Reported period, vintage or revision status, units, seasonal adjustment, and release lag context.; Comparison baseline, previous value, consensus or benchmark if cited, and source limitation notes.; Intended use of the output, especially whether it may be reused in market commentary or trading language..
  • source_bound_evidence: List only cited evidence collected for this pack: The exact release, series_id, series name, BLS CPI table or field, and report field being summarized.; Observation date, reported value, retrieval time, realtime_start/realtime_end vintage, and any revision-status note.; CFTC COT report date, market name, open-interest or positioning field, and historical compressed context when positioning is cited.; The immediate comparison context needed to explain the release without inventing a market, policy, or portfolio conclusion..
  • decision_policy: Apply fallback 'Defer market interpretation; collect release, vintage, unit, lag, and comparison context, and keep any interim output as a source-bound note.' and stop/escalate when any policy trigger applies.
  • safe_restatement: Use bounded language no stronger than: The cited sources report the macro value for the listed series_id and retrieval time; interpretation remains bounded by revision risk, vintage context, and COT lag, and this is not a market or portfolio call.
  • blocked_language: Do not restate or imply: This CPI release proves the next market move and justifies a portfolio trade.
  • citation_trail: Preserve citation requirements: Name the FRED series_id, BLS CPI release or table field, CFTC report date, and retrieval time whenever repeating a macro fact.; Preserve FRED realtime_start/realtime_end vintage context when citing a series observation.; Keep the reported macro value separate from CFTC positioning context, later market interpretation, strategy language, or portfolio claims.; Do not describe a single release as proof of the next market move, trade outcome, portfolio decision, or policy decision..

Static action note example

Example id: macro_release_context_pack_static_action_note_example

Note status: allow_with_limits

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 macro note: summarize a CPI release and explain what the published value shows without turning one print into a market-direction claim. Action type: macro_release_context_interpretation. Default posture: allow_with_limits. Minimum inputs: Official source, series or release identifier, publication timestamp, and retrieval timestamp.; Reported period, vintage or revision status, units, seasonal adjustment, and release lag context.; Comparison baseline, previous value, consensus or benchmark if cited, and source limitation notes.; Intended use of the output, especially whether it may be reused in market commentary or trading language..
  • source_bound_evidence: confirmed: FRED series observations identify the series_id, observation date, reported value, realtime_start, and realtime_end vintage. The source supports a time-bound macro observation; it does not support a market outcome or trade conclusion. warning: FRED API documentation remains a source requirement for macro series retrieval and field interpretation. The API reference supports retrieval mechanics and field names; the static pack does not run a live FRED refresh. confirmed: BLS CPI data pages provide the CPI release/table source for the reported inflation field. The CPI source can anchor the release field, but it should not be upgraded into a policy or market prediction. warning: BLS public data API features describe machine retrieval behavior without making this sample a live API result. A downstream agent should preserve the static retrieval time unless it independently fetches and cites a fresh BLS response. warning: CFTC Commitment of Traders context carries a report date and can lag the macro release being summarized. The positioning reference can add context, but it should not be collapsed into the release value or used as a timing signal. warning: CFTC Historical Compressed files can provide prior report context, but they remain contextual evidence only. Historical COT context helps compare report dates; it does not prove a future trade outcome.
  • decision_policy: allow_with_limits: The macro release can be restated with source, series_id, reported value, vintage, retrieval time, and scope intact, but interpretation limits must stay visible. Unresolved items: A single release does not establish the next market move, portfolio decision, trade outcome, or policy decision.; Revision risk, FRED vintage context, BLS release scope, and CFTC report-date lag must stay visible whenever the release is summarized.; The static sample does not prove a live FRED, BLS, or CFTC refresh occurred. Required follow-up: Name the exact release field, series_id, observation date, reported value, and retrieval time in the final evidence card.; Keep any market, policy, or portfolio interpretation separate from the reported release value and COT context.; Add revision-risk, vintage, and lag language before reusing the sample in a public macro note..
  • safe_restatement: The cited sources report the macro value for the listed series_id and retrieval time; interpretation remains bounded by revision risk, vintage context, and COT lag, and this is not a market or portfolio call.
  • blocked_language: This CPI release proves the next market move and justifies a portfolio trade.
  • citation_trail: Macro release context packaging, public-material-macro-release-context-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/macro-release-context-pack Citation requirements: Name the FRED series_id, BLS CPI release or table field, CFTC report date, and retrieval time whenever repeating a macro fact.; Preserve FRED realtime_start/realtime_end vintage context when citing a series observation.; Keep the reported macro value separate from CFTC positioning context, later market interpretation, strategy language, or portfolio claims.; Do not describe a single release as proof of the next market move, trade outcome, portfolio decision, or policy decision..

Agent workflow

Workflow id: macro_release_context_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: macro_release_context_pack_static_action_note_example

Canonical citation: Macro release context packaging, public-material-macro-release-context-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/macro-release-context-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: macro_release_context_pack

Action type: macro_release_context_interpretation

Workflow id: macro_release_context_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: 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.

Default posture: allow_with_limits

Must confirm before use

  • Collected and cited every minimum input field: macro_release_context, source_links, intended_use_context.
  • 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: macro_release_context, source_links, intended_use_context.
  • 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: macro_release_context_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: macro_release_context_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-macro-release-context-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: macro_release_context_pack

Page: https://trading4ai.com/agent-verification/materials/macro-release-context-pack

Artifact: https://trading4ai.com/reliability/public-materials/macro-release-context-pack.json

Action type: macro_release_context_interpretation

Default posture: allow_with_limits

Minimum input fields: macro_release_context, source_links, intended_use_context

Decision matrix rows: 4

Evidence verification steps: 5

Misuse patterns: 2

Canonical citation: Macro release context packaging, public-material-macro-release-context-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/macro-release-context-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

  • Release context row
  • Revision and lag row
  • Intended use context row
  • Not-a-market-claim 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: macro_release_context_pack

Default posture: allow_with_limits

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: FRED series observations API documentation, FRED API documentation, BLS CPI data, BLS public data API features, CFTC Commitment of Traders, CFTC Historical Compressed COT data.

    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[]

Source manifest

  • FRED series observations API documentation

    URL: https://fred.stlouisfed.org/docs/api/fred/series/series_observations.html

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

    Evidence records: fred_series_observation_vintage

    Supports: FRED series observations identify the series_id, observation date, reported value, realtime_start, and realtime_end vintage / This shows how public evidence packs can help an agent stay source-bound and time-bound instead of sounding overconfident.

    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.
  • FRED API documentation

    URL: https://fred.stlouisfed.org/docs/api/fred/

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

    Evidence records: fred_api_source_boundary

    Supports: FRED API documentation remains a source requirement for macro series retrieval and field interpretation / This shows how public evidence packs can help an agent stay source-bound and time-bound instead of sounding overconfident.

    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.
  • BLS CPI data

    URL: https://www.bls.gov/cpi/data.htm

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

    Evidence records: bls_cpi_release_source

    Supports: BLS CPI data pages provide the CPI release/table source for the reported inflation field / This shows how public evidence packs can help an agent stay source-bound and time-bound instead of sounding overconfident.

    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.
  • BLS public data API features

    URL: https://www.bls.gov/bls/api_features.htm

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

    Evidence records: bls_public_data_api_boundary

    Supports: BLS public data API features describe machine retrieval behavior without making this sample a live API result / This shows how public evidence packs can help an agent stay source-bound and time-bound instead of sounding overconfident.

    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.
  • CFTC Commitment of Traders

    URL: https://www.cftc.gov/MarketReports/CommitmentsofTraders/index.htm

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

    Evidence records: cftc_cot_report_lag

    Supports: CFTC Commitment of Traders context carries a report date and can lag the macro release being summarized / This shows how public evidence packs can help an agent stay source-bound and time-bound instead of sounding overconfident.

    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.
  • CFTC Historical Compressed COT data

    URL: https://www.cftc.gov/MarketReports/CommitmentsofTraders/HistoricalCompressed/index.htm

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

    Evidence records: cftc_historical_compressed_context

    Supports: CFTC Historical Compressed files can provide prior report context, but they remain contextual evidence only / This shows how public evidence packs can help an agent stay source-bound and time-bound instead of sounding overconfident.

    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: allow_with_limits

The macro release can be restated with source, series_id, reported value, vintage, retrieval time, and scope intact, but interpretation limits must stay visible.

Safe restatement: The cited sources report the macro value for the listed series_id and retrieval time; interpretation remains bounded by revision risk, vintage context, and COT lag, and this is not a market or portfolio call.

Blocked restatement: This CPI release proves the next market move and justifies a portfolio trade.

Unresolved items

  • A single release does not establish the next market move, portfolio decision, trade outcome, or policy decision.
  • Revision risk, FRED vintage context, BLS release scope, and CFTC report-date lag must stay visible whenever the release is summarized.
  • The static sample does not prove a live FRED, BLS, or CFTC refresh occurred.

Required follow-up

  • Name the exact release field, series_id, observation date, reported value, and retrieval time in the final evidence card.
  • Keep any market, policy, or portfolio interpretation separate from the reported release value and COT context.
  • Add revision-risk, vintage, and lag language before reusing the sample in a public macro note.

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

  • Confirm the release name, series_id, observation date, reported value, and cited release field before summarizing.
  • Preserve FRED realtime_start/realtime_end vintage context and any BLS CPI release or table reference used.
  • Separate the reported macro value from CFTC COT positioning context, later market interpretation, or narrative.
  • Preserve revision risk, publication lag, COT report-date lag, and scope limits when restating the evidence.
  • State when supporting context is missing rather than filling the gap with a policy, market, or portfolio call.

Escalation triggers

  • A single release is being used to justify a strong market-direction claim.
  • The observed time, revision status, or source field is unclear.
  • The summary jumps from one data point to a broad portfolio or trading conclusion.

Safe to repeat

  • The cited release reported the stated value at the observed time.
  • This pack gives source-bound context and does not establish what the market must do next.
  • Any interpretation should preserve revision risk and release-specific limitations.

Blocked claims

  • This release proves the next market move.
  • This data point guarantees a rate decision or trade outcome.
  • The macro evidence alone is enough to recommend a position.

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-macro-release-context-pack-2026-05-25

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

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

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

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

When citing this pack, preserve artifactVersion, generatedAt, sampleEvidenceRecords[].retrievedAt, and the bounded sampleReviewOutput summary.

Keep the pack source-bound and do not upgrade it into valuation, execution, or suitability advice.