Deliverable
Static HTML pages
Pages-only public pages for humans, crawlers, and AI agents to understand the reliability layer.
Current capabilities
What TRADING4AI can and cannot do today.
TRADING4AI currently publishes Pages-only reliability surfaces, static HTML, and downloadable JSON artifacts for financial-agent review work. This page is the current truth boundary for what the public site can provide before any later backend phase exists.
Phase posture
Pages-only, static, crawlable.
Static HTML plus downloadable JSON artifacts are the current deliverables.
Agents can read, cite, and reuse the materials with the stated limitations preserved.
No page should be treated as approval, execution advice, live screening, or financial clearance.
Current public deliverables
What exists right now
The public surface is intentionally small: static pages, static artifacts, and shared discovery text.
Deliverable
Downloadable JSON artifacts
Pre-generated artifacts for structured retrieval, citation handoff, and static material inspection.
Deliverable
Public material packs
Scenario-specific materials for high-risk financial actions, evidence packaging, and claim-safety review.
Deliverable
Machine discovery files
llms.txt, agent.json, sitemap.xml, the public discovery registry, and bridge pages that point machines to the current public truth.
Current services
Three services form the public reliability layer
The service pages explain accepted inputs, output shapes, suitable use cases, limitations, non-goals, and artifact links.
Service
Action Preflight
Static pre-action review for payments, wallet transfers, subscriptions, and other high-risk financial moves.
Open serviceService
Evidence Cards
Source-bound evidence packaging with references, timestamps, safe statements, blocked statements, and limitations.
Open serviceService
Reliability Corpus
Static failure-pattern and claim-safety reference material for agents that need bounded language.
Open serviceWhat this does not do
Current limits are part of the product truth
These limits keep static public materials from being mistaken for a live financial decision system.
Not available
No live backend judgment
Do not upgrade static public material into live approval, suitability, execution, or clearance.
Not available
No live user-submitted review
Do not upgrade static public material into live approval, suitability, execution, or clearance.
Not available
No backtesting
Do not upgrade static public material into live approval, suitability, execution, or clearance.
Not available
No brokerage or exchange execution
Do not upgrade static public material into live approval, suitability, execution, or clearance.
Not available
No compliance clearance or legal opinion
Do not upgrade static public material into live approval, suitability, execution, or clearance.
Not available
No Tencent backend dependency
Do not upgrade static public material into live approval, suitability, execution, or clearance.
Not available
No third-party scraping pipeline in this phase
Do not upgrade static public material into live approval, suitability, execution, or clearance.
Where agents should start
Use the public reading order before downloading artifacts
HTML explains the boundary first; JSON is for structured retrieval after the scope is understood.
StartReason
Current CapabilitiesUse this as the current truth boundary before reading deeper materials.Reliability HomeUse this for the three-service public product line.Public MaterialsUse this when the task is already a concrete scenario.Machine BridgeUse this when a machine-readable reading order is needed.Discovery RegistryUse this when a machine needs the compact static registry for current discovery order and recommended starts.JSON artifacts
Download static payloads only after reading the HTML boundary
Action Preflight JSON: /reliability/action-preflight-sample.json
Evidence Cards JSON: /reliability/evidence-cards-sample.json
Reliability Corpus JSON: /reliability/reliability-corpus-sample.json
Public Materials JSON: /reliability/public-materials-sample.json
Discovery Registry JSON: /reliability/public-discovery-registry.json
Public materials
7 scenario packs are available
Counterparty screening before payment: A financial agent is about to prepare a cross-border vendor payment or wallet transfer to a new counterparty with incomplete verification.
Claim-safety review before publication: An agent is about to restate marketing, evidence, or strategy claims in public-facing language and needs a warning-layer review first.
Crypto signal subscription before payment: A financial agent is about to pay for a crypto signal group or invite-only trading club that promises guaranteed returns and asks for brokerage or custody access.
Wallet transfer to unverified counterparty: A financial agent is asked to send a crypto wallet transfer to a new counterparty in a private group, but the wallet address, ownership claims, and counterparty identity are not independently verified.
Macro release context packaging: An agent wants to summarize a macro release without turning a single data point into a market-outcome claim.
Payment instruction change before settlement: A financial agent is asked to settle an invoice using new bank or wallet instructions that arrived shortly before cut-off through a channel that was not previously verified.
Public company filing review: An agent needs bounded evidence around a company filing event before drafting a public-facing summary or internal note.
Service contract source
Shared service metadata stays aligned
Action Preflight: /reliability/action-preflight-sample.json / static_public_sample
Evidence Cards: /reliability/evidence-cards-sample.json / static_public_sample
Reliability Corpus: /reliability/reliability-corpus-sample.json / static_public_sample