CoTradingCoTrading
HomeSkillsCasesLearnData & sources
中文Free desktop
CoTradingCoTrading
HomeSkillsCasesLearnData & sources
中文Free desktop
CoTradingCoTrading

Research with evidence. Validate with a record. Free methods and your own material, connected to your AI tools and ongoing work.

Product
  • Features
  • Pricing
  • Download
  • FAQ
Resources
  • Skills
  • Cases
  • Data
  • Learn
  • Calculators
  • Blog
  • Documentation
  • Changelog
  • Roadmap
Company
  • About
  • Contact
  • Waitlist
Legal
  • Cookie Policy
  • Privacy Policy
  • Terms of Service
© 2026 CoTrading. All Rights Reserved.
CoTrading

CoTrading

AI research and quantitative workbench

CoTrading serves experienced individual investors with limited time and coding experience. We provide evidence-backed methods, reproducible strategy experiments and ways to continue in your own AI tools. Public teaching cases identify their sources, assumptions and limitations.

How we build and check our methods

A useful research record shows the question, inputs, evidence and limits. These standards apply to our public guides, teaching cases and skill packages.

Keep evidence and interpretation separate

Distinguish reported facts, attributed management explanations, calculations, our inference and unanswered questions. Prefer original filings and official documentation. Link sources near the claim and retain the document, period, currency, unit and page or section needed to check it; a source only supports claims within its actual scope.

Identify the type of example and verification

Label synthetic teaching inputs and historical source reviews explicitly. Expected output, a deterministic tool check and a completed model task are different evidence. State the actual package, host, version and scope tested; missing or pending verification remains visible. An example return is not evidence of future performance.

Describe AI assistance honestly

We use AI to assist research, drafting, translation and code checks. Model output is not an original source, and automated checks do not constitute human financial or reader review. We claim human review or host acceptance only when that specific review or test has actually been completed and recorded; we do not invent reviewers or credentials.

Publish and correct according to the evidence

Availability and compatibility follow the actual release and verification status. Use real publication dates and update dates for substantive revisions. When an error is confirmed, correct the affected claim or release status and identify the relevant version and impact; retain important limitations instead of hiding them behind a success label.

To report a problem, start with a page URL or method version, the error location and a source we can check publicly. Redact personal information. Do not send API keys, actual holdings or full private research documents; confirm your rights before sharing material.

Report an issue or correctionRead the editorial and source standards