TRADING4AIStatic public material pack for financial-agent reliability review

Public Material Pack

Public company filing review

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

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 summarize a public company filing event without upgrading filing facts into valuation or recommendation claims.

Example input

A user asks an agent to summarize a filing, exhibit, item, XBRL fact, or company event and then publish a bounded explanation.

Expected static output

A source-bound filing note that preserves CIK, accession, form type, filing date, source path, exact field or exhibit, limitations, and blocked recommendation language.

Best used when

  • A public filing fact needs to be cited precisely before an agent repeats it.
  • The agent needs to separate filing-supported facts from analyst interpretation, price targets, or suitability claims.

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 a useful middle ground between full securities research and generic AI summarization: preserve provenance, timestamps, and limits.

Linked service: Evidence Cards

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

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

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 needs bounded evidence around a company filing event before drafting a public-facing summary or internal note.
  • Use it when the reader needs a bounded checklist, sample evidence records, and an example of safe versus blocked language.
  • Treat Public company filing review 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.

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 produce valuation, price targets, suitability conclusions, or real-time securities research.

Usage fit

Where this pack helps and where it stops

Suitable for

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

Not suitable for

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

Source / limitation policy

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

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 issuer name, CIK, form type, filing date, accession number, primary document, and source URL being cited.
  • The exact filing sections, exhibit references, XBRL tags, companyfacts fields, or attachments that support the summary.
  • Period end, fiscal year, fiscal period, item number, exhibit number, XBRL fact value, unit, scale, and any inline XBRL context used in the fact table.
  • The retrieval time and SEC EDGAR access path used by the static sample.
  • Any amendment, superseded filing, or incomplete-record context that changes how the filing should be read.

Delivery outputs

  • A bounded filing evidence card tied to exact SEC EDGAR CIK, accession, filing date, and section or field references.
  • A filing fact matrix that keeps period, item, exhibit, XBRL fact value, unit, scale, source path, and not live refresh status together.
  • An amendment, superseded-record, or missing-context note when the filing record is incomplete.
  • Safe source-bound language that keeps filing facts separate from valuation, price-target, recommendation, or suitability claims.
  • A do-not-claim block showing which filing-to-investment conclusions remain unsupported.

Decision matrix

  • Filing identifier row

    Status: confirmed

    Evidence fields: filing_identifier, source_links

    Source requirement: Record the company, CIK, accession number, form type, filing date, and reporting period as the anchor for the filing summary.

    Allowed static use: Use as the filing identity anchor for the source-bound event summary.

    Blocked upgrade: Do not turn the filing identifier into valuation support or a recommendation.

    Agent action: Anchor the summary to the filing identity before summarizing any facts.

  • Filing fact reference row

    Status: warning

    Evidence fields: filing_fact_reference, source_links

    Source requirement: Record the exact item, exhibit, XBRL fact, unit, scale, and source path for the filing fact being cited.

    Allowed static use: Use this row as the structured filing fact reference for bounded summaries.

    Blocked upgrade: Do not upgrade a filing fact reference into price target, valuation, or suitability language.

    Agent action: Preserve the exact fact context and keep valuation claims out.

  • Period and exhibit context row

    Status: warning

    Evidence fields: filing_identifier, filing_fact_reference

    Source requirement: Record period end, fiscal year, fiscal period, item number, and exhibit references so the note does not lose the filing context.

    Allowed static use: Use as a static filing-context row that keeps period and exhibit boundaries visible.

    Blocked upgrade: Do not drop period or exhibit context and then say the result is current, complete, or comparable enough for recommendation language.

    Agent action: Retain period and exhibit context in every summary and escalate if the context is incomplete.

  • Not valuation or suitability row

    Status: blocked

    Evidence fields: filing_identifier, intended_use_context

    Source requirement: Record the intended use and the fact that this pack is a source-bound filing-review aid, not a valuation or suitability tool.

    Allowed static use: Use only for bounded filing summaries that preserve the source boundary.

    Blocked upgrade: Do not convert the filing note into valuation, recommendation, or suitability language.

    Agent action: Block valuation wording and escalate when the user wants a recommendation.

Citation rules

  • Cite the SEC EDGAR source path, issuer CIK, accession number, filing date, form type, and retrieval time whenever the summary repeats a filing-supported fact.
  • Preserve the EDGAR API or search path used in the static sample and do not imply a live refresh occurred.
  • Respect SEC EDGAR fair-access and user-agent requirements when any downstream agent retrieves the source directly.
  • Distinguish filing facts from analyst interpretation, valuation, price-target, trading, or suitability conclusions.
  • Preserve amendment and scope language instead of implying that one filing resolves the whole investment question.

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 filing summary: restate a public company event from an 8-K without turning the filing into valuation language or a buy recommendation.

Sample evidence records

  • SEC EDGAR Search Filings identified the issuer CIK, form type, filing date, accession number, and primary document

    Status: confirmed

    Source: SEC EDGAR Search Filings

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

    This anchors the event summary to filing identifiers rather than a generic company narrative.

  • SEC EDGAR Submissions API and companyfacts/XBRL endpoints define the structured fields an agent may cite

    Status: confirmed

    Source: SEC EDGAR API documentation

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

    Structured fields help an Evidence Card cite what was observed, but they still do not create valuation support.

  • The filing fact matrix must preserve period end, fiscal year, fiscal period, item number, and exhibit references

    Status: warning

    Source: SEC EDGAR filing context checklist

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

    A company-event summary becomes ambiguous if it drops period end, fiscal context, item number, exhibit number, or whether the cited record is initial or amended.

  • XBRL fact value, unit, scale, and inline XBRL context must travel with any structured numeric filing fact

    Status: warning

    Source: SEC EDGAR API documentation

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

    A fact value without unit, scale, period, and source field context is not safe to reuse as a machine-readable Evidence Card claim.

  • Programmatic retrieval must preserve fair access behavior, including user agent and request rate discipline

    Status: warning

    Source: SEC accessing EDGAR data guidance

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

    A downstream agent should cite static retrieval time here and must not imply TRADING4AI performed a live SEC refresh.

  • No source in the sample package supports a price target, valuation view, or suitability conclusion

    Status: unresolved

    Source: Public company filing pack sample boundary

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

    The filing supports an event summary only, not a securities recommendation.

Evidence Card sample

Public company filing review sample evidence card

Review verdict: review

The cited SEC EDGAR record states the filing event under the listed CIK, accession number, period, item, exhibit, XBRL unit and scale, and retrieval time; this static sample is not a live refresh, is not valuation research, and does not establish suitability.

Citation block

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

Key findings

  • confirmed: SEC EDGAR Search Filings identified the issuer CIK, form type, filing date, accession number, and primary document (This anchors the event summary to filing identifiers rather than a generic company narrative.)
  • confirmed: SEC EDGAR Submissions API and companyfacts/XBRL endpoints define the structured fields an agent may cite (Structured fields help an Evidence Card cite what was observed, but they still do not create valuation support.)
  • warning: The filing fact matrix must preserve period end, fiscal year, fiscal period, item number, and exhibit references (A company-event summary becomes ambiguous if it drops period end, fiscal context, item number, exhibit number, or whether the cited record is initial or amended.)
  • warning: XBRL fact value, unit, scale, and inline XBRL context must travel with any structured numeric filing fact (A fact value without unit, scale, period, and source field context is not safe to reuse as a machine-readable Evidence Card claim.)
  • warning: Programmatic retrieval must preserve fair access behavior, including user agent and request rate discipline (A downstream agent should cite static retrieval time here and must not imply TRADING4AI performed a live SEC refresh.)
  • unresolved: No source in the sample package supports a price target, valuation view, or suitability conclusion (The filing supports an event summary only, not a securities recommendation.)

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 produce valuation, price targets, suitability conclusions, or real-time securities research.
  • The filing does not by itself support a price target, buy rating, valuation view, or suitability claim.
  • Any amended or later filing context must still be checked before publication.
  • The static sample records retrieval time and source paths; it does not prove a live EDGAR refresh occurred.

Do not claim

  • This filing proves the stock will rise.
  • The filing alone makes the company a buy.
  • The filing summary is a substitute for full securities research.

Action routing

actionRouting type: public_company_filing_review

Preflight stage: before_filing_summary_or_company_claim

Default posture: review

Primary action risk: A filing fact may be summarized without CIK, accession, period, item, exhibit, XBRL, unit, scale, or not-live-refresh boundaries.

Minimum input field ids: filing_identifier, filing_fact_reference, source_links, intended_use_context

Minimum required inputs

  • Company name, ticker if used, CIK, form type, accession number, filing date, and reporting period.
  • Exact filing item, exhibit, XBRL fact, unit, scale, or table reference behind the claim.
  • Source URL and retrieval timestamp for the SEC filing, company filing page, or other cited official source.
  • Intended claim text and whether the output will be used as summary, research context, or public-facing copy.

Missing input fallback

Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.

Route when

  • An agent needs to summarize or cite a public-company filing fact before using it in research or a company claim.
  • The task needs source-bound filing context without becoming valuation, price target, suitability, or buy/sell advice.

Stop or escalate when

  • CIK, accession, filing date, reporting period, item, exhibit, XBRL unit, or scale context is missing.
  • The output turns filing context into valuation, recommendation, suitability, or a live freshness guarantee.

Search intent

Intent id: public_company_filing_pack_search_intent

User task: Turn a company filing event into a cited evidence note without making valuation or recommendation claims.

Route reason: Route to Public company filing review when the user task matches public_company_filing_review and needs A source-bound filing note that preserves CIK, accession, form type, filing date, source path, exact field or exhibit, limitations, and blocked recommendation language.

queryExamples: SEC filing evidence card, company filing event summary, 10-K or 8-K source card

Use when

  • An agent needs to summarize or cite a public-company filing fact before using it in research or a company claim.
  • A public filing fact needs to be cited precisely before an agent repeats it.
  • 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

filing_identifier: Company, ticker if used, CIK, form type, accession number, filing date, and reporting period. Missing input risk: The agent may cite the wrong filing, wrong period, or stale company fact.

filing_fact_reference: The exact item, exhibit, XBRL fact, table, unit, and scale behind a filing claim. Missing input risk: The agent may restate a filing fact with the wrong unit, scale, or source location.

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.

filing_identifier: What evidence identifies the filing identifier for this public_company_filing_review review? Acceptable evidence: CIK, 10-K, 8-K, accession number, filing date. If missing: The agent may cite the wrong filing, wrong period, or stale company fact. Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.

filing_fact_reference: What evidence identifies the filing fact reference for this public_company_filing_review review? Acceptable evidence: Item 7, Exhibit 99.1, XBRL concept, USD millions, share count. If missing: The agent may restate a filing fact with the wrong unit, scale, or source location. Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.

source_links: What evidence identifies the source links for this public_company_filing_review 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 the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.

intended_use_context: What evidence identifies the intended use context for this public_company_filing_review 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 the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.

Decision policy

Default posture: review

Allowed static output: The cited SEC EDGAR record states the filing event under the listed CIK, accession number, period, item, exhibit, XBRL unit and scale, and retrieval time; this static sample is not a live refresh, is not valuation research, and does not establish suitability.

Blocked static output: This filing proves the stock is a buy and supports a new price target.

Proceed only when

  • Collected and cited: Company name, ticker if used, CIK, form type, accession number, filing date, and reporting period.
  • Collected and cited: Exact filing item, exhibit, XBRL fact, unit, scale, or table reference behind the claim.
  • Collected and cited: Source URL and retrieval timestamp for the SEC filing, company filing page, or other cited official source.
  • Collected and cited: Intended claim text and whether the output will be used as summary, research context, or public-facing copy.

Fallback when missing inputs

Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.

Stop or escalate when

  • CIK, accession, filing date, reporting period, item, exhibit, XBRL unit, or scale context is missing.
  • The output turns filing context into valuation, recommendation, suitability, or a live freshness guarantee.
  • The summary upgrades a filing event into a price target or investment conclusion.
  • Key filing context, amendments, or attachments were not reviewed.
  • A marketing or social claim is being repeated without the underlying filing support.

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: Company name, ticker if used, CIK, form type, accession number, filing date, and reporting period.; Exact filing item, exhibit, XBRL fact, unit, scale, or table reference behind the claim.; Source URL and retrieval timestamp for the SEC filing, company filing page, or other cited official source.; Intended claim text and whether the output will be used as summary, research context, or public-facing copy.. Required action: Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing. Allowed output: The cited SEC EDGAR record states the filing event under the listed CIK, accession number, period, item, exhibit, XBRL unit and scale, and retrieval time; this static sample is not a live refresh, is not valuation research, and does not establish suitability. Blocked upgrade: This filing proves the stock is a buy and supports a new price target. Human review required: yes.

escalate: Any stop-or-escalate trigger applies: CIK, accession, filing date, reporting period, item, exhibit, XBRL unit, or scale context is missing.; The output turns filing context into valuation, recommendation, suitability, or a live freshness guarantee.; The summary upgrades a filing event into a price target or investment conclusion.; Key filing context, amendments, or attachments were not reviewed.; A marketing or social claim is being repeated without the underlying filing support.. 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 filing states the cited event or disclosure in the referenced source set. This pack preserves source provenance and does not convert the filing into a suitability judgment. Further interpretation should remain bounded by the filing scope and retrieval time. Blocked upgrade: This filing proves the stock will rise. The filing alone makes the company a buy. The filing summary is a substitute for full securities research. 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 SEC EDGAR record states the filing event under the listed CIK, accession number, period, item, exhibit, XBRL unit and scale, and retrieval time; this static sample is not a live refresh, is not valuation research, and does not establish suitability. Blocked upgrade: This filing proves the stock is a buy and supports a new price target. 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: filing_identifier, filing_fact_reference, 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: filing_identifier, filing_fact_reference, 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: Company name, ticker if used, CIK, form type, accession number, filing date, and reporting period.; Exact filing item, exhibit, XBRL fact, unit, scale, or table reference behind the claim.; Source URL and retrieval timestamp for the SEC filing, company filing page, or other cited official source.; Intended claim text and whether the output will be used as summary, research context, or public-facing copy..
  • source_bound_evidence: List only cited evidence collected for this pack: The issuer name, CIK, form type, filing date, accession number, primary document, and source URL being cited.; The exact filing sections, exhibit references, XBRL tags, companyfacts fields, or attachments that support the summary.; Period end, fiscal year, fiscal period, item number, exhibit number, XBRL fact value, unit, scale, and any inline XBRL context used in the fact table.; The retrieval time and SEC EDGAR access path used by the static sample.; Any amendment, superseded filing, or incomplete-record context that changes how the filing should be read..
  • decision_policy: Apply fallback 'Defer the company claim; collect missing filing identifiers, item or exhibit references, units, and retrieval context before publishing or citing.' and stop/escalate when any policy trigger applies.
  • safe_restatement: Use bounded language no stronger than: The cited SEC EDGAR record states the filing event under the listed CIK, accession number, period, item, exhibit, XBRL unit and scale, and retrieval time; this static sample is not a live refresh, is not valuation research, and does not establish suitability.
  • blocked_language: Do not restate or imply: This filing proves the stock is a buy and supports a new price target.
  • citation_trail: Preserve citation requirements: Cite the SEC EDGAR source path, issuer CIK, accession number, filing date, form type, and retrieval time whenever the summary repeats a filing-supported fact.; Preserve the EDGAR API or search path used in the static sample and do not imply a live refresh occurred.; Respect SEC EDGAR fair-access and user-agent requirements when any downstream agent retrieves the source directly.; Distinguish filing facts from analyst interpretation, valuation, price-target, trading, or suitability conclusions.; Preserve amendment and scope language instead of implying that one filing resolves the whole investment question..

Static action note example

Example id: public_company_filing_pack_static_action_note_example

Note status: review

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 filing summary: restate a public company event from an 8-K without turning the filing into valuation language or a buy recommendation. Action type: public_company_filing_review. Default posture: review. Minimum inputs: Company name, ticker if used, CIK, form type, accession number, filing date, and reporting period.; Exact filing item, exhibit, XBRL fact, unit, scale, or table reference behind the claim.; Source URL and retrieval timestamp for the SEC filing, company filing page, or other cited official source.; Intended claim text and whether the output will be used as summary, research context, or public-facing copy..
  • source_bound_evidence: confirmed: SEC EDGAR Search Filings identified the issuer CIK, form type, filing date, accession number, and primary document. This anchors the event summary to filing identifiers rather than a generic company narrative. confirmed: SEC EDGAR Submissions API and companyfacts/XBRL endpoints define the structured fields an agent may cite. Structured fields help an Evidence Card cite what was observed, but they still do not create valuation support. warning: The filing fact matrix must preserve period end, fiscal year, fiscal period, item number, and exhibit references. A company-event summary becomes ambiguous if it drops period end, fiscal context, item number, exhibit number, or whether the cited record is initial or amended. warning: XBRL fact value, unit, scale, and inline XBRL context must travel with any structured numeric filing fact. A fact value without unit, scale, period, and source field context is not safe to reuse as a machine-readable Evidence Card claim. warning: Programmatic retrieval must preserve fair access behavior, including user agent and request rate discipline. A downstream agent should cite static retrieval time here and must not imply TRADING4AI performed a live SEC refresh. unresolved: No source in the sample package supports a price target, valuation view, or suitability conclusion. The filing supports an event summary only, not a securities recommendation.
  • decision_policy: review: The SEC EDGAR source set supports a bounded filing event summary, but any valuation, recommendation, or suitability language remains out of scope and should be removed. Unresolved items: The filing does not by itself support a price target, buy rating, valuation view, or suitability claim.; Any amended or later filing context must still be checked before publication.; The static sample records retrieval time and source paths; it does not prove a live EDGAR refresh occurred. Required follow-up: Quote the exact filing section, exhibit, XBRL tag, or companyfacts field that supports the event summary.; State the issuer CIK, accession number, form type, filing date, period end, fiscal period, item number, exhibit, XBRL unit and scale, and whether the record is initial, amended, or incomplete at retrieval time.; Remove valuation and recommendation language from the final restatement..
  • safe_restatement: The cited SEC EDGAR record states the filing event under the listed CIK, accession number, period, item, exhibit, XBRL unit and scale, and retrieval time; this static sample is not a live refresh, is not valuation research, and does not establish suitability.
  • blocked_language: This filing proves the stock is a buy and supports a new price target.
  • citation_trail: Public company filing review, public-material-public-company-filing-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/public-company-filing-pack Citation requirements: Cite the SEC EDGAR source path, issuer CIK, accession number, filing date, form type, and retrieval time whenever the summary repeats a filing-supported fact.; Preserve the EDGAR API or search path used in the static sample and do not imply a live refresh occurred.; Respect SEC EDGAR fair-access and user-agent requirements when any downstream agent retrieves the source directly.; Distinguish filing facts from analyst interpretation, valuation, price-target, trading, or suitability conclusions.; Preserve amendment and scope language instead of implying that one filing resolves the whole investment question..

Agent workflow

Workflow id: public_company_filing_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: public_company_filing_pack_static_action_note_example

Canonical citation: Public company filing review, public-material-public-company-filing-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/public-company-filing-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: public_company_filing_pack

Action type: public_company_filing_review

Workflow id: public_company_filing_pack_agent_workflow

Source kinds: official_registry, sample_page

Source manifest count: 4

Official registry sources: 3

Official guidance sources: 0

Source quality profile: registry_heavy

Registry coverage expectation: primary_for_this_static_pack

This pack is registry-heavy because public company event evidence should anchor to SEC EDGAR filing identifiers, accession records, documents, and fair-access boundaries.

Agent source use

  • Use SEC EDGAR registry fields as citation anchors for filing facts.
  • Keep issuer, CIK, accession, form type, filing date, item, exhibit, and XBRL fields together.
  • Do not turn filing registry facts into valuation, price-target, suitability, or trading conclusions.

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

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

Default posture: review

Must confirm before use

  • Collected and cited every minimum input field: filing_identifier, filing_fact_reference, 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: filing_identifier, filing_fact_reference, 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: public_company_filing_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: public_company_filing_pack_sample_evidence_card

Source manifest entries: 4

Official registry sources: 3

Source quality boundary: static_source_manifest_not_live_screening

Canonical citation artifact version: public-material-public-company-filing-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: public_company_filing_pack

Page: https://trading4ai.com/agent-verification/materials/public-company-filing-pack

Artifact: https://trading4ai.com/reliability/public-materials/public-company-filing-pack.json

Action type: public_company_filing_review

Default posture: review

Minimum input fields: filing_identifier, filing_fact_reference, source_links, intended_use_context

Decision matrix rows: 4

Evidence verification steps: 5

Misuse patterns: 2

Canonical citation: Public company filing review, public-material-public-company-filing-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/public-company-filing-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

  • Filing identifier row
  • Filing fact reference row
  • Period and exhibit context row
  • Not valuation or suitability 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: public_company_filing_pack

Default posture: review

Static only: yes

  • Source manifest verification

    Verification action: Check the static source manifest before citing this pack. Source kinds: official_registry, sample_page. Source labels: SEC EDGAR Search Filings, SEC EDGAR API documentation, SEC EDGAR filing context checklist, SEC accessing EDGAR data 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[]

Source manifest

  • SEC EDGAR Search Filings

    URL: https://www.sec.gov/search-filings

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

    Evidence records: edgar_accession_record

    Supports: SEC EDGAR Search Filings identified the issuer CIK, form type, filing date, accession number, and primary document / This is a useful middle ground between full securities research and generic AI summarization: preserve provenance, timestamps, and limits.

    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 EDGAR API documentation

    URL: https://www.sec.gov/search-filings/edgar-application-programming-interfaces

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

    Evidence records: edgar_api_structured_fields, xbrl_fact_value_unit_scale

    Supports: SEC EDGAR Submissions API and companyfacts/XBRL endpoints define the structured fields an agent may cite / XBRL fact value, unit, scale, and inline XBRL context must travel with any structured numeric filing fact / This is a useful middle ground between full securities research and generic AI summarization: preserve provenance, timestamps, and limits.

    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 EDGAR filing context checklist

    URL: /agent-verification/materials/public-company-filing-pack

    Kind: sample_page; role: sample_context; retrieved: 2026-05-25T00:00:00.000Z

    Evidence records: filing_period_item_exhibit_context, valuation_support_missing

    Supports: The filing fact matrix must preserve period end, fiscal year, fiscal period, item number, and exhibit references / No source in the sample package supports a price target, valuation view, or suitability conclusion

    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 accessing EDGAR data guidance

    URL: https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data

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

    Evidence records: edgar_fair_access_boundary

    Supports: Programmatic retrieval must preserve fair access behavior, including user agent and request rate discipline / This is a useful middle ground between full securities research and generic AI summarization: preserve provenance, timestamps, and limits.

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

The SEC EDGAR source set supports a bounded filing event summary, but any valuation, recommendation, or suitability language remains out of scope and should be removed.

Safe restatement: The cited SEC EDGAR record states the filing event under the listed CIK, accession number, period, item, exhibit, XBRL unit and scale, and retrieval time; this static sample is not a live refresh, is not valuation research, and does not establish suitability.

Blocked restatement: This filing proves the stock is a buy and supports a new price target.

Unresolved items

  • The filing does not by itself support a price target, buy rating, valuation view, or suitability claim.
  • Any amended or later filing context must still be checked before publication.
  • The static sample records retrieval time and source paths; it does not prove a live EDGAR refresh occurred.

Required follow-up

  • Quote the exact filing section, exhibit, XBRL tag, or companyfacts field that supports the event summary.
  • State the issuer CIK, accession number, form type, filing date, period end, fiscal period, item number, exhibit, XBRL unit and scale, and whether the record is initial, amended, or incomplete at retrieval time.
  • Remove valuation and recommendation language from the final restatement.

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

  • Identify the issuer name, CIK, form type, filing date, accession number, and primary document before summarizing.
  • Tie each repeated fact to the exact SEC EDGAR filing section, exhibit, XBRL tag, or companyfacts field used.
  • Preserve period end, fiscal year, fiscal period, item number, exhibit number, inline XBRL fact value, unit, and scale when citing structured facts.
  • Preserve whether the filing is initial, amended, superseded, or incomplete in the current record.
  • Keep filing facts separate from analyst-style interpretation, valuation language, price targets, or suitability claims.
  • State clearly when the filing supports only a bounded event summary and not a full securities-research conclusion.

Escalation triggers

  • The summary upgrades a filing event into a price target or investment conclusion.
  • Key filing context, amendments, or attachments were not reviewed.
  • A marketing or social claim is being repeated without the underlying filing support.

Safe to repeat

  • The filing states the cited event or disclosure in the referenced source set.
  • This pack preserves source provenance and does not convert the filing into a suitability judgment.
  • Further interpretation should remain bounded by the filing scope and retrieval time.

Blocked claims

  • This filing proves the stock will rise.
  • The filing alone makes the company a buy.
  • The filing summary is a substitute for full securities research.

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-public-company-filing-pack-2026-05-25

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

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

artifactUrl: /reliability/public-materials/public-company-filing-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.